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.

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

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

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

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

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

Glad I could help!

We'll get that documentation updated as well.

Hi @brandon_owensby_2976,

Yes, that actually does wire things up with OtterScript, though I just realized I forgot to include a sample for how to actually invoke that script from OtterScript...

PSCall2 MyScript.ps1
(
    Parameters: %(inputvalue: Hello, resultingtext: outputvar)
);

Log-Information MyScript returned $outputvar;

The Parameters argument is meant to handle anything declared as an input/output value in the script's header. Note that for outputs you actually supply the name of the OtterScript variable to assign as the parameter value. For the record, I agree that this is all very confusing and we could certainly do a better job in the UI and docs. I believe the original goal when we added PSCall2 was to make the script parameters more discoverable, but at least as it works now, it has had the opposite effect.

That crazy stuff with the prefix is the mechanism it uses behind the scenes to capture output values that are declared in that parameters header or in the OuputVariables argument.

Does using this kind of header and PSCall2 invocation work at all for you? There's other things that could go wrong with marshalling values to/from PowerShell, but this ought to at least get you outputs without having to jump through those extra hoops.

-Greg

Hi @brandon_owensby_2976,

You're right that this is not very intuitive, and there are some outstanding issues we intend to fix in BuildMaster 2026. Generally, the best way to get all of this wired up right now is to have an Augmented Help header in the PowerShell script like this:

<#
.SYNOPSIS
    Appends world.

.AHPARAMETER inputvalue
    Input string

.AHPARAMETER resultingtext(output)
    Will be set to the resulting text

#>

param ([string]$inputvalue, [ref]$resultingtext)

$resultingtext = $inputvalue + " world" 

The key here is the [ref] specifier in the param block and the (output) specifier in the .AHPARAMETER augmented help header above.

For scripts without a param/Augmented Help header, you should be able to use the InputVariables and OutputVariables parameters of PSCall2 instead.

This is unfortunately missing from the docs at the moment, but before getting that updated I'd like to see if we can streamline or improve this to make it more intuitive.

Does this help at all? We're happy to work with you to improve this before the 2026 release.

Thanks!
Greg

Hi @Nils-Nilsson,

We've released pgutil 2.4.0 that has the audit command, along with a couple new commands under containers for adding/deleting tags. Note that it requires APIs added in ProGet 2026.3 or later.

Give it a try and let us know what you think.
-Greg

Hi @appplat_4310,

It shouldn't be a problem to get this in today's release (2026.2). I've logged it as PG-3295.

-Greg

Hi @Ashley,

It turns out that we just weren't reading upload-time from the upstream json when using the simple API, so this was pretty trivial to fix and we'll certainly be able to include it in tomorrow's release. Here's the abbreviated result of a quick local test I did after making the fix (also after fixing the issue with the duplicated versions):

{
  "meta": {
    "api-version": "1.1"
  },
  "name": "psycopg",
  "versions": [
    "3.0b1",
    "3.0",
    "3.0.1",
    "3.0.2",
    "3.0.3",
    "3.0.4",
    "3.0.5",
    "3.0.6",
    "3.0.7",
    "3.0.8",
    "3.0.9",
    "3.0.10",
    "3.0.11",
    "3.0.12",
    "3.0.13",
    "3.0.14",
    "3.0.15",
    "3.0.16",
    "3.0.17",
    "3.0.18",
    "3.1",
    "3.1.1",
    "3.1.2",
    "3.1.3",
    "3.1.4",
    "3.1.5",
    "3.1.6",
    "3.1.7",
    "3.1.8",
    "3.1.9",
    "3.1.10",
    "3.1.11",
    "3.1.12",
    "3.1.13",
    "3.1.14",
    "3.1.15",
    "3.1.16",
    "3.1.17",
    "3.1.18",
    "3.1.19",
    "3.1.20",
    "3.2.0",
    "3.2.1",
    "3.2.2",
    "3.2.3",
    "3.2.4",
    "3.2.5",
    "3.2.6",
    "3.2.7",
    "3.2.8",
    "3.2.9",
    "3.2.10",
    "3.2.11",
    "3.2.12",
    "3.2.13",
    "3.3.0",
    "3.3.1",
    "3.3.2",
    "3.3.3",
    "3.3.4"
  ],
  "files": [
    {
      "filename": "psycopg-3.0b1-py3-none-any.whl",
      "url": "http://localhost:5000/pypi/snake/download/psycopg/3.0b1/psycopg-3.0b1-py3-none-any.whl",
      "requires-python": ">=3.6",
      "size": 131830,
      "upload-time": "2021-09-03T21:34:46.638478Z",
      "hashes": {
        "sha256": "fd510caaaa90aec11781c0581a8a03f847e35925db6de293404db87d625a44e8"
      }
    },
    {
      "filename": "psycopg-3.0b1.tar.gz",
      "url": "http://localhost:5000/pypi/snake/download/psycopg/3.0b1/psycopg-3.0b1.tar.gz",
      "requires-python": ">=3.6",
      "size": 108312,
      "upload-time": "2021-08-30T04:25:06.027667Z",
      "hashes": {
        "sha256": "90188a415f2132eabccfa58ae41330d3bfc1c5c410add4d6194e783521478189"
      }
    },
    {
      "filename": "psycopg-3.0-py3-none-any.whl",
      "url": "http://localhost:5000/pypi/snake/download/psycopg/3.0/psycopg-3.0-py3-none-any.whl",
      "requires-python": ">=3.6",
      "size": 140812,
      "upload-time": "2021-10-12T16:20:12.084578Z",
      "hashes": {
        "sha256": "65b9fb8838dae61040ad3e0cfc184d4ffd17f740ef4c0353d76050a6eb061a9c"
      }
    }
    //...SNIP
  ]
}

Offline installers are available here which you can use to upgrade these older versions:
https://my.inedo.com/downloads/installers

We've tracked this down to an issue with native symbol files indexed in a PostgreSQL database. It will be fixed by PG-3243 in ProGet 2025.24, scheduled for release tomorrow (20 March 2026).

Packages with affected symbol files should be re-uploaded to ProGet following this release to resolve the lookup issue.

You can test the fix from this prerelease image: proget.inedo.com/productimages/inedo/proget:25.0.22-ci.4

In this version, it will automatically recreate each of those databases the next time it needs an update, and after that you should no longer see this unbounded growth. Let us know if you're still seeing a problem!

Hi @geraldizo_0690,

We've reproduced this and have a fix in internal testing as PG-3225. An incorrect index is causing the local connector database index to grow much larger than it should, and this effect is compounded in frequently updated repos like Kali.

We are currently testing the fix internally and will have it included in Friday's release of ProGet 2025.22. If you'd like to test the fix yourself soon, I can make a prerelease image available to you.

Thanks!
-Greg

Hi @Sigve-opedal_6476,

I haven't been able to reproduce this in a Rocky 9 test environment. After setting up the feed and connector in ProGet I ran dnf install zabbix-sql-scripts, and then repeated the test a few times with different versions and variations on formatting the versions. I also tried with cached and uncached packages. I was able to get a 404 to happen one time, but it was due to the upstream repo returning a 404 at the correct URL - which then worked the next time it was tried.

Is this happening consistently for you?

Hi @udi-moshe_0021,

It actually is already bundled with the installer and should have been run before ProGet's installation. I'm not sure why it would have failed, but we'll add more checking to at least provide a warning if this fails in the future.

Thanks for letting us know what the problem was!

Thanks! This will be fixed in today's release of ProGet 2025.17 as PG-3187.

Just to keep everyone informed: We are pretty sure we have the underlying issue resolved as of PG-3158. We were incorrectly supplying the wrong InverseQ value to OpenSSL when reading a key from an existing file - so this impacted both uploaded keys and keys from previous ProGet versions. This will be included in next Friday's 2025.15 release, but is available right now at proget.inedo.com/productimages/inedo/proget:25.0.15-ci.4 if anyone would like to test it immediately.