Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1heL5H-0004b3-F0 for pgsql-bugs@arkaria.postgresql.org; Fri, 21 Jun 2019 15:04:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1heL5F-0004uv-Mq for pgsql-bugs@arkaria.postgresql.org; Fri, 21 Jun 2019 15:04:09 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1heL5F-0004nR-5X for pgsql-bugs@lists.postgresql.org; Fri, 21 Jun 2019 15:04:09 +0000 Received: from mail-qk1-x742.google.com ([2607:f8b0:4864:20::742]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1heL5C-0004U2-4X for pgsql-bugs@lists.postgresql.org; Fri, 21 Jun 2019 15:04:07 +0000 Received: by mail-qk1-x742.google.com with SMTP id l128so4649707qke.2 for ; Fri, 21 Jun 2019 08:04:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=q61Qy+R0T6zJz3eFTouf648/tc5rW5X5D+haVw1zPXA=; b=kryE2/EUKIhHckjEbXMG+MH/62osN0gt71bkmfs2IbrPcolW8lZG1XZjHrHFD5lFfC +X1ut3EsAj+ONrQCA/su7a1uZIFMl9SFUCggcyZWfxTLtVHnTdu40L2glAP3S//vHSL3 Gq2qJ1C/5HvRbd1yrXyXZfhfr1Pd1CY/pvNlcSSDc295J86n7yqpyW0MlyRMccuIZsQR Gi2S++YuPe7ccB5AglY4xG4efQkrBY8milUeZAOB3Iq/VdpSlFk3K+7MB5aZqDugA48N t3E/godUk4hm8UT+ft+qzWMr/fNyQAtbuigixLmkQOZokHtR6eZ93wdi5MJ7FqcGXxbf 6q+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=q61Qy+R0T6zJz3eFTouf648/tc5rW5X5D+haVw1zPXA=; b=m3z9JxiTLjZcO/4INpCByWzTMNc5Md9yuXGiBNADKpjPuKgsBGjJQtgPm0bjAVGaZV shT0Sto9eYBPnaNwwryToUyK0zpNtavojUmIVcJ9VNa9QV7C/32H7QkbA5K05GNQ0Lpz 65VWw+0dw5E+avLu/iQ3Lak76j8g3QG0pRTQjI/zNQQeF+ma66FloB/4EYbmRbwYI4nc /V1kWZcQoB2132gm2MgtJctY404QyAFQwOhBHFFa8dskZ56swR6X4jMmTlCztqpQysUr ym97afG10TIMqW6/L4C0ElYAcAkINwi/VfjCpbiARbL2afrhMLq/d0r3SNSfyw/7bUz6 VC6A== X-Gm-Message-State: APjAAAUQWlyHMsJ3lMuJ4ANbHQS4t9Lkx0aMbomYHSlXVDjPTeuFSSRU 0O+XtdSGQgWlySazrHWkCD3W7w== X-Google-Smtp-Source: APXvYqwifZN85XHgiPAcolE3Sj2KmML+ah58wTQgfuemGurKiSYjFSZxNZTutnZTmdRTeTb/kBBBBg== X-Received: by 2002:a05:620a:125b:: with SMTP id a27mr14460547qkl.112.1561129444474; Fri, 21 Jun 2019 08:04:04 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([191.125.99.86]) by smtp.gmail.com with ESMTPSA id g10sm1464952qkk.91.2019.06.21.08.04.02 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Fri, 21 Jun 2019 08:04:04 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 2BAB5120827; Fri, 21 Jun 2019 11:03:58 -0400 (-04) Date: Fri, 21 Jun 2019 11:03:58 -0400 From: Alvaro Herrera To: Matt Harter Cc: Devrim =?iso-8859-1?B?R/xuZPx6?= , "pgsql-bugs@lists.postgresql.org" Subject: Re: BUG #15768: Removed rpms and now require /etc/redhat-release Message-ID: <20190621150358.GA13774@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <85E56491-5F45-48B8-84A4-15BD7566AE7F@genesys.com> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-Apr-18, Matt Harter wrote: > Well whether or not it is officially supported, it still works on amazon linux, and since their default repositories are behind on postgres (which of course is really an amazon limitation) we have to manually add the repository. Since the recent change that added a required dependency (which is clearly NOT required for amazon linux), our previously working deploy pipelines are now blocked/broken. We have temporarily mitigated the issue by using rpm and explicitly ignoring the repositories dependencies, but that seems like a band-aid fix for the real problem which is that dependency shouldn’t be there. Why does a repository need to enforce the os it is on? If a consumer wants to do something “wrong” or against the documented way to do things, their issues are their problem. I agree, and adding such a dep sounds like a strange change to make. What was the rationale for that? -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services