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 1pmnPX-0004qe-Fk for pgsql-pkg-debian@arkaria.postgresql.org; Thu, 13 Apr 2023 03:14:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pmnPW-0004oB-2D for pgsql-pkg-debian@arkaria.postgresql.org; Thu, 13 Apr 2023 03:14:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pmnPV-0004o2-Qi for pgsql-pkg-debian@lists.postgresql.org; Thu, 13 Apr 2023 03:14:09 +0000 Received: from mail-yw1-x1131.google.com ([2607:f8b0:4864:20::1131]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1pmnPO-002Z1C-HR for pgsql-pkg-debian@lists.postgresql.org; Thu, 13 Apr 2023 03:14:09 +0000 Received: by mail-yw1-x1131.google.com with SMTP id 00721157ae682-54f21cdfadbso206658317b3.7 for ; Wed, 12 Apr 2023 20:14:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681355640; x=1683947640; 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=AfWVtl3IAdqp5jRT9rlt/rh5REOtma/z9Tfzp2NVYNM=; b=N3Z47cL2HsxX8s9JKz+XUC8K+Q8tV/vS0TYqhJsZDU474KLC+jsbf+dMtrBp22coz/ mpG0jI4qAy8QfTmMcbStMSLWESlQr+G2KTmcsIuAtNPZp4+ln2LqMZJhHrQff/czt9bM 1WmdC2deevpkr+WYwq6pzfNSCgkrMczR7xPKDbvSvuG4zBBvXgyAQuMz0bDcTKl6srx1 7bDAA1sm/KP68JEWIlb+kXiaf+hor+JighJbMm67xDCNNpcu3YF2x5ZxZuQTlotWDdpe TrFEsz9U1mLYfmM8oC/jBqneFlbfnqYokGQHT+/umO/p8A+AtO+XJ2bQ7pnjIRwN+nvo QJyg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681355640; x=1683947640; 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=AfWVtl3IAdqp5jRT9rlt/rh5REOtma/z9Tfzp2NVYNM=; b=L2S7Ju4uyKoXHYonkAb7IhkZ9E5SCrxzkwtFcHdFTw27JegpyT1CSdVroTsH1liB9O DIGc4cnGuCwMWR3CF38V7PDTSENZpqjRyEI/Y6rAbaocMuqFOaUtrdBb2A51bvo4hS6J YWoRM9AGjmILJbc5KUC3Z3ft5SWqH/3FmVrPCqI0yn9M++C9IoJSOUQJyPRGfph50SDo AXExMmkoDRn9dgCGknaGe6UOHJxXVbdPT5TCcGUE8DiMhcckv0iirSaTDOfTs4crlPfc pW6MV7ZIcRdFIV6LU6M9hn2g3vHqLW0cyIG6FWsRlUiBLOgp+HTKBuIM08Y71YoN+k1S BhYQ== X-Gm-Message-State: AAQBX9eP/rVGOiwhdQFEklQxOB+VSNBywh0uyqR8nyJe0PIcEzHDRhcf sq3+GXf8zs6aKOsrlxDwkglk/G1irmHxl9ZPnLg= X-Google-Smtp-Source: AKy350Y9kzFlxdSPNXYmy824RmZCMcfIUntN//NI07z4+9dYQrVh1M1kTjDZ3UOOR5v8wIzqtbK+gzAtrl2I9dH3Wic= X-Received: by 2002:a81:ac19:0:b0:53c:6fda:835f with SMTP id k25-20020a81ac19000000b0053c6fda835fmr481839ywh.0.1681355640115; Wed, 12 Apr 2023 20:14:00 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Bradford Boyle Date: Wed, 12 Apr 2023 20:13:49 -0700 Message-ID: Subject: Re: Packaging request - pgvector To: Paul De Audney 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, Apr 12, 2023 at 5:33=E2=80=AFPM Paul De Audney wrote: > > Hello maintainers, > > Thank you for all the work you do maintaining the packages. > > I was wondering what is the correct way to make a packaging request for h= ttps://github.com/pgvector/pgvector? > > The yum repo has this already packaged, is there any shared infrastructur= e/packaging targets between the packaging formats/repos? > > Kind regards, > > Paul Hi Paul, I'm not a member of the PostgreSQL Debian packaging team and my knowledge comes from looking at the various package repos and the code for pgapt -- it's entirely possible that my knowledge is incorrect. With that said, my understanding of how the PostgreSQL APT repo is populated is that it takes upstream packages from Debian unstable and rebuilds source and binary packages for all supported Debian and Ubuntu distributions. The first step would be to prepare a Debian package for pgvector and submit it for inclusion in Debian unstable. Once that is done, a job can be added to pgapt to populate the repo with rebuilds of this package. I just checked and it doesn't look like there is an existing package for pgvector, nor is there an intent to package (ITP) in the Debian bug tracking system (BTS). I can help with creating a Debian package for pgvector and preparing a patch for pgapt, but I'd need a Debian developer to sponsor the upload to unstable and someone with commit privileges to pgapt. If there's no objection, I can take a first pass at this over the weekend. -- Bradford