Navigation

    Inedo Community Forums

    Forums

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    1. Home
    2. gdivis
    3. Best
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    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
      gdivis
      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
      gdivis
      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
      gdivis
      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
      gdivis
      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
      gdivis
      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
      gdivis
      gdivis
    • RE: pgutil showing incorrect buildnr

      That's a display issue in pgutil. It's not supposed to show the build number as part of the version at all, so we'll fix that. Note that we do include the build as part of the tag, but the actual release title on GitHub is just 2.1.1, 2.0.6, etc. Thanks for reporting this!

      posted in Support
      gdivis
      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
      gdivis
      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
      gdivis
      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
      gdivis
      gdivis
    • 1 / 1