Package names in apt-mo look wrong
See original GitHub issueThis is using https://apt-mo.trafficmanager.net/repos/dotnet
$ apt-get update
$ apt-cache search dotnet
libgtk-dotnet3.0-cil - GTK.NET library
libgtk-dotnet3.0-cil-dev - GTK.NET library - development files
dotnet - .NET Core & command line tools
dotnet-dev - .NET Core & command line tools
dotnet-dev-1.0.0-rc2-23911 - .NET Core & command line tools
dotnet-host - .NET Core Shared Host
dotnet-nightly - Unstable Developer Build of .NET Core & command line tools
dotnet-sharedframework-microsoft.netcore.app-1.0.0-rc2-23911 - .NET Core Shared Framework Microsoft.NETCore.App 1.0.0-rc2-23911
Looks like the version string got put in the package name string…
- dotnet-dev-1.0.0-rc2-23911
- dotnet-sharedframework-microsoft.netcore.app-1.0.0-rc2-23911
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Wrong captured package name when - in name #6127
It (the group name ) matched cassandra-driver 's cassadra but driver dropped, so the project name mismatch. It used to work at pip...
Read more >Package name does not correspond to the file path - IntelliJ
File > Settings > Editor > Inspections, then search for "Wrong package statement " (Under Java, Probable Bugs) on the right and uncheck...
Read more >What should I do if I published an app with a wrong ...
Republish the app with the proper name. There could be legal issues if any of the nodes in the package name are trademarked....
Read more >Package names
Effective Go provides guidelines for naming packages, types, functions, and variables. This article expands on that discussion and surveys names ...
Read more >aptitude search something # print only package names, no ...
To just print the package names use -F%p . aptitude search foo -F%p. Share.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@colemickens Known issue with the feeds currently. Publishing of the shared framework broke something. Chuan is telling me there is an aptly error on the repo side. Am following up with him. Will keep updated.
dotnet/cli#2043 Is fixing some of the deb versions inconsistencies (the wrong version is actually in that name), but the version being part of the name is part of the new side by side strategy
The older dotnet-dev, dotnet-nightly, and dotnet packages will all be cleaned up from the feed soon.
(cc @blackdwarf @piotrpMSFT for SxS)