Re: pgrouting updated to version 2.2.0-1.pgdg+1

Hello Sebastian, Christoph:
I will contact the people of the debian link,
it so happens, that yesterday I made the tag, but this morning I
realized that I didn't update news and change log so I deleted
the tag, and made a new one. and to this last one I made the release.
And in the link you are giving me, it looks like it took yesterday's tag.

I don't know how much affects this in what you are doing
to make the release.

Thanks for your help and patience. I want to make things correctly and
I really appreciate your help.

Vicky

On Tue, Apr 19, 2016 at 2:01 PM, Sebastiaan Couwenberg <sebastic(at)xs4all(dot)nl>
wrote:

> Hi Vicky,
>
> On 04/19/2016 08:01 PM, Christoph Berg wrote:
> > Vicky Vergara wrote:
> >> There are 2 questions:
> >> First one, and most urgent would be, someone got a server crash, so I
> had
> >> to make a version 2.2.1:
> >> https://github.com/pgRouting/pgrouting/releases/tag/pgrouting-2.2.1
> >> I think some spelling errors were fixed. (see bellow)
>
> s/bellow/below/ ;-)
>
> >> My guess is that: that one has to be packaged.
> >> I really apologize for the double work.
>
> No problem, the changes between 2.2.0 and .1 were minimal, so the
> packaging burden was light too.
>
> > the real Debian packaging is done by Bas and others in
> > https://anonscm.debian.org/cgit/pkg-grass/pgrouting.git/
> > (2.2.1 is already in there, btw :)
> > You'll really talk to them directly. (Cc'ed)
>
> Michael Fladischer did the packaging for pgRouting 2.0.0, but he isn't
> very active any more unfortunately. So I'm picking up the slack, mostly
> because pgRouting one of the reverse dependencies of PostGIS which I
> also help maintain in Debian along with Markus Wanner.
>
> > I myself am also packaging a bunch of PostgreSQL packages for Debian,
> > but in the case of pgrouting, I'm merely re-building what's in the git
> > quoted above for apt.postgresql.org. I'm happy that it Just Works :)
>
> We did need a little poking to get pgRouting 2.1.0 packaged because the
> new upstream version detection didn't handle the changed tag naming
> convention. That was quickly resolved after Christoph contacted the
> Debian GIS team forwarding the request for packaging of pgRouting 2.1.
>
> >> The second is I am wondering about this:
> >> * Team upload.
> >> * New upstream release.
> >> * Update copyright file, changes:
> >> - Update copyright years for various copyright holders
> >> - Add license & copyright for sources by Razequl Islam
> >> - Add new files by Alexander Neundorf
> >> - Add license & copyright for CMake files by Kitware, Inc
> >> * Bump Standards-Version to 3.9.8, no changes.
> >> * Simplify file glob patterns in doc-base.
> >> * Enable verbose make output.
> >> * Add patch to fix spelling errors.
> >> * Enable all hardening buildflags.
> >>
> >> My main concern are:
> >> The copyrights: What is wrong?, so I can fix it in the repository.
>
> Why do you think the copyright is wrong?
>
> The Debian package contains a machine readable copyright file which
> includes all the license & copyright statements included in the upstream
> source per Debian Policy 12.5:
>
> https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
>
> As part of the packaging update for 2.2.0 I reviewed the changes between
> 2.1.0 and 2.2.0, and incorporated the license & copyright changes in the
> debian/copyright file.
>
> If changes to the upstream source were made as part of the Debian
> package update, I would have forwarded the patches like I did for the
> spelling errors.
>
> >> The hardening build flags: What is that? & How do I do the testing with
> the
> >> those flags when making the release?
>
> Hardening buildflags are compile time options "to help harden a
> resulting binary against memory corruption attacks, or provide
> additional warning messages during compiles." See:
>
> https://wiki.debian.org/Hardening
>
> In the Debian package build we just export
> DEB_BUILD_MAINT_OPTIONS=hardening=+all to have the dpkg-buildflags
> helper pass the all the hardening options to the build system.
>
> You can add these options to the upstream buildsystem if you want test
> them as part of the release and not using the Debian packaging tools.
>
> Kind Regards,
>
> Bas
>
> --
> GPG Key ID: 4096R/6750F10AE88D4AF1
> Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
>

--

Georepublic UG (haftungsbeschränkt)
Salzmannstraße 44,
81739 München, Germany

Vicky Vergara
Operations Research

eMail: vicky(at)georepublic(dot)de
Web: https://georepublic.info

Tel: +49 (089) 4161 7698-1
Fax: +49 (089) 4161 7698-9

Commercial register: Amtsgericht München, HRB 181428
CEO: Daniel Kastl