Navigation

    Inedo Community Forums

    Forums

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

    gdivis

    @gdivis

    inedo-engineer

    I'm a product engineer at Inedo.

    13
    Reputation
    128
    Posts
    31
    Profile views
    0
    Followers
    0
    Following
    Joined Last Online
    Website inedo.com Location Inedo HQ

    gdivis 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
      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

    Latest posts made by gdivis

    • RE: ProGet bug - Regression: RPM feed repodata broken since 25.0.8

      Any change to feed that could affect a package is supposed to trigger this, and that does include deleting a package, adding a package, or a detected change in any repodata files from any associated connectors. What happens is any operation like that sets an index dirty flag for the feed, and if a request is made for it after that, it is rebuilt. There is also a 30 second delay before this can get triggered, so if you:

      • upload/delete a package
      • wait 30s
      • get repodata/repomd.xml

      It should show an updated timestamp and revision.

      We are currently moving to more of a job-based system for these index rebuilds, which also will provide better visibility into their creation and allow for manually triggering them. We're starting this process with Debian feeds since those exhibit the most problems with the current system, but plan to extend it to rpm and apk as well.

      Anyway, if you're not seeing it update even after the 30s delay then there must be some other issue at work, so we'll need to dig into that.

      posted in Support
      gdivis
      gdivis
    • RE: ProGet bug - Regression: RPM feed repodata broken since 25.0.8

      Hi @felfert,

      Apologies for the delay, I was out of the office recently. We tested this one quite a bit before release and didn't see any cases of the index not getting updated. Of course, I believe you that it is happening, but it's not something I've been able to reproduce. One thing to note is that those repodata files in storage only get updated on-demand - so something would have to actually make a request for the index to get ProGet to rebuild it (this is something that we are planning to change in a separate issue, but that is how it works currently).

      Of course, we'd be happy to do some testing with your packages specifically if you'd like to upload some - just open a ticket at https://my.inedo.com/tickets/new which does allow file attachments. Ignore the header that says it's for paid users only; we'll associate it with this forum post.

      -Greg

      posted in Support
      gdivis
      gdivis
    • RE: ProGet bug - Regression: RPM feed repodata broken since 25.0.8

      We've now fixed this and several other related RPM issues as PG-3094, scheduled for release this Friday in ProGet 2025.9. Thanks again for the bug report!

      posted in Support
      gdivis
      gdivis
    • RE: Buildmaster fresh install / Unable to clone repository

      Hi @carsten_1879,

      Thanks for trying it out. It is new, and has not been tested as much against older repositories. That said, we've reproduced this error and it's now fixed in the latest build - buildmaster:25.0.0-ci.28 if you would like to try it again. It's caused by older repos that don't support offset deltas being transmitted during a clone or fetch. Small repos that we used for testing ADOS so far were not large enough to have deltas at all, so those worked. So far as I can tell, the repository name containing a dot doesn't have any effect.

      Thanks!
      -Greg

      posted in Support
      gdivis
      gdivis
    • RE: Bad links.json file in buildmaster container

      Hi Marc,

      Thanks for the note! That file is actually a sort of cross-platform way of storing symbolic links. BuildMaster also includes all the binaries needed for agents on both Windows and Linux, including .net runtimes for all three. In order to save space we deduplicate identical binaries from the agents. We use a simple json file instead of proper symlinks because we use the same file on Windows/Linux and it's easier this way. All the paths in the file have historically used Windows path separators due to how we generate it, and we convert those in BuildMaster at runtime to the proper format.... or at least we were supposed to. At some point there was a regression added that caused this to not happen when updating from Linux.

      Anyway, this will be fixed as BM-3981 in the next release :)

      posted in Support
      gdivis
      gdivis
    • RE: ProGet Docker Compose Upgrade Issues

      There was in issue with Docker container initialization due to some of the updated startup code in ProGet 2025 - it's now been resolved, and if you pull the proget:25.0.1 it should work.

      Hope this helps!

      posted in Support
      gdivis
      gdivis
    • RE: Proget 2024.37(8) to 2025 Fails to Upgrade

      This looks like it was caused by us packaging an old version of Inedo Hub as part of the offline installer. We'll have it fixed for the 2025.1 release which will go out this week.

      posted in Support
      gdivis
      gdivis
    • RE: Arm/MacOS build of PGutil

      Hi @layfield_8963,

      We've added osx-arm64 as another target, and we'll start deploying that along with the other binaries. We'll probably push out a new release today or tomorrow.

      Thanks!

      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-postgres test does not survive container disposal/recreation

      Hi Fritz,

      We appreciate the feedback on this! ProGet 2025 will indeed have a separate dedicated mount for the database, but we didn't include this in the preview. As to the other issues, yes we do have a supervisor that attempts to start postgres and perform a clean shutdown on container stop... but there are some bugs we are working through, likely made worse by the ownership issues you discovered.

      These concerns will absolutely be addressed before launch.

      Again, thanks for trying it out and please let us know of any other issues you find or suggestions you may have!

      -Greg

      posted in Support
      gdivis
      gdivis