Another take on this. Dave convinced me that I had access to svr1, which
it turns out I did, so I managed to check the logs myself. And I find:
Aug 21 10:51:24 postgresql postfix/smtp[52021]: 3F45C9FB2BB:
to=<pgsql-patches-p
ostgresql.org@postgresql.org>, orig_to=<pgsql-patches@postgresql.org>,
relay=mai
a.hub.org[200.46.208.251], delay=1, status=sent (250 2.7.1 Ok,
discarded, id=258
35-09 - BANNED: P=p003,L=1,M=multipart/mixed |
P=p002,L=1/2,M=application/x-gzip
,T=gz,N=vcbuild.tar.gz | P=p...)
Seems -patches is rejecting any mail with attached .tar.gz files, if I
read that correctly? That's just *wrong* IMNSHO - that's exactly what
-patches is *for* :-) (Assuming I read the logline right, that is -
can't say I really recognize the message enough o be sure)
Is there a list somewhere of what kind of stuff gets discarded without
notification?
Anyway. I've put the patch on
http://www.hagander.net/pgsql/vcbuild.tar.gz. I'll be happy to repost it
to the list once it's fixed, but for now please consider using that link
to review...
//Magnus
> -----Original Message-----
> From: Magnus Hagander
> Sent: Monday, August 21, 2006 4:00 PM
> To: pgsql-hackers@postgresql.org
> Cc: Marc G. Fournier
> Subject: Unable to post to -patches (was: Visual C++ build files)
>
> One more attempt to send this, now without the attachment. It's
> getting eaten somewhere. I assume it's not the moderation queue,
> because someone would hopefully have gotten to it during the four
> weeks I was gone..
>
> Anyawy. Third take on the message itself, if it goes through, could
> someone who has access please look to see where the other two
> emails went? Exact dates in CEST (UTC+2) in the forward headers
> below. For the latest send, I got this in my mailserver logs:
>
>
> Aug 21 15:51:23 altair postfix/smtp[8141]: 221DCF4104: to=<pgsql-
> patches@postgre sql.org>, relay=svr1.postgresql.org[200.46.204.71],
> delay=2, status=sent (250 Ok
> : queued as 3F45C9FB2BB)
>
> Contains a postfix queue id that could be tracked.
>
> //Magnus
>
> > -----Original Message-----
> > From: Magnus Hagander
> > Sent: Monday, August 21, 2006 3:51 PM
> > To: pgsql-patches@postgresql.org
> > Subject: FW: Visual C++ build files
> >
> > Argh!
> >
> > I sent this patch before I left on vacation, but for some reason
> it
> > seems it never came through - I can't seem to find it in the
> archives
> > :-(
> >
> > Let's see if I can get it through this time.
> >
> > //Magnus
> >
> > > -----Original Message-----
> > > From: Magnus Hagander
> > > Sent: Thursday, July 13, 2006 10:32 PM
> > > To: pgsql-patches@postgresql.org
> > > Subject: Visual C++ build files
> > >
> > > Attached is the current version of my scripts to build the
> > complete
> > > PostgreSQL system using Visual C++. See archives for reasons
> > why...
> > >
> > > The basic idea is to parse as much information as possible out
> of
> > the
> > > existing Makefiles and configure.in, to make sure we don't add
> a
> > huge
> > > maintenance headache. Most things are parsed, some are not
> (some
> > not
> > > possible,some just too hard IMHO). There's also code that
> > replaces
> > > what configure needs to do, and shellscripts like gen_fmgroids.
> > >
> > > It generates solution and project files for Visual C++ 2005,
> > which
> > > should work fine with both the commercial and the free versions
> > (some
> > > optimiser features etc not available in the free one, of
> course,
> > but
> > > that's MS for you). System can be built both from the GUI and
> > from the
> > > commandline.
> > >
> > > Currently only a DEBUG build can be built. Naturally, the plan
> is
> > to
> > > allow RELEASE builds as well :-) That part is just not finished
> > yet,
> > > and for now debug builds are really the only thing
> interesting...
> > >
> > > Per previous message, this patch will require some further
> work,
> > but I
> > > wanted to get it submitted in good time before feature freeze
> for
> > > people to look over. My hope is to have it in for 8.2, but most
> > likely
> > > we'll continue to build the release binaries with mingw for one
> > more
> > > release at least. It would be very good to be able to build
> > proper
> > > debug-enabled binaries to help people debug issues, though -
> and
> > to
> > > get it on the buildfarm properly.
> > >
> > > So, the plan is to update the buildfarm code to deal with
> > building and
> > > testing the VC builds as well. After speaking with Andrew about
> > it, it
> > > seems this shouldn't be all too hard to do. Some required
> changes
> > are
> > > already made for other reasons (decreasing dependency on
> external
> > > tools), others still needed but not started yet.
> > >
> > > All files should be uncompressed into a directory named
> "vcbuild"
> > > in the root of the tree. No changes are made to any other
> files,
> > so
> > > there should be no effect at all on other parts of the system.
> > >
> > >
> > > //Magnus
