Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pzMd7-00007w-Dx for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 17 May 2023 19:16:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pzMd6-00063V-Bg for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 17 May 2023 19:16:08 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pzMd6-00063L-3o for pgsql-pkg-debian@lists.postgresql.org; Wed, 17 May 2023 19:16:08 +0000 Received: from mail-lj1-x236.google.com ([2a00:1450:4864:20::236]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1pzMd0-000MLB-TN for pgsql-pkg-debian@lists.postgresql.org; Wed, 17 May 2023 19:16:06 +0000 Received: by mail-lj1-x236.google.com with SMTP id 38308e7fff4ca-2ad819ab8a9so12510301fa.0 for ; Wed, 17 May 2023 12:16:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684350961; x=1686942961; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=AL5fjAiIfGR4d7I5XD8opxd2O+AE2XkfI/ih4yqf45Y=; b=SLv2vRIr9jxgZB8M/swgN4dPhcQMpjjLDSvfa8o8THKpeFcTAdK7dUoMPpw2uod9MV xYdbX6gTvroz43R2OiLDh+F1yXFmMIBMpMgW6nZ0I3Fwvg3RQdwGSDScaJ59Py0eyvet eCnXxfEappmMNz8nSGNoC+S51Keaaj6MdixyFdqIa7nTyoyzlrXcMxVIZlBK5TsCdtt1 pHR8Pkd3MWIwV4SGmMQ8FCLjlSmwnuoNl8NbUQaEP+Rl6xeqIM6cGFiyrMwPFXqBD5Mp 5FyDsZAdSBFUQlwB2XIyHnpjAevM5fK1ZxIttOQBiiiDK4YncFCOc6Mngxc/+w07R7Nr e3aw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684350961; x=1686942961; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=AL5fjAiIfGR4d7I5XD8opxd2O+AE2XkfI/ih4yqf45Y=; b=lWFilgcJ0aJrXRR9Q2vEEbU1cthI92OruHWsE7GDPhOLMyA6U0cyOg+xb5XwYO4piV jvA6miZ/+th6IwF7eHhD4JQYJCLsYtKLRwCb8RlhVpwqaeTI/hVgkw5RY/+gR2z5LQ+/ mwsuZr6Fx+MvQwatO1xojF0BfdKugFv0oBeDx5AgLaUxWRTX8RDUKtNeU3zLwAYYdZUK rKXCkwUL4dTLAw5ANn8nGHBO29WZSqp6cQ1LfxvZldHovd9zcpnf9UDFRDMR6sGFKkoi ZGy5m5DzRkILPvwQqiaoCQHylidbFXImBIG1MB1vzI2scuf6SMKehJABAkUYmw4hkOu5 LFUw== X-Gm-Message-State: AC+VfDwBrk/rhEiWfSP7rdRpyr8a2aDFoGafFcEqSf62uTzIMO8WGtu8 2wvgEOkBULXLTXg5P8F5YDZ0RT2wuJIDpqciW3s= X-Google-Smtp-Source: ACHHUZ5w9AZZuQXKLkJMhzQ9B7HlxY9Ipj8kUrHdekGa7ThAblR/9sj0HrmnlZQ80a25Rv4U8nC7dq3kVnUsL36ZJSg= X-Received: by 2002:a2e:9099:0:b0:2ae:db65:2d01 with SMTP id l25-20020a2e9099000000b002aedb652d01mr3995487ljg.23.1684350961051; Wed, 17 May 2023 12:16:01 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: James Coleman Date: Wed, 17 May 2023 15:15:49 -0400 Message-ID: Subject: Re: Postgres 15.2 packages missing To: Christoph Berg Cc: pgsql-pkg-debian@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, May 17, 2023 at 11:14=E2=80=AFAM Christoph Berg w= rote: > > Re: James Coleman > > Thanks. I had a vague memory of something like that, but then when I > > saw the 15.0 and 15.1 packages I assumed I'd remembered incorrectly. > > > > What's the reasoning for maintaining only the newest point release in t= he repo? > > Mostly that reprepro that doesn't support it, unfortunately. It's > still the best repo managing software around. We might have a look at > "aptly", but its command line interface is somewhat weird and possibly > not an improvement. > > Thanks for spotting the inconsistency, I managed to clean up the > debris in there. The extra packages in there were mostly from old > packages built while the distribution in question was still in > development itself, so this wasn't even usable as a general wayback > machine. > > apt-archive.postgresql.org is automatically kept up to date and > receives all packages with a delay of one day. Ah, that helps. Thanks for maintaining the repo. I'm probably misunderstanding something here still, but is reprepro _not_ used to manage the archive repo such that we don't have that problem there? Thanks, James