Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login
    1. Home
    2. stevedennis
    3. Posts

    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!

    stevedennisS Offline
    • Profile
    • Following 0
    • Followers 1
    • Topics 0
    • Posts 532
    • Groups 2

    Posts

    Recent Best Controversial
    • RE: Support for NotAutomatic/ButAutomaticUpgrades headers in Debian feed Release files

      Hi @geraldizo_0690,

      Thanks for the pointers -- now as an FYI, these settings would have to be a Feed-level setting, but the drop-downs would be the same.

      FYI, here's the code we use to generate the Release file --- I'm not sure what those other header values do, but we probably wouold just want to add the two you suggested.

      What do you think?

      I suspect this will be a quick, opt-in change!

      private void WriteReleaseFile(Stream output)
      {
          using var writer = new StreamWriter(output, InedoLib.UTF8Encoding, leaveOpen: true) { NewLine = "\n" };
          writer.WriteLine($"Suite: {this.Distro}");
          writer.WriteLine($"Codename: {this.Distro}");
          writer.WriteLine(FormattableString.Invariant($"Date: {this.Generated:ddd', 'dd' 'MMM' 'yyyy' 'HH':'mm':'ss' UTC'}"));
      // NotAutomatic: yes  <-- add here
      // ButAutomaticUpgrades: yes <-- add here
          writer.WriteLine($"Architectures: {string.Join(' ', this.indexes.Select(i => i.Architecture).Distinct(StringComparer.OrdinalIgnoreCase))}");
          writer.WriteLine($"Components: {string.Join(' ', this.indexes.Select(i => i.Component).Distinct(StringComparer.OrdinalIgnoreCase))}");
      
          var desc = FeedCache.GetFeed(this.feedId)?.Feed_Description;
          if (!string.IsNullOrWhiteSpace(desc))
              writer.WriteLine($"Description: {desc.ReplaceLineEndings(" ")}");
      
          writeHashes("MD5Sum:", i => i.MD5);
          writeHashes("SHA1:", i => i.SHA1);
          writeHashes("SHA256:", i => i.SHA256);
          writeHashes("SHA512:", i => i.SHA512);
      
          void writeHashes(string name, Func<IndexHashData, byte[]> getHash)
          {
              writer.WriteLine(name);
              foreach (var i in this.indexes)
              {
                  writer.WriteLine($" {Convert.ToHexString(getHash(i.Uncompressed)).ToLowerInvariant()} {i.Uncompressed.Length,16} {i.Component}/binary-{i.Architecture}/Packages")
                  writer.WriteLine($" {Convert.ToHexString(getHash(i.GZip)).ToLowerInvariant()} {i.GZip.Length,16} {i.Component}/binary-{i.Architecture}/Packages.gz");
              }
          }
      }
      
      posted in Support
      stevedennisS
      stevedennis
    • RE: Bitbucket authentication issues

      Hi @brandon_owensby_2976 ,

      It sounds like you're on the right rack with troubleshooting; the issue is definitely on the server-side in this case, so I asked ChatGPT. Who knows if any of this is accurate, but...

      This is a very common situation with older versions of Bitbucket Server (especially pre-6.x / pre-7.x era, but even up to some 7.x versions in certain setups).

      The REST API (e.g. /rest/api/1.0/...) and the Git Smart HTTP protocol (/scm/.../info/refs, /git-upload-pack, etc.) are handled by different authentication filters in Bitbucket Server.

      Most likely you're using a Personal Access Token / HTTP Access Token (most frequent cause in older versions). In many Bitbucket Server versions (especially ≤ 7.17–7.21), HTTP access tokens were designed mainly for REST API and did not work reliably (or at all) for Git over HTTPS in many cases.

      As a workaround , you need to use a real username + password (or username + app password if 2FA is on) for Git operations

      We've seen similar in really old version of ADO, GitHub, etc, where API tokens wouldn't work for Git.

      Anyway, I would try that - at least from the curl side of things. And maybe upgrading will help as well. If it works, then you'll likely only be able to use a Generic Git repository with a real username/password -- and just create a special builds user which effectiveely acts like an APi key.

      Cheers,
      Steve

      posted in Support
      stevedennisS
      stevedennis
    • RE: Suggestion: Show total container image size

      Hi @Stephen-Schaff,

      It seems pretty easy to add these up and display them on the screen! I suppose the "hard part" is the UI...

      A "Total" line doesn't seem to look right. And it seems like too little information to put in one of those info-boxes. "Total Size: XXXX MB" at the bottom just looks incomplete.

      Any suggestions? I'm struggling a bit to see how it could be displayed without looking a little out of place... and since it was your idea I figured I'd ask ;)

      Thanks,

      Steve

      posted in Support
      stevedennisS
      stevedennis
    • RE: Support for NotAutomatic/ButAutomaticUpgrades headers in Debian feed Release files

      Hi @geraldizo_0690,

      Hello,

      I'm not all that familiar with Debian/APT... but I briefly researched this, and it seems like this involves adding values like this at the top of the Release file like this:

      NotAutomatic: yes 
      ButAutomaticUpgrades: yes
      

      Is that it really? And this setting would impact the entire feed... but have no real relation/impact to connectors or packages?

      If that's the case, how would you envision configuring this? I'm thinking on the Feed Properties page, but perhaps as a checkbox? How do other products/tools do it in your experience?

      Thanks,
      Steve

      posted in Support
      stevedennisS
      stevedennis
    • RE: Bitbucket authentication issues

      Hi @brandon_owensby_2976 ,

      Thanks for the feedback. Based on what you described, it sounds like...

      • BitBucket Server API is working fine
      • Git API is not working due to a failed/failing authentication challenge

      You were able to confirm this with the "Generic Git Repository" also not working. If you were to do a curl -I -u USERNAME;APIKEY https:/.../.git you would most certainly get a 401 response as well.

      Anyway that's where I would start -- try to figure out why the Git API is not accepting the credentials. It's most likely related to permissions on theh key, but it's really hard to say... just a guess.

      Thankks,
      Steve

      posted in Support
      stevedennisS
      stevedennis
    • RE: Migrate Feed from C drive to another drive

      Hi @Julian-huebner_9077 ,

      Here's some information on file storage paths:
      https://docs.inedo.com/docs/proget/feeds/feed-overview/proget-feed-storage

      Long story short, if you modify Storage.PackagesRootPath under Admin > Advanced Settings and move your files as needed, then it should work just fine.

      Thanks,
      Steve

      posted in Support
      stevedennisS
      stevedennis
    • RE: BuildMaster fails to return TeamCity build configs

      Hi @kquinn_2909 ,

      We haven't forgotten about this; the issue is trying to figure out steps to reproduce it based on the information we have... considering it works on our test instance and all. We may consider putting some more debugging code in, though figuring out how to expose that in this context is a little challenging.

      Just as a sanity check though, do you have a project that doesn't have a "space" in the name? I want to make sure this isn't something really simple as WebProjects%20Replicator vs WebProjects_Replicator.

      The other idea is authentication/authorization, though I would imagine you would get an error accessing the project instead of no builds.

      Thanks,
      Steve

      posted in Support
      stevedennisS
      stevedennis
    • RE: [ProGet] Recently Published Rule

      Hi @jstrassburg_8563,

      if the resolved version that npm i underscore chose was released in the blocking period, the npm command would 400?

      If you have "Block Noncompliant Packages" enabled (which we generally don't recommend) and you have a rule that new packages are complaint, then the npm command would most certainly give some kind error.

      You will probably see a 400 code, but I don't think it will display the message that's sent by ProGet (i.e. "package blocked due to...")? The real issue comes with a large dependency tree, and it'll be hard to know what exactly the issue is.

      As such, we recommend running pgutil builds scan/audit in your CI/CD pipelines instead of blocking. This will produce a much easier to understand report, and even allow you to bypass issues reported on a case-by-case basis.

      Thanks,
      Steve

      posted in Support
      stevedennisS
      stevedennis
    • RE: Helm connector with relative url

      Hi @sigurd-hansen_7559 ,

      Thanks for pointing me to the repository; I was able to reproduce this, and it will be fixed via PG-3194 in the next maintenance release (scheduled for Friday).

      Thanks,
      Steve

      posted in Support
      stevedennisS
      stevedennis
    • RE: Not able to download Docker images that doesn't have / in it

      Hi @toseb82171_2602,

      In Docker, images must have a namespace. When they don't, the Docker client will transparently append library/ to those namespaces. In general, this behavior is not desirable, and it's recommended to use library/python or, in a ProGet context, myproget.corp/mydockerfeed/library/python.

      That said, there is a setting on the connector that may help resolves such images, but these images can be problematic even with that.

      AS for extending the trial, no problem - you can actually do this yourself on my.inedo.com, on the day of expiry. Of course, please contact us if you run into any issues or have licensing questions.

      Thanks,
      Steve

      posted in Support
      stevedennisS
      stevedennis
    • RE: How do i clone a feed (packages) into a new feed?

      Hi @nachtmahr,

      Yes, that's what I would reommend doing -- using the internal storage path. Just make sure to NOT select the option to delete the files and make sure to select "search subdirectories" so everything will be imported.

      Cheers,
      Steve

      posted in Support
      stevedennisS
      stevedennis
    • RE: How do i clone a feed (packages) into a new feed?

      Hi @nachtmahr ,

      There is no "clone" method per se, but you can accomplish this by bulk-importing packages into a new feed: https://docs.inedo.com/docs/proget/feeds/feed-overview/proget-bulk-import

      Cheers,
      Steve

      posted in Support
      stevedennisS
      stevedennis
    • RE: [ProGet] Recently Published Rule

      Hi @tim-vanryzin_8423 ,

      Great question on developer experience! We're very curious to learn that ourselves, so please let us know as you implement it.

      First and foremost, if you haven't already, check out the Recently Published & Aged Packages rules blog article to see how this works and our current advice. FYI - we are likely going to change the best practices guidance in 2026 to discourage download blocking.

      From an API/technical standpoint, it's simply not possible to "hide" the fact that 1.12.15 is the latest version. So, if you have a connector, ProGet will report the latest version as reported by the connector.

      But even it were technically possible, there's no simply great developer experience here. Keep in mind that most never look at the ProGet ui -- they configure things once, and forgeet about it.

      So really, it's just a question of when you want the developer to find out they can't use Xyz-1.12.15. Here are the general options:

      • Manual Curation (no connectors) - it's always going to be on nuget.org / npmjs.org, so even if you manually curate every page in ProGet, they'll know it exists and will be confused why it's not on ProGet; they may not even know who to ask
      • Download blocking - you could simply block downloads of newest packages, but that's just going to look like random "400 errors" to developers and they will become frustrated
      • Build Auditing - run pgutil builds audit on your build server, and you can see if the packages are noncompliant; this is where we are shifting our advice, as a failed build at that stage will be so much more obvious than a 400 buried in a package restore step

      Ultimately this requires training developers to use lock files and not always get latest. That's why we are shifting to pgutil builds audit -- it's almost self-training. When their builds fail, they will see the reason clearly and should be able to adjust their code/configuration to not use a non-compliant version.

      -- Dean

      posted in Support
      stevedennisS
      stevedennis
    • RE: [ProGet] How do I specify Storage.PackagesRootPath in configuration?

      Hi @jonathan-werder_8656 ,

      Thanks for clarifying! I'll be honest, I had no idea where you were getting configuration files in the first place... and I forgot that was ever a thing. Sorry about that.

      Anyway, I don't think that this has worked in years, and it's most definitely not something we'd recommend today. We'll try to track it down and remove it in the docs / help text.

      For your use case (automated installation) just use pgutil settings to set that value.

      Thanks,
      Steve

      posted in Support
      stevedennisS
      stevedennis
    • RE: Support for RPM module streams?

      Hi @henderkes,

      I'm not familiar with module streams, but if you tried it in ProGet and it didn't work then likely not? It sounds like a different API/endpoint, but I haven't researched it at all.

      However, based on how you described it ("removed from Fedora 39"), it sounds like one of those "good but old" technologies that don't make sense for us to implement.

      Thanks,
      Alana

      posted in Support
      stevedennisS
      stevedennis
    • RE: [ProGet] How do I specify Storage.PackagesRootPath in configuration?

      Hi @jonathan-werder_8656 ,

      You can set this value under Admin > Advanced Settings.

      Thanks,
      Steve

      posted in Support
      stevedennisS
      stevedennis
    • RE: Connector for accessing Jfrog pypi feed

      Hi @pmsensi ,

      You'd need to run through a proxy like Fiddler or ProxyMan, which can capture the outbound / inbound traffic. Or if you provide us with a URL/API key we might be able to play around and attach a debugger. You could always create a free trial or something and set it up that way.

      First thing that comes to mind is that your endpoint is incorrect and you may need to "play around" with the URL. Typically it's like this:

      • endpoint is https://server.corp/path/my-pypi
      • index file is https://server.corp/path/my-pypi/simple
      • ProGet automatically appends /simple unless you specify otherwise on Advanced

      The "Simple " endpoint is just a list of HTML like <a href="...">. That's what ProGet/connectors/pypi follow.

      Thanks,

      Steve

      posted in Support
      stevedennisS
      stevedennis
    • RE: PHP Composer feed connect to vcs type repository or how to upload

      Hi @ayatsenko_3635, @dubrsl_1715,

      Thanks for the feedback and continued discussion.

      So, our Composer feed is relatively new, so we are open to exploring new ideas. One option might be to do an "import" of packages into ProGet, similar to how we handle connectors in Terraform feeds. But that's something that could also be done with a script, so we'd want to see what that looks like as a prototype.

      That said, we definitely can't implement "content pointers" to Git repositories. The Git-based "package" model is not only outdated but it has several "fatal" Software Supply Chain problems.

      The biggest problem, by far, is that package content is hosted by a third party (i.e. GitHub) and managed by another third party (i.e. the repository owner). At any time, a package author or the host can simply delete the repository and cause a major downstream impact - like the infamous left-pad incident in npm.

      This is why other package ecosystems have adopted a "read only" package repositories and disallow deletes (except for rare cases like abuse). Once you upload a package to npmjs, nuget, rubygems, etc. -- it's permanently there, and users can always rely on that being the case.

      That's simply not possible with Git-based "packages". The "content pointer" must be updated periodically updated, such as if the author decides to move the Git repo to GitLab, Gitea, etc. Now you no longer have a read-only package repository, but one that must be editable. Who edits? Are they tracked? What edits are allowed? Etc.

      There are several of other issues, especially with private/organizational usage, like the fact that there's no reasonable way to QA/test packages (i.e. compared to using a pre-release/repackaging workflow) and that committing/publishing are coupled (i.e. you tag a commit to publish it). This makes governance impractical.

      And that's not to mention the fact that there's no real way to "cache" or "privatize" third-party remote Git repositories. Unless, of course, you mirror them into your own Git server... which is technically challenging, especially if the author changes hosts.

      We first investigated feeds years ago, but they didn't have package files at the time -- only Git repository pointers. Like Rust/Cargo (which used to be Git-based, and still technically supports Git-based packages), we anticipate this same maturity coming to Packagist/Composer as well.

      So while we certainly understand that this is a workflow shift, it's a natural evolution/maturation of package management. Likewise, it took decades for the development world to shift from "file shares" and legacy source control to "Git", but that's what everyone has standardized on.

      That's the world ProGet operates in, so it might be a bit "too far ahead", or we might be misreading the tea leaves - but a "package mindset" is a requirement in using ProGet. But hoepfully we can make that easier, possibly with exploring "package imports" or something like that.

      Cheers,
      Steve

      posted in Support
      stevedennisS
      stevedennis
    • RE: Known licenses are shown as unknown

      Hi @frank-benson_4606 ,

      Thanks for clarifying, that makes sense.

      I'm afraid that ProGet does not "crawl" the parent artifacts for metadata; we had considered it, but it's rather challenging to do from an engineering standpoint, difficult to present crawler errors, and fairly uncommon.

      Thanks,
      Steve

      posted in Support
      stevedennisS
      stevedennis
    • RE: PHP Composer feed connect to vcs type repository or how to upload

      Hi @dubrsl_1715 ,

      Thanks for the clear explanation; I'm afraid your best bet here is to "take the plunge" and adopt package management best practices. A key tenet being a "self-contained archive file with a manifest" that is read-only and "cryptographically sealed" (i.e. hashed).

      A "pointer to a Git commit" seems convenient at first, but there's a good reason that many ecosystems (including Composer) have moved away from it -- ultimately it's just not scalable and doesn't handle team workflows very effectively.

      This will likely involve updating your composer.lock files and also the way you publish packages. In general, your process for creating a new version of a PHP packages should look something like:

      1. Checkout code
      2. Modify composer.json file with a version number
      3. Package the file
      4. Publish to ProGet

      As you get more mature, you can get into pre-release versioning and repackaging.

      Hope that helps,

      Steve

      posted in Support
      stevedennisS
      stevedennis
    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 26
    • 27
    • 4 / 27