Re: RFS: libconfig (requires transition)
- To: firstname.lastname@example.org
- Cc: email@example.com
- Subject: Re: RFS: libconfig (requires transition)
- From: Jose Luis Tallón <firstname.lastname@example.org>
- Date: Fri, 03 Feb 2012 01:50:15 +0100
- Message-id: <[🔎] 4F2B2F47.email@example.com>
- In-reply-to: <4F2722E1.firstname.lastname@example.org>
- References: <4F21C630.email@example.com> <20120126221815.GL31641@mraw.org> <4F21F7C1.firstname.lastname@example.org> <20120127072054.GQ4901@radis.cristau.org> <email@example.com> <20120127192341.GR4901@radis.cristau.org> <4F240D87.firstname.lastname@example.org> <20120130191500.GC19118@radis.cristau.org> <4F2722E1.email@example.com>
My apologies if you did send an e-mail and I didn't read it. My inbox is
severely overloaded as of lately...
Isn't it good style to notify the maintainer and/or coordinate with them
before an NMU ?
On 31/01/12 00:08, Jonathan McCrohan wrote:
Julien Cristau<firstname.lastname@example.org> wrote:
Please don't change the -dev package name.
All of the packages except one have versioned Build-depends
on libconfig8-dev. Surely this needs to be replaced with
libconfig-dev or at least libconfig9-dev?
No it doesn't? You can rename the -dev package to
libconfig-dev if you want, but certainly don't *need* to, and
if you do it, then it would be way better from our point of
view to keep building libconfig8-dev as a transitional package
until the reverse deps are updated, and to do that separately
from the SONAME bump.
Being bitten a couple times already after not checking buildability of
r-deps... it is the library maintainer's responsibility, after all.
If its ok, I'll leave the package as is.
I can change it if it makes it easier for you so. Your paragraph above
made it sound as if it didn't matter which way it was done.
To clarify, what is the process for this transition? Will the
package be uploaded to experimental to allow me to report bug
reports and patches against dependant packages?
I'm not sure I understand what you're asking.
This is my first upload which requires a transition, and I am unsure
of what happens next.
Please read the library maintainer's guide first (or re-read if needed).
It does avoid many a headache...
Well, unfortunately for the world (some would say ;) ), not too many
packages depend on libconfig; Nor are they very complex.
Therefore, a full transition via experimental and involving the RM is
not needed, AFAIK. Just notifying the depending maintainers should
suffice (it would be different during freeze, of course)
It seems common for packages to be uploaded to
experimental for a time prior to the actual transistion to allow other
maintainers update their packages accordingly. I was wondering will
this be the case with this transition?
Just drop me a line if I can be of any help.