Hey, Tino.

Okay I've compared the package you've put together with the one I had
assembled to see the differences, and the result looks okay to me.  A minor
suggestion to consider for the debian/changelog would be to separate
contributions similar to how other packages do it such as:

-------------------------------------------------------------
xca (1.3.2-1) unstable; urgency=medium

[ Tino Mettler ]
  * New upstream release (Closes: #706539, #811347)
  * Switch to dh build
  ...

[ Chris Knadle ]
  * Bump standards version to 3.9.6, no changes needed
  * Add 0001-Use-Debian-specific-CPPFLAGS.patch to use hardening flags
    (This also replaces the change from the previous NMU.)
  ...
-------------------------------------------------------------

It's fine to leave the debian/changelog as-is (other than changing the
release distribution from "UNRELEASED" to "unstable", obviously) if you'd
prefer the current form.



The other thing to note is that debhelper now automatically makes an
xca-dbgsym package by default.  Normally switching from a -dbg package to a
-dbgsym package requires a transition (see 'man dh_strip' and the
--dbgsym-migration option), but since no -dbg package was shipped previously
I don't think any transition is needed.  If for some reason you'd rather not
ship a -dbgsym package there's a --no-automatic-dbgsym dh_strip option.
(Mentioning this because it's quite new.)



Tino Mettler:
> On Mon, Feb 01, 2016 at 22:07:53 +0000, Chris Knadle wrote:
>> Tino Mettler:
> 
>>> The package also closes your bug #811347.
>>
>> Yes, as it should.  ;-)
> 
> Hi Chris,
> 
> it's your bug about your package, so I mentioned it in the case that
> there are some aspects in my package that justify to keep the bug open.

Thanks.  ;-)  No need, the package you've put together looks good.

[...]
>>> I forgot to ask: do you plan to upload that package? If not, I'll ask
>>> my usual sponsor.
>>
>> Well I'm not a DD (yet) so I can't upload it directly -- I'm a DM.
> 
> sorry, I thought you uploaded the NMU. I should use
> tracker.debian.org more often.

Yeah it took me a bit to get used to using Tracker, and after using it for
some time it becomes invaluable.

>> DMs can only directly upload packages that they are the
>> maintainer/uploader for, and only if a DD has requested that the DM
>> be given permission to upload that specific package.
>>
>> ftp-master.debian.org has the following link for details:
>>
>>    https://lists.debian.org/debian-devel-announce/2012/09/msg00008.html
> 
> I alread read about the basic aspects of becoming a DM or DD and even
> talked to the local Debian folks about this.  However, family life
> currently sets strong timing contraints. :-)

Yep, understood.  ;-)

>> Side notes:
>>
>> One of the most recent 2 messages in this thread was signed, and I see the
>> key was revoked -- looks like it was signed with your old key rather than
>> your newer one.  ;-)
> 
> I'm an idiot. Thanks for the hint.

Please be kind to yourself.  :)  I now realize this is a whole lot more
important than I would have realized earlier.

And -- we all make honest mistakes from time to time, so it's important that
that be something that's okay.  So when this happens it seems best to simply
admit the err and move on.

>> If you're interested in becoming a DM, what you'll need is 2 GPG signatures
>> from DDs (on your newer key)
> 
> This is WIP, I already got one signature on the new key.

Cool.  :)

>> (And now also an Alioth guest
>> account, apparently.)  See the "Join the NM process" link at:
> 
> I already have one and use it for collab-maint for another package.
> 
> Thanks for all your remarks, I'll send the package to my usual sponsor.

Very good.

   -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us

Reply via email to