Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tfBVX-000GoV-0E for pgsql-pkg-debian@arkaria.postgresql.org; Tue, 04 Feb 2025 05:29:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tfBVV-001RiP-Hg for pgsql-pkg-debian@arkaria.postgresql.org; Tue, 04 Feb 2025 05:29:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tfBVV-001RiH-Bd for pgsql-pkg-debian@lists.postgresql.org; Tue, 04 Feb 2025 05:29:57 +0000 Received: from mail-oa1-x2f.google.com ([2001:4860:4864:20::2f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tfBVS-003ADf-0Q for pgsql-pkg-debian@lists.postgresql.org; Tue, 04 Feb 2025 05:29:56 +0000 Received: by mail-oa1-x2f.google.com with SMTP id 586e51a60fabf-2b7f09611a9so10588fac.3 for ; Mon, 03 Feb 2025 21:29:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738646992; x=1739251792; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=MAeXoSSlNyS95RddM4wENtqZ6OVefEe+SFUd4+VC1hk=; b=Iw+fQzoWIQaLgFW/B1B/Mmvz+5vGFfNfXFq5OOJJPd1vC9Z0moURQk/FlFDhOF4/9G U6gM3JxhaPw868jZz5wB4inaWMWlqtFHWb6Tuz+vJMMsdK415Mg15rkQe9CCMGjFseCN UDGvq/r68BYoe0CrphOI8TJaUUXR6Hx41goQTPRGqQRqaw4S7iQ2xSPWwOnNDrUsvT9D ZQlTPaaM1Z5ugRXW9QgtKfKyJwyEybrZM755itwtURiy97VuLySr1rqm1dvB0Wgni+FI VRTT57Ta6q56iJu8L8yQiXdLRruBHeTX6IFtMDcZkQRK+/ic7UESBf/9nZZverpxcR8a 7w7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738646992; x=1739251792; h=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=MAeXoSSlNyS95RddM4wENtqZ6OVefEe+SFUd4+VC1hk=; b=PZjtDGbxxDUoNyCl9LNTJchupUE3SkgQaXaqP2l2h5jaau4UuUeJZqq3kr2AD+qf0V WLNMYS5SCEOl7t9IbrNTlj68ZDFWZ3OowY1bg0REKw3wcNyy2kYtPg7HlFN0vw1uIGA4 GF9XHGp7ZxVLSOTI533A2slQWH7OW781d9AivYWY9PXjCSPRwlbvvvCN28On2jmTdCZK QYT9yISPDEDXko5OaA0PYFBvP+HeSv7TafzKLwm0L1XXH/qR8HhLI3HfXmT7y7E2B7ut iIk/T/QBpfyiDR8TmPZS6DrCbvLz0L1oNaTPUJCowuu0WL+DuU4/Puv+bJfiswTHIcAq OziQ== X-Forwarded-Encrypted: i=1; AJvYcCVc1N4zTzN335Z+Udj8weC/AtCubA/kQgyVMzYoa7AeRb2kwdTd2kCxwf3eYDdGO3xkwpPhK6xmjB7P/su0/FZN@lists.postgresql.org X-Gm-Message-State: AOJu0YzBwlrJCvY7qtMUXgtCnAjurxJ9uBb+LB3YLF+EAreoZ5bLAakN 17pbzG6huW2lJfY4rjpLnU86DeMMMzpcdXHTnjKe8qKt6tu+BVzsTodmSaL7LFuB1dibmF8Vdf6 NurS2BIBLDW1k3KeUfrfsKypNvRWiMBU/ X-Gm-Gg: ASbGncvRFsiAF0f/UDxf5bDuWmpAZmt9NrU/tpY+E52g8TXHB3/I5Y8ZtVOu8ZKhFgK vuJpoV71yM88I0nZ0VWy14ntChlJGHuwQ0zQdjqm/3nXSqcGmrsLKyOIWnQlwnjx7eNge2Pou X-Google-Smtp-Source: AGHT+IGPTO77l6W0z5mw5hQ2uVHAYyIgCMmxRpbL3aezGGJOWPvZdNRVSUVveAe7qrJtvOyEb5QQ6fAszX/K4ix/UIM= X-Received: by 2002:a05:6870:7d09:b0:29e:290f:7aea with SMTP id 586e51a60fabf-2b32f2e93c7mr16229077fac.34.1738646992622; Mon, 03 Feb 2025 21:29:52 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Bradford Boyle Date: Mon, 3 Feb 2025 21:29:41 -0800 X-Gm-Features: AWEUYZkkvrvZATbnB5sUIAQkz2LeHSXKhEKHzW2qusuWAHw6wU0CkXv2u6cW9to Message-ID: Subject: Re: Redis & SQLite FDW packages To: pgsqlitegis@tutamail.com, pgsql-pkg-debian@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi Michel, I've reviewed your branch and here is my feedback: * d/changelog is for the Debian version of the package Since the first packaged version of the extension is 2.5.0, the changelog should start with that version. Older versions are not included since they haven't been uploaded to the Debian archive. * Potentially incorrect version format This depends on whether the package is intended to be a native or non-native package; see [0] for a summary of the differences between the two. The majority of PostgreSQL Debian packages that I have reviewed/worked on have been non-native. For a non-native package, the Debian package version is a combination of the upstream version (e.g., 2.5.0) and a Debian component (e.g., 2.5.0-1). * Invalid Source and Package name Per Debian policy [1]: > Package names (both source and binary, see Package) must consist > only of lower case letters (a-z), digits (0-9), plus (+) and minus > (-) signs, and periods (.). They must be at least two characters > long and must start with an alphanumeric character. So the correct name for the source package would be sqlite-fdw and for the binary package postgresql-PGVERSION-sqlite-fdw * Missing some common Build-Depends that dh_make_pgxs includes when creating a new source package * Incorrect matching pattern in d/watch The matching pattern needs to match hrefs in the web page at found at the URL. In this case, it needs to match the tag format of v(x.y.z).tar.gz * Additional packages are required for running the installcheck test I needed to include locales-all, sqlite3, and tzdata-legacy in the tests dependencies for the test to run * Needed to pass REGRESS_PREFIX to make when running installcheck The latest version of PostgreSQL in Debian unstable is 17.2. When running the installcheck target, this version was expanded into a directory path to specify which SQL queries to run during testing but the there is no 17.2 directory under expected. This will probably require a change to upstream sqlite_fdw in order for the test to successfully run on the full matrix of supported PG versions. I have pushed my work-in-progress (which incorporates your work) to a personal repo on salsa.debian.org [3]. To try building the binary package localy, you can install the devscripts package and then try running debuild -i -us -uc -b. I have my development environment setup to build packages with sbuild [2] so I haven't tested this. I wouldn't recommend setting up sbuild unless you intend to really get involved with broader Debian packaging work. Regards, -- Bradford [0]: https://www.debian.org/doc/debian-policy/ch-source.html [1]: https://www.debian.org/doc/debian-policy/ch-controlfields.html#source [2]: https://salsa.debian.org/bradfordboyle/sqlite-fdw [3]: https://wiki.debian.org/sbuild