[Debian GNUstep maintainers] gnustep-base transition

Eric Heintzmann heintzmann.eric at free.fr
Wed Sep 27 19:15:59 UTC 2017



Le 27/09/2017 à 09:31, Yavor Doganov a écrit :
> Eric Heintzmann wrote:
>> Le 26/09/2017 à 21:00, Yavor Doganov a écrit :
>>> I would also suggest to get rid of the -dbg packages and switch to
>>> the automatic -dbgsym ones.  Objections?
>>>
>> Using dh_strip --dbgsym-migration= ?
> Yes.
>
>> With this changes, do you know if packages will go in the new queue ?
> I'm not sure, but I don't think so, they are in a separate archive.
> Dropping a binary package (-dbg) does not lead to going through NEW.
> And -dbgsym packages are built automatically by default these days,
> which would mean that all new package uploads would clutter NEW --
> doesn't seem logical at all.
>
> In any case gnustep-base must pass through the NEW queue anyway.

and with a new soname gnustep-gui too
So let's migrate to .dgbsym

>
> Eric, do you maintain debian/changelog in some specific way?  Usually,
> when I make some kind of change, I accompany that change with a
> respective changelog entry.  I see that gnustep-base has some changes
> but no new changelog, while gnustep-make has some strange version.  Is
> the latter a result of some git-buildpackage workflow or is added
> intentionally?
>
Well I don't know the good practices, if there are any, for
debian/changelog in git repo.
I don't write it before the the upload.
I just use 'gbp dch --snapshot --auto' to generate temporary one to
build the package but I don't commit them. (for -make it was an
accident, sorry)
At the end I write one and upload the package but i don't commit it
until pkg is accepted in the archive.




More information about the pkg-GNUstep-maintainers mailing list