Hey, On Wed, 2012-07-11 at 08:02 +0000, Bart Martens wrote: > Can you fix bugs 643252 and 668725 for wheezy before introducing a newer > upstream release in unstable ? Both of those issues were fixed months ago in the 2.0.11 release currently in the mentors repo, I filed an RFS but nobody came forward. I also suspect that 643252 is related to the previous sponsor pulling out all the dbconfig-common work I put into the initial package, what he uploaded failed to work for me and I have been using a build out of my own repository. The problem is that I'm not a DM, so I need to rely on sponsors. Not all sponsors respect the integrity of the package and I often see broken packages uploaded. If I could find a sponsor whom I could work with (rather than one whom ignores things for months and then gets shirty when I don't respond quick enough for his liking, and then proceeds to pull out large parts of debian directory - without consultation - breaking things in the process) then these things would not be an issue. I also believe that the 2.0.11 build needs to go into wheezy as it meets with the php 5.4 requirement. Check out the 2.0.11-3 package on debian mentors or at : deb http://debian.lusan.id.au/debian unstable main contrib non-free The repository contains a keyring package as the packages are signed. :) If you still need a separate 2.0.10 release for wheezy then let me know and I can do it ... but I'll need a sponsor I can work with. :) I recently became a co-maintainer for sql-ledger, although working with alioth and svn-buildpackage was new to me I found Raphael to be far more tolerant and willing to help/guide than Tony was (no response for six months after he agreed to sponsor the package and then suddenly when I take 3 days to respond he has a go at me). I have some long term health issues that do mean I'm not always able to do things to other peoples timetables, but I do get them done. The postfix-cluebringer and sql-ledger packages have also been the first two packages I have had to build to meed the standards of the Debian project proper, rather than for personal or company internal use where large lintian overrides (or simply not using lintian) are viable. I hope we can work something out :) -- Nikolai Lusan <nikolai@lusan.id.au>
Attachment:
signature.asc
Description: This is a digitally signed message part