Hi @rochishgvv_4077 , There is no way to continuously sync to a NuGet feed. You can create a "Connector" to your GitLab package registry, so that the packages are always on demand: https://docs.inedo.com/docs/proget-feeds-connector-overview You can download all the packages from a Connector using a Feed Downloader: https://docs.inedo.com/docs/proget-feed-importing You can configure GitLab to push to ProGet. We don't have any info on how to do that, however. Cheers, Alana

Hi @scroak_6473 , I'm not sure what the issue is and the errors are very peculiar, I assume that everything works, until you restore the database? Afte restoring database, there are a few paths I would check under Admin > Advanced Settings: Extensions.BuiltInExtensionsPath <--- should be C:\Program Files\ProGet\Extensions Extensions.ExtensionsPath <--- should be C:\ProgramData\ProGet\Extensions Extensions.CommonCachePath <-- should be C:\ProgramData\ProGet\ExtensionsCache Extensions.UseNewExtensionLoader <--- should be checked And then after edting those, make sure to restart the web.

Hi @jchitel_9895 , Thanks for the additional info! We "moved" your new topic back to this one, since we link these on this page in the docs and want to keep everything in one place: https://docs.inedo.com/docs/proget-feeds-other-types Keep in mind that feed types are a significant initial and ongoing investment (it's a product in a product), and at first glance, Homebrew doesn't seem to make any commercial sense. First and foremost, there doesn't seem to be a market here. Homebrew itself isn't commercialized. They tried a Kickstarted from 2013, but it seems to remain a hobby-type project. Compare that to Chocolatey (which may be a little older, and also did a kickstarter I think) -- they now have a decent size fulltime staff now. But secondly (and on a technical level), there isn't a "Homebrew Repository" or "Homebrew Server" - as you mentioned, it's Git-based - which means all it's doing is cloning Git repositories, and probably using tags and specific repo layouts to determine packages. Cheers, Alex

Hi @NanciCalo, thank you for the details regarding the occurring issues. I will surely look up on the solution for the "Windows" file issue and review the updating option for BM version. Thank you for the fast response! Cheers, Mihajlo

Hi @osnibjunior, Glad to hear this is working now! I think you are right about the circular reference issue. That is most likely what caused the issue initially. Thanks, Rich

Hi @jimbobmcgee , The "Bad handshake" error is occurring (as you probably guessed) while trying to establish SSL tunnel. This basically occurs at the operating system level, and is usually a total mystery. The underlying error seems to be coming from SSPIWrapper.AcquireCredentialsHandle, and is just this: (0x8009030D): The credentials supplied to the package were not recognized I have absolutely no idea what that means, but... there's a ton of things I found via searching. A few articles are suggesting that it means lack of access to read the private key Maybe it's in the wrong folder (on the Otter server)? I think it needs to be in "Personal" folder of "Machine" certificates, but it sounds like it's definitely something wrong with Otter reading the certificate.... Let us now if you find out more! Hope that helps, Alana

Hi @MF-60085, Thanks for the data! We've found that the root cause this time is due to some duplicate rows in the original table, which for some reason was not created with any uniqueness constraints. We'll get this fixed in a prerelease version within a day or two.

Hi @guyk, Glad to hear it! Thanks, Rich

Hi @apxltd, Wow, that was fast... I noticed that this was apparently already implemented in 2023.5 (PG-2359). Just wanted to let you know that I tested this with 2023.6 and it works like a charm [image: 1685946867461-inedo-3717-proget-2023.png]

@jimbobmcgee said in Apply-Template adding unexpected CR newline chars: Without wanting to hold you to a particular date, what is the typical release timeframe? We're targeting BuildMaster 2023 for Q3/Q4 and Otter for Q4. We don't have any dates beyond that at this point. And it sounds like you understand quite well why we're not so keen to jump on making relatively easy changes - definitely a lot to consider. We have a lot of "product debt" like this and have learned to be a lot more cautious. That said, I think as long as it's documented it's probably okay. That's the hard part of course (writing docs) - but there's a Note attributes that can be added to explain things as well. cheers!

@apxltd said in OT - SSH Secure Credentials Private Key ed25519: Thanks for clarifying @philippe-camelio_3885. I see the issue in the code now. I think it's been this way for quite a while Thanks for your reply

Hi @jimbobmcgee, I fixed this via OT-493 FIX; Custom Server Targeting should be selectable if the script type is OtterScript. It was a regression in the job template editor. Am I right in saying that for server is only expected to work for Custom server targeting, though? Correct; as of Otter v3 it's no longer supported in other scenarios. And for server can take a scalar variable argument, such as... Also correct, so the code you shared should work!

@hwittenborn awesome! I'm not sure if you saw it yet, but we have a new API called the Common Package API; I hope to fold in Promotion, Repackaging, and Deployment under this so it can be consistent

Cool, thanks a ton for the quick response and getting the docs fixed! I'll send something in a new message if I get any other questions.

Hello, if the ProGet server is running (and didn't crash), and you don't see any errors on the ProGet server... then the issue is between the server and the client. You can try to trace this using a tool like Wireshare or Fiddler, but to be honest the error could be anything including a bad wifi/network connection. It's not PRoGet or chocolatey specific, so you can search broadly for "how to troubleshoot unable to connect to remote server" for lots and lots of tips on how to resolve such an error. Cheers, Alana

@apxltd; apologies for the delay; I did not get a notification. Essentially, it is a chicken-and-egg problem. Enabling key-based, non-interactive login was one of the things I was hoping to automate/remediate with Otter; instead it is currently a prerequisite to using Otter. The device is not a 'server' per se, but a third-party 'appliance' built on top of Linux. The device image itself comes prebuilt with keyboard-interactive auth (not password) enabled. Having Otter support keyboard-interactive seemed more beneficial to a wider audience, than trying to alter the appliance software.

I thought I was wrong

Hi @ForgotMyUsername , I can't reproduce #1, and I don't have enough details (specific error messages, stack traces, etc) to guess what the issue could be. Same for #2 -- I would need to see specific OtterScript and the errors you're getting to take a guess at where the problem is. One thing that would be helpful, if you could create step-by-step reproduction information. For example, Create application named TOM + JERRY Create PowerShell Script named XYZ etc... Short of that, stack traces and errors logs are really important. There are a lot of copmontents working together, and hard to guess based on general descriptions :) Cheers, Alana

@ForgotMyUsername great news, thanks for letting us know :)