public inbox for [email protected]  
help / color / mirror / Atom feed
From: Jeremy Schneider <[email protected]>
To: Christoph Berg <[email protected]>
Cc: [email protected]
Subject: Re: pg18 patch: separate package for llvm/jit
Date: Sat, 1 Mar 2025 17:06:43 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

On Sat, 1 Mar 2025 16:51:49 -0800
Jeremy Schneider <[email protected]> wrote:

> one question - the commit message says "Closes: #927182" and i'm
> curious what that number is a reference to? It doesn't seem to be an
> issue or PR that I found on salsa.debian.org but maybe I haven't
> looked in the right place yet.

nevermind, that was obvious

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927182

also cf
https://www.debian.org/doc/manuals/debmake-doc/ch06.en.html#changelog

Crazy that bug has been open since 2019. I'll go learn a bit more about
the debian bug tracking system.

I've now bookmarked
https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=postgresql-17

This raises a higher level question... is this mailing list the right
place for this kind of discussion?

In my first pass through, I didn't see anything at
https://wiki.postgresql.org/wiki/Apt or
https://wiki.postgresql.org/wiki/Apt/FAQ about "where is the best place
to ask questions" or "how to check if a bug/issue was already reported"
or "how to raise a question about new feature or change discussions"

-Jeremy






view thread (4+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: pg18 patch: separate package for llvm/jit
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox