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

    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!

    felfertF Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 12
    • Posts 62
    • Groups 0

    felfert

    @felfert

    8
    Profile views
    62
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online
    Location Germany

    felfert Unfollow Follow

    Best posts made by felfert

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

      Hi,

      Just noticed after update to proget (docker) 25.0.8:

      In the gui, the version of a rpm package is displayed correctly:
      Screenshot 2025-08-20 at 09-39-47 cloudtools Versions.png

      But dnf (or yum) cannot find the package anymore. sudo dnf update should update the locally installed cloudtools, but instead the following is displayed:
      Screenshot_20250820_094822.png

      Notice the release number in the listing is cut off (dash remains) and when the actual download is attempted, both the dash and the number are missing.

      Suspect: PG-3074 (just a gut feeling ๐Ÿ˜)

      Cheers,
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: proget 500 Internal server error when pushing to a proget docker feed

      @atripp I tested this one and it works.

      However:
      In the meantime, i have updated to the released 25.0.9 (aka latest) and now I cannot reproduce the error either - even if I explicitely revert the function to the old one where it produced the error before ๐Ÿ˜•

      So I'm afraid that i might not be a reliable tester for this specific error anymore.

      Cheers
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: ERROR while migrating maven repository from Jfrog Artifactory.

      @wechselberg-nisboerge_3629 said in ERROR while migrating maven repository from Jfrog Artifactory.:

      I am especially confused about the fact that it prints Windows paths, even though it is running as Linux Docker container.

      That one fooled me previously as well, but if you look carefully, those are source paths from their build-system
      e.g. C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\...

      posted in Support
      felfertF
      felfert
    • RE: Machine ID changes after restart

      As a reference and perhaps an example for how to run proget as quadlets, here are my config files for quadlets:

      1. /etc/containers/systemd/mssql.container
      [Unit]
      Description=Microsoft SQL server
      
      [Service]
      Restart=always
      # Extend Timeout to allow time to pull the image
      TimeoutStartSec=900
      
      [Container]
      Image=mcr.microsoft.com/mssql/server:2019-latest
      EnvironmentFile=/etc/mssql.env
      Volume=/var/data/mssql:/var/opt/mssql:U,Z
      Network=inedo.network
      HostName=inedo-sql
      
      [Install]
      WantedBy=multi-user.target
      
      1. /etc/containers/systemd/proget.container
      [Unit]
      Description=Inedo proget
      After=mssql.service
      Requires=mssql.service
      
      [Service]
      Restart=always
      # Extend Timeout to allow time to pull the image
      TimeoutStartSec=900
      
      [Container]
      Image=localhost/proget:current
      EnvironmentFile=/etc/proget.env
      Volume=/var/data/proget/backups:/var/proget/backups:z
      Volume=/var/data/proget/database:/var/proget/database:z
      Volume=/var/data/proget/extensions:/var/proget/extensions:z
      Volume=/var/data/proget/packages:/var/proget/packages:z
      Volume=/var/data/proget/ssl:/var/proget/ssl:z
      Volume=/etc/localtime:/etc/localtime:ro
      Network=inedo.network
      PublishPort=80:80
      HostName=proget
      
      [Install]
      WantedBy=multi-user.target
      
      1. /etc/containers/systemd/inedo.network
      [Network]
      

      Remarks:

      The Image in /etc/containers/systemd/proget.container is intentionally referencing a locally tagged image. This goes together with the following script for easily updating
      proget:

      #!/bin/bash
      set -e
      set -x
      systemctl stop proget
      sleep 5
      itag=latest
      if [ $# -eq 1 ] ; then
          itag=$1
      fi
      podman tag proget:current proget:previous
      podman pull proget.inedo.com/productimages/inedo/proget:${itag}
      podman tag proget.inedo.com/productimages/inedo/proget:${itag} proget:current
      systemctl start proget
      cat<<EOF
      Upgrade finished and proget started.
      Old image has benn tagged proget:previous
      EOF
      

      and: Obviously, the hierarchy below /var/data/proget has to be manually created in advance. /var/data/proget is on a separate virtual disk.

      Forgot the env files referenced in the .container files:

      /etc/mssql.env:

      ACCEPT_EULA=Y
      MSSQL_SA_PASSWORD=*****REDACTED*****
      MSSQL_PID=Express
      

      /etc/proget.env:

      PROGET_SQL_CONNECTION_STRING=Data Source=inedo-sql; Initial Catalog=ProGet; User ID=sa; Password=*****REDACTED*****
      TZ=Europe/Berlin
      

      Both are mode 0600, so that the passwords in there are a little bit more protected.

      And: Just after freshly setting it all up, I normally immediately migrate to embedded postgres and then remove the mssql container as well as the inedo network.

      Cheers
      -Fritz

      posted in Support
      felfertF
      felfert

    Latest posts made by felfert

    • RE: Proget docker update from 2026.14 to 2026.15 breaks Postgres DB

      @dean-houston said:

      Anyway... should work now!

      I can confirm it does work like a charm now. As usual, I might add ๐Ÿ‘

      Cheers
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: Proget docker update from 2026.14 to 2026.15 breaks Postgres DB

      @atripp I noticed the new image, but now there seems to be something wrong with the manifest of that image:

      Trying to pull proget.inedo.com/productimages/inedo/proget:latest...
      Error: unable to copy from source docker://proget.inedo.com/productimages/inedo/proget:latest: copying system image from manifest list: determining manifest MIME type for docker://proget.inedo.com/productimages/inedo/proget:latest: reading manifest sha256:f199a28113dc593819a14ba52084d2cedeee40238029f8989d13563d703c9531 in proget.inedo.com/productimages/inedo/proget: manifest unknown
      

      Same happens when I replace latest by 26.0.16

      Also, If i visit https://proget.inedo.com/containers/tags/ProductImages/inedo/proget/26.0.16/subimages in a browser, and then click on the sub-image sha, I get the following:

      (404) Image "inedo/proget:sha256:f199a28113dc593819a14ba52084d2cedeee40238029f8989d13563d703c9531" was not found in the "ProductImages" registry.
      Image "inedo/proget:sha256:f199a28113dc593819a14ba52084d2cedeee40238029f8989d13563d703c9531" was not found in the "ProductImages" registry.
      
      For more information, visit the Error Log Page.
      

      Can you have a quick look?

      posted in Support
      felfertF
      felfert
    • RE: Proget docker update from 2026.14 to 2026.15 breaks Postgres DB

      @atripp said:

      Thanks for the heads-up @felfert !

      It looks like this has to do with some kind of change in the base image, though it didn't get spotted in our regression testing; we're aware of the issue now and have already "pulled" the tag.

      We believe we have a fix and hope to address first thing Monday morning.

      I believe this is caused by them (The pgdg packagers) switching from the old way (adding the user in the postinst script of the postgresql-common package) to the more modern way of letting systemd assign the system-wide uid/gid of the postgres user. An indication for this is the fact, that they now provide a file /usr/lib/sysusers.d/postgresql-common.conf which was missing before.

      Of course this can happen at any time in the upstream distro, and since the database is an external mount into the container this can never be handled at install-time of the postgres package. Therefore, the safest way to solve this, is to chown the DB files on every startup, just like i have shown in my previous message.

      Just my 2ยข
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: Proget docker update from 2026.14 to 2026.15 breaks Postgres DB

      Investigating myself, I stumbled over one significant change in the new container:

      The owner of the hierarchy in /var/proget/database has changed in the updated container:

      Old (2026.14):

      root@proget:/usr/local/proget# ls -la /var/proget/database/
      total 160
      drwx------. 20 postgres root      4096 Nov 15 09:11 .
      drwxr-xr-t.  8 root     root        94 Nov 15 09:11 ..
      -rw-r--r--.  1 root     root        98 Jun 21  2025 .pgsqlconn
      -rw-------.  1 postgres      104     3 Jun 21  2025 PG_VERSION
      drwx------.  7 postgres      104  4096 Aug 20  2025 base
      -rw-------.  1 postgres postgres    44 Nov 15 09:11 current_logfiles
      drwx------.  2 postgres      104 16384 Nov 15 09:11 global
      drwx------.  2 postgres postgres 12288 Nov 15 09:11 log
      drwx------.  2 postgres      104  4096 Jun 21  2025 pg_commit_ts
      drwx------.  2 postgres      104  4096 Jun 21  2025 pg_dynshmem
      -rw-------.  1 postgres      104   206 Aug 29  2025 pg_hba.conf
      -rw-------.  1 postgres      104  2640 Jun 21  2025 pg_ident.conf
      drwx------.  4 postgres      104  4096 Nov 15 12:46 pg_logical
      drwx------.  4 postgres      104  4096 Jun 21  2025 pg_multixact
      drwx------.  2 postgres      104  4096 Jun 21  2025 pg_notify
      drwx------.  2 postgres      104  4096 Jun 21  2025 pg_replslot
      drwx------.  2 postgres      104  4096 Jun 21  2025 pg_serial
      drwx------.  2 postgres      104  4096 Jun 21  2025 pg_snapshots
      drwx------.  2 postgres      104  4096 Nov 15 09:11 pg_stat
      drwx------.  2 postgres      104  4096 Jun 21  2025 pg_stat_tmp
      drwx------.  2 postgres      104  4096 Nov 15 00:50 pg_subtrans
      drwx------.  2 postgres      104  4096 Jun 21  2025 pg_tblspc
      drwx------.  2 postgres      104  4096 Jun 21  2025 pg_twophase
      drwx------.  4 postgres      104  4096 Nov 15 09:17 pg_wal
      drwx------.  2 postgres      104  4096 Oct  5 10:51 pg_xact
      -rw-------.  1 postgres      104    88 Jun 21  2025 postgresql.auto.conf
      -rw-------.  1 postgres      104 30875 Jul 31 14:28 postgresql.conf
      -rw-------.  1 postgres      104    64 Nov 15 09:11 postmaster.opts
      -rw-------.  1 postgres postgres   100 Nov 15 09:11 postmaster.pid
      

      New (2026.15):

      root@proget:/usr/local/proget# ls -la /var/proget/database/
      total 68
      drwx------. 20  101 root  4096 Nov 15 11:47 .
      drwxr-xr-t.  8 root root    94 Nov 15 11:47 ..
      -rw-r--r--.  1 root root    98 Nov 15 11:18 .pgsqlconn
      -rw-------.  1  101  103     3 Nov 15 11:18 PG_VERSION
      drwx------.  6  101  103    46 Nov 15 11:18 base
      -rw-------.  1  101  103    44 Nov 15 11:18 current_logfiles
      drwx------.  2  101  103  4096 Nov 15 11:22 global
      drwx------.  2  101  103    46 Nov 15 11:18 log
      drwx------.  2  101  103     6 Nov 15 11:18 pg_commit_ts
      drwx------.  2  101  103     6 Nov 15 11:18 pg_dynshmem
      -rw-------.  1  101  103   206 Nov 15 11:18 pg_hba.conf
      -rw-------.  1  101  103  2640 Nov 15 11:18 pg_ident.conf
      drwx------.  4  101  103    68 Nov 15 11:32 pg_logical
      drwx------.  4  101  103    36 Nov 15 11:18 pg_multixact
      drwx------.  2  101  103     6 Nov 15 11:18 pg_notify
      drwx------.  2  101  103     6 Nov 15 11:18 pg_replslot
      drwx------.  2  101  103     6 Nov 15 11:18 pg_serial
      drwx------.  2  101  103     6 Nov 15 11:18 pg_snapshots
      drwx------.  2  101  103    25 Nov 15 11:32 pg_stat
      drwx------.  2  101  103     6 Nov 15 11:18 pg_stat_tmp
      drwx------.  2  101  103    18 Nov 15 11:18 pg_subtrans
      drwx------.  2  101  103     6 Nov 15 11:18 pg_tblspc
      drwx------.  2  101  103     6 Nov 15 11:18 pg_twophase
      drwx------.  4  101  103   109 Nov 15 11:27 pg_wal
      drwx------.  2  101  103    18 Nov 15 11:18 pg_xact
      -rw-------.  1  101  103    88 Nov 15 11:18 postgresql.auto.conf
      -rw-------.  1  101  103 31163 Nov 15 11:18 postgresql.conf
      -rw-------.  1  101  103    64 Nov 15 11:18 postmaster.opts
      

      Note: the uid:gid of the postgres user has changed from 101:103 to 994:994

      Attempt to show this in a code snippet was denied for security reasons by the forum.
      Apparently just mentioning the files path in /etc/ that stores these values, triggers a security alert of the forum so I had to obfuscate it a little bit:

      Old:

      root@proget:/usr/local/proget# grep postgres /etc/p*wd
      postgres:x:101:103:PostgreSQL administrator,,,:/var/lib/postgresql:/bin/bash
      

      New:

      grep postgres /etc/p*wd
      postgres:x:994:994:PostgreSQL administrator:/var/lib/postgresql:/bin/bash
      

      And success after manually updating the owner in the container.
      I just ran the following inside the container:

      chown -R postgres /var/proget/database
      

      After a container restart, it worked again.

      => I vaguely remember from the early releases with embedded postgres,
      that there was some permission problem too. So: problem found - fix pending (i hope ๐Ÿ˜Š )

      Cheers
      -Fritz

      posted in Support
      felfertF
      felfert
    • Proget docker update from 2026.14 to 2026.15 breaks Postgres DB

      Hi, After update from 2026.14 to 2026.15 the embedded postgres does not startup anymore.

      I am running proget on Rocky9 as a RHEL-quadlet and the usual upgrade results in postgres not running. Below is a systemd log of the startup attempt after pulling the latest 2026.15 image. This is on a temporary sandbox instance which was freshly installed (with 2026.14), migrated to postgres and finally attempted to upgrade using the following commands in bash:

      systemctl stop proget.service
      podman tag proget:current proget:previous
      podman pull proget.inedo.com/productimages/inedo/proget:latest
      podman tag proget.inedo.com/productimages/inedo/proget:latest proget:current
      systemctl start proget.service
      

      The log of starting the proget.service:

      Nov 15 11:47:49 fe-pgsandbox systemd[1]: Starting Inedo proget...
      Nov 15 11:47:49 fe-pgsandbox podman[4871]: 2026-11-15 11:47:49.67945833 +0100 CET m=+0.106530950 volume create 5302ee210ff0031da105f2981924f780fcffafbd023e28480eca79969af6ef7a
      Nov 15 11:47:49 fe-pgsandbox podman[4871]: 2026-11-15 11:47:49.689362147 +0100 CET m=+0.116434767 volume create a56cbe394584572b9bb748bb4a696a8e55d8b9518a5dee4b2758c6a54fb49b3e
      Nov 15 11:47:49 fe-pgsandbox podman[4871]: 2026-11-15 11:47:49.713049861 +0100 CET m=+0.140122498 container create 3664a42997ef1a2ee01c76b76dfd28f1d47ec2f2462c9293486a60dd89daf8cd (image=localhost/proget:current, name=systemd-proget, org.opencontainers.image.version=24.04, PODMAN_SYSTEMD_UNIT=proget.service)
      Nov 15 11:47:49 fe-pgsandbox podman[4871]: 2026-11-15 11:47:49.652473761 +0100 CET m=+0.079546468 image pull 65a036b666bc930c7d0d755f07140b814e55f22498cac35de35ad5df3b19cc30 localhost/proget:current
      Nov 15 11:47:50 fe-pgsandbox podman[4871]: 2026-11-15 11:47:50.221430187 +0100 CET m=+0.648502815 container init 3664a42997ef1a2ee01c76b76dfd28f1d47ec2f2462c9293486a60dd89daf8cd (image=localhost/proget:current, name=systemd-proget, org.opencontainers.image.version=24.04, PODMAN_SYSTEMD_UNIT=proget.service)
      Nov 15 11:47:50 fe-pgsandbox systemd[1]: Started Inedo proget.
      Nov 15 11:47:50 fe-pgsandbox podman[4871]: 2026-11-15 11:47:50.238660116 +0100 CET m=+0.665732727 container start 3664a42997ef1a2ee01c76b76dfd28f1d47ec2f2462c9293486a60dd89daf8cd (image=localhost/proget:current, name=systemd-proget, PODMAN_SYSTEMD_UNIT=proget.service, org.opencontainers.image.version=24.04)
      Nov 15 11:47:50 fe-pgsandbox systemd-proget[4948]: Updating certificates in /etc/ssl/certs...
      Nov 15 11:47:50 fe-pgsandbox proget[4871]: 3664a42997ef1a2ee01c76b76dfd28f1d47ec2f2462c9293486a60dd89daf8cd
      Nov 15 11:47:50 fe-pgsandbox systemd-proget[4948]: 0 added, 0 removed; done.
      Nov 15 11:47:50 fe-pgsandbox systemd-proget[4948]: Running hooks in /etc/ca-certificates/update.d...
      Nov 15 11:47:50 fe-pgsandbox systemd-proget[4948]: done.
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: info: Microsoft.Hosting.Lifetime[0]
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]:       Application started. Press Ctrl+C to shut down.
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: info: Microsoft.Hosting.Lifetime[0]
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]:       Hosting environment: Production
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: info: Microsoft.Hosting.Lifetime[0]
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]:       Content root path: /usr/local/proget
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: ProGet version is 26.0.15.14.
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: Current DB schema version is unknown.
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: Updating database schema...
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: info: Microsoft.Hosting.Lifetime[0]
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]:       Application started. Press Ctrl+C to shut down.
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: info: Microsoft.Hosting.Lifetime[0]
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]:       Hosting environment: Production
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: info: Microsoft.Hosting.Lifetime[0]
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]:       Content root path: /usr/local/proget
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: Cannot connect to database; will retry in 1 second... Full error: Failed to connect to 127.0.0.1:5728
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: Attempting to use shared configuration for ProGet.
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: Shared configuration file not found at /etc/inedo/ProGet.config.
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: No encryption key is configured. Credentials will be stored in plain text.
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: info: Inedo.Web.BackgroundTaskQueueService[0]
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]:       Background Task Queue is starting.
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: warn: Microsoft.AspNetCore.Hosting.Diagnostics[15]
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]:       Overriding HTTP_PORTS '8080' and HTTPS_PORTS ''. Binding to values defined by URLS instead 'http://*:80'.
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: warn: Microsoft.AspNetCore.Server.Kestrel[0]
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]:       Overriding address(es) 'http://*:80'. Binding to endpoints defined via IConfiguration and/or UseKestrel() instead.
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: info: Microsoft.Hosting.Lifetime[14]
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]:       Now listening on: http://[::]:80
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: info: Microsoft.Hosting.Lifetime[0]
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]:       Application started. Press Ctrl+C to shut down.
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: info: Microsoft.Hosting.Lifetime[0]
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]:       Hosting environment: Production
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]: info: Microsoft.Hosting.Lifetime[0]
      Nov 15 11:47:51 fe-pgsandbox systemd-proget[4948]:       Content root path: /usr/local/proget
      Nov 15 11:47:52 fe-pgsandbox systemd-proget[4948]: Cannot connect to database; will retry in 1 second... Full error: Failed to connect to 127.0.0.1:5728
      Nov 15 11:47:53 fe-pgsandbox systemd-proget[4948]: Cannot connect to database; will retry in 1 second... Full error: Failed to connect to 127.0.0.1:5728
      Nov 15 11:47:54 fe-pgsandbox systemd-proget[4948]: Cannot connect to database; will retry in 1 second... Full error: Failed to connect to 127.0.0.1:5728
      Nov 15 11:47:55 fe-pgsandbox systemd-proget[4948]: Cannot connect to database; will retry in 1 second... Full error: Failed to connect to 127.0.0.1:5728
      Nov 15 11:47:56 fe-pgsandbox systemd-proget[4948]: Cannot connect to database; will retry in 1 second... Full error: Failed to connect to 127.0.0.1:5728
      

      After rollback (Stopping the container and re-tagging the previous image, Starting container)
      everything was up and running again (with the old version of course).

      Thanks
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: pgutil health fails after updating to proget 2026

      Thanks a lot @atripp for the quick fix. Problem solved ๐Ÿ˜Š

      Cheers
      -Fritz

      posted in Support
      felfertF
      felfert
    • pgutil health fails after updating to proget 2026

      Subject says it all:

      [root@gsg1repo ~]# pgutil health
      Checking http://localhost:8080/...Server responded with OK (200): Unexpected server response ('O' is an invalid start of a value. Path: $ | LineNumber: 0 | BytePositionInLine: 0.)
      

      Looking into the source, it attempts to GET /health and expects some json, but proget just replies with OK. So apparently the api endpoint has changed. I could create a PR, but where is the API endpoint doc for 2026?

      Thanks
      -Fritz

      Later: Never mind my first question, found it. BUT apparently (according to the API doc) there is no global health api? I found only feed-related health?!

      posted in Support
      felfertF
      felfert
    • proget.inedo.com DDOSed?

      Visiting https://proget.inedo.com responds with a 500, saying

      (500) Server Error
      The connection pool has been exhausted, either raise 'Max Pool Size' (currently 100) or 'Timeout' (currently 15 seconds) in your connection string.
      
      For more information, visit the Error Log Page.
      

      At the bottom, it says:

      Inedo Edge 2 Download Center (Powered by ProGet ISV Edition)
      

      Just in case you haven't noticed yet.

      Cheers
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: Debian feed broken after upgrade to 2025.14

      @gdivis
      Too bad I already changed all my keys and updated a lot of Test-VM-Instances in an internal OpenStack. Would have been be MUCH less work. Oh well.
      Thanks anyway for the info ๐Ÿ‘
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: Debian feed broken after upgrade to 2025.14

      @dean-houston

      I can confirm, that regenerating the signing keys of all debian feeds solved the problem.
      Thanks for your support.

      -Fritz

      posted in Support
      felfertF
      felfert