On 06/07/2010 03:33 AM, Yaroslav Halchenko wrote: > thanks for looking into libfann -- I am not myself a user of it, and it > is unfortunate that not much of upstream development happening, but it > is indeed somewhat pathetic to ship the same version of it through > multiple releases of Debian ;) > > I will look at your packaging, please buzz me if you don't hear from me > in a day or two, ok? meanwhile
Will do, thanks! >> I took over as Maintainer of libfann from Steffen, and have prepared >> packages for fann-2.1.0beta (the most recent version). > Is Steffen aware of that? Yes, he consented (see RFA+ITA #583645) > judging from changelog (and git history) it is not clear from what > packaging did you start? why Debian changelog entries for Steffen's > (upstream) packaging weren't adopted (with UNRELEASED)? Ouch, I really screwed that one up. The packaging was so outdated that I literally started from scratch, and then forgot to rebase my changes on the previous versions. This happened primarily out of routine - I've been packaging mostly new stuff so far, and that was my usual workflow. I re-created the git tree, using the following steps: - Import libfann1-1.2.0 from the official archive with git-import-dsc - Import fann-2.1.0beta from upstream with git-import-orig - DFSG-cleaned upstream - Re-applied all my changes, documenting each one properly. I originally skipped upstream's unreleased changelog entries because I implemented them completely differently (mostly because of python-support and dh syntax), but I included them this time for consistency. If you've already cloned the repository, you'll have to to it again... the old one is still available as pkg-libfann-old.git, though. Thanks again, Christian (I think we can leave Gerfried out of CC: in future, so we avoid spamming him :-) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
