Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login
    1. Home
    2. gdivis

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    gdivisG Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 0
    • Posts 152
    • Groups 2

    gdivis

    @gdivis

    inedo-engineer

    I'm a product engineer at Inedo.

    33
    Profile views
    152
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online
    Website inedo.com
    Location Inedo HQ

    gdivis Unfollow Follow
    inedo-engineer administrators

    Best posts made by gdivis

    • RE: Support for R and CRAN

      Thanks everyone for your interest in this. As @apxltd said, I'll be leading the effort on this. As the package format and repository system both seem relatively simple, I don't foresee too many technical challenges with adding this to ProGet, but there are a few things I'd like to make sure I understand right now:

      1. ProGet typically needs to understand versioning rules for packages (to show which is the latest, to do retention policies, etc). From what I've gathered, CRAN uses 2 or more integers separated by dots. Does anyone know if that's required universally, or if it's just a convention?
      2. CRAN doesn't appear to have a server-side repository API, instead just exposing a list of packages using HTML. Is my understanding correct here?
      3. Submitting a package to CRAN looks like it's only done manually using a form here. Is that right, or is there some other automated mechanism that is used?

      Also- we don't have any in-house R experts, so any (tentative) commitments to try out a prerelease version of ProGet with CRAN support would be very helpful in getting this feature out sooner :)

      Thanks!

      posted in Support
      gdivisG
      gdivis
    • RE: Proget 5.2.13 Upgrade Issue with Docker

      We've now reproduced this, and it turns out there's a regression in 5.2.13 with how config files are read which determine whether to use SQL Server or postgres. We have implemented a fix as PG-1614, which will be included in ProGet 5.2.14 (scheduled for release on Friday, October 18).

      For now, I'd recommend just reverting to 5.2.12 until the next version is available.

      Thanks to all who reported this!

      posted in Support
      gdivisG
      gdivis
    • RE: Running Otter plan from Romp Install command line

      I'll see if we can get a new version built that includes an option to output the full log to the console after a job completes. In the meantime, you could call romp with a simple batch script like:

      romp install %1
      romp jobs logs
      

      Then invoke it with: romp.bat <packageName>

      Let me know if that's helpful!

      posted in Support
      gdivisG
      gdivis
    • RE: Delete Files / Directory in Asset Directories via PS/CLI/API

      Hi Dennis,

      Thanks for the feedback! You should be able to delete files/folders using the Asset Directory Delete API. Using curl, it should look something like this:

      curl -X POST http://proget/endpoints/<AssetDirName>/delete/<path to directory>
      

      We are actually focusing on Asset Directory improvements for the upcoming ProGet v6.0 release, so if you see any gaps or problems be sure to let us know!

      -Greg

      posted in Support
      gdivisG
      gdivis
    • RE: upack version ranges issues

      Hi,

      Thanks for the bug report! We've logged and fixed these as PG-2098 and PG-2099. Note that due to limitations in how that dependency table is built, it's nontrivial to have it take you to the latest package that satisfies the given range if it has an exclusive upper bound - but we have changed it to prefer linking to the upper version number if one is present.

      -Greg

      posted in Support
      gdivisG
      gdivis
    • RE: Bugs with Proget handling of simple repository APIs

      Hi @itops_6398,

      Thank you for the bug report. I've logged this as PG-2507, and we will likely have it fixed for the next release of ProGet 2023.20, scheduled for October 13. If the fix or testing turns out to be more than expected, it may get deferred to the following release, but I don't expect that to be the case here.

      posted in Support
      gdivisG
      gdivis
    • RE: Bugs with Proget handling of simple repository APIs

      Sure. I've logged that change as PG-2508. It should be easy enough to make that URL configurable in ProGet.

      posted in Support
      gdivisG
      gdivis
    • RE: pgutil not working in CI/CD yaml pipeline

      Hi @pbinnell_2355,

      Looks like the example code was incorrect. I've updated it. When a dotnet tool is installed globally, you run it by just running the tool name directly, so pgutil instead of dotnet pgutil

      Hope this help!
      -Greg

      posted in Support
      gdivisG
      gdivis
    • RE: Incomplete proget debian connector local index file for ubuntu noble-backports dist

      Hi @dimas,

      I've looked into this and it appears that restricted and multiverse in noble-backports do not actually have any packages in their indexes. It's a quirk of how these connectors are implemented in ProGet that components with no packages indexed are omitted from the output index. Is this causing a problem for you? We can look into changing this behavior, but it likely won't be a trivial fix.

      -Greg

      posted in Support
      gdivisG
      gdivis
    • RE: 0 byte download when using pgutil assets/packages download in github workflow

      Hi @layfield_8963,

      Looks like this was just a simple bug preventing output from being written when stdout has been redirected. It's now fixed in pgutil 2.1.1.

      Thanks for the update!
      -Greg

      posted in Support
      gdivisG
      gdivis

    Latest posts made by gdivis

    • RE: 500 Error after upgrade

      Hi @stephen.schaff,

      This was actually a regression that has been fixed by PG-3432, which is included in the release we just now deployed. Although it primarily affects docker blob replication, there are also situations where it can prevent blob uploads from other sources as well. If you upgrade to 2026.17, the issue should resolve.

      -Greg

      posted in Support
      gdivisG
      gdivis
    • RE: ProGet 2026.16: Docker connector throwing exceptions

      Hi @Nils-Nilsson,

      It is a bug unfortunately. It's logged as PG-3432, and we have a SQL script attached to that issue that will resolve the problem. We will likely do another release soon to include this as well.

      -Greg

      posted in Support
      gdivisG
      gdivis
    • RE: Title: BuildMaster 26.0.2 (PostgreSQL): Scripts list page leaks a DB connection per visit; Native API calls fail with missing __BuildMaster_GetStoredProcInfo

      Hi @m.u,

      We've actually found and fixed that connection leak internally this week. It's logged as PG-4026 and we are including the fix in BuildMaster 2026.3 tomorrow.

      I've logged the issue with the Native API as PG-4027, and it looks to be a trivial fix that we can also get in tomorrow's release, but I will let you know if it ends up taking longer.

      Thanks for reporting the issues!

      -Greg

      posted in Support
      gdivisG
      gdivis
    • RE: ProGet database issues after upgrading to 2026.11 and migrating to Postgres

      We've scheduled PG-3386 to resolve the slow multi-build analysis on Postgres. It will be included in ProGet 2026.12, which is scheduled for release on Oct 2.

      posted in Support
      gdivisG
      gdivis
    • RE: ProGet database issues after upgrading to 2026.11 and migrating to Postgres

      Hi @jw,

      The purge failure is unexpected, but I've seen something similar in the past with from an imported SQL Server database that had some invalid data in it. For now, leaving those IDs in the database shouldn't affect your performance. We'll look into adding more robust detection of invalid data to the cleanup page. Regardless, the order of cleanups performed shouldn't matter.

      PackageAnalyzer does quite a bit more in ProGet 2026, so I would expect it to take a bit longer, but not that much.

      I'll bring both of these up with the team and post again here with an update.

      -Greg

      posted in Support
      gdivisG
      gdivis
    • RE: Invalid Content-Range header for HTTP range requests when downloading files from asset directories

      Hi @joris.guex,

      Sorry for the delay - I've been out of the office for a bit.

      I've logged this as PG-3379, scheduled for the next release of ProGet 2026.12 on Oct 2. I haven't looked at the code yet, but it should be another trivial fix to bring this fully up to spec.

      Thanks!
      -Greg

      posted in Support
      gdivisG
      gdivis
    • RE: ProGet cannot correctly generate valid Release-File- and Package-File-Url for the Debian feed if the distribution contains slashes.

      Hi @geraldizo_0690,

      We have reproduced this and are testing the fix now. It will be included in the next release (ProGet 2026.11 on Sep 18). The tracking issue is PG-3370.

      Thanks for reporting the problem!
      -Greg

      posted in Support
      gdivisG
      gdivis
    • RE: [ProGet/PGUtil] Bug: When setting feed property only the last one will be retained.

      Hi @nils-nilsson,

      We've investigated and this is definitely a bug in the feed management API. Unfortunately that API is pretty rough, and this is not at all the trivial fix it ought to be. I've logged the issue as PG-3369 and scheduled it for ProGet 2026.12, which is the release after next, currently targeted for Oct 2.

      -Greg

      posted in Support
      gdivisG
      gdivis
    • RE: Invalid Content-Range header for HTTP range requests when downloading files from asset directories

      Hi @joris.guex

      You're right! It looks like ProGet is reporting the second value of the range as if it was an exclusive bound rather than inclusive. Somehow it has been like this for years.

      Anyway, it looks to be a trivial fix, so we should be able to get this in this Friday's release of 2026.9. I've created PG-3350 as the tracking issue for it.

      Thanks for reporting the problem!
      -Greg

      posted in Support
      gdivisG
      gdivis
    • RE: Request to update PSCall documentation for getting data back from a ps1 asset

      Glad I could help!

      We'll get that documentation updated as well.

      posted in Support
      gdivisG
      gdivis