Bug#441200: libconfig name clash

# it's libconfig's problem now reassign 441200 src:libconfig severity 441200 minor tag 441200 upstream thanks On Thu, 22 Jan 2009, Don Armstrong wrote: > If there aren't any objections,[1] lets reassign this bug back to > src:libconfig while retitling and changing the severity to indicate > the p

Bug#441200: libconfig name clash

On Thu, Jan 22, 2009 at 11:45:53AM -0800, Don Armstrong wrote: > I think it's still a bug that libconfig is using such a generic name, > but it's certainly one that can be made severity minor, tagged > upstream, and possibly wontfix'ed. Whatever the case, I don't think > the ctte needs to be involv

Bug#441200: libconfig name clash

Don Armstrong writes: > If there aren't any objections,[1] lets reassign this bug back to > src:libconfig while retitling and changing the severity to indicate the > problem. Sounds good to me. -- Russ Allbery (r...@debian.org) -- To UNSUBSCRIBE

Bug#441200: libconfig name clash

On Thu, 22 Jan 2009, Russ Allbery wrote: > For the rest of the tech-ctte, to save reading through the bug log: > > * The original dispute was over the package name "libconfig", which was > excessively generic. There was a package by that name in Debian > maintained by its author, and a separa

Bug#441200: libconfig name clash

Julien Danjou writes: > At 1232576811 time_t, Carsten Hey wrote: >> I don't think this bug still makes any sense due to this facts. Should >> this bug be closed? > > I guess so. I concur. For the rest of the tech-ctte, to save reading through the bug log: * The original dispute was over the pa

Bug#441200: libconfig name clash

At 1232576811 time_t, Carsten Hey wrote: > I don't think this bug still makes any sense due to this facts. Should > this bug be closed? I guess so. Cheers, -- Julien Danjou .''`. Debian Developer : :' : http://julien.danjou.info `. `' http://people.debian.org/~acid `- 9A0D 5FD9 EB42 22F6 8

Bug#441200: libconfig name clash

Hi, the old libconfig has been orphaned and removed from lenny and sid (#499259). After that the hyperrealm libconfig has then been uploaded as libconfig (#438683). I don't think this bug still makes any sense due to this facts. Should this bug be closed? Regards Carsten -- To UNSUBSCRIBE,

Bug#441200: libconfig name clash

ok, I think we should try to vote on this one: * Ian Jackson ([EMAIL PROTECTED]) [071127 21:25]: > So I hereby formally propose the set of resolutions and (unaccepted) > amendments implied by this DRAFT BALLOT: > > -8<- > > [Option D:] > (1) The existing libconfig in Debian may retain its

Bug#441200: libconfig name clash

Andreas Barth writes ("Bug#441200: libconfig name clash"): > What are the reasons to also vote about a procedure for the new name, > and not leave that to the default mechanismns? Well, if we say nothing at all then at least one of the two parties has suggested they may pick the

Bug#441200: libconfig name clash

On Tue, Nov 27, 2007 at 09:25:02PM +, Ian Jackson wrote: > [Option D:] > (1) The existing libconfig in Debian may retain its name. The maintainer of that package writes: ] Here's my argument(s). I'll try to keep it short: ] ] a) First come, first serve. I'm both the upstream author an

Bug#441200: libconfig name clash

* Ian Jackson ([EMAIL PROTECTED]) [071128 03:25]: > [Option D:] > (1) The existing libconfig in Debian may retain its name. > [Options X and N:] > (1) The existing libconfig in Debian must be renamed or removed. > > [Option N:] > (2) The newer library may use the name libconfig.

Bug#441200: libconfig name clash

There has been little further discussion following my last message. I think we just need to vote on this. Regardless of how finely balanced the various options are, we need to make a decision. So I hereby formally propose the set of resolutions and (unaccepted) amendments implied by this DRAFT B

Bug#441200: libconfig name clash

Hi Ian >@2007.11.15_22:18:01_+0200 Here's my argument(s). I'll try to keep it short: a) First come, first serve. I'm both the upstream author and maintainer and the library is used by several of my programs (some Debian packages, some not). I wou

Bug#441200: libconfig name clash

At 1195157881 time_t, Ian Jackson wrote: > 13. We are unlikely to be able to persuade the newer library's > upstream to rename it at this point. As a result, insisting on it > having a different name in Debian would cause considerable > inconvenience to any users of the library and is

Bug#441200: libconfig name clash

-BEGIN PGP SIGNED MESSAGE- No-one else on the committee has commented on this issue at all. Do you have any opinions ? Here is my draft, which I'm not proposing formally as yet: 1. This is a dispute about who should be allowed to use the name `libconfig' (both as a library name as

Bug#441200: libconfig name clash

Julien Danjou writes ("libconfig name clash"): > My arguments are the following: abz's libconfig is old, non used > (no reverse-dependencies) and has only 40 installs according to popcon[2]. > Furthermore, it's packaged as a native Debian package and does not seems > to be distributed anywhere. I d

Bug#441200: libconfig name clash

Package: tech-ctte Severity: normal Hi, The current problem is simple. I did an ITP of libconfig[1], a simple and efficient C/C++ library for parsing configuration file. This library is written by Mark Linder, and is well maintained. Filling the ITP, I knew there was already libconfig in Debian.