I new release would be packaged and uploaded to unstable within a day
or two at most. I get alerts when there is a new version to be packaged.
The package build is also setup for patches if one were available and
could be uploaded today.
Kevin Johnson wrote:
> Vladimir,
>
> We will be rel
On Thu, Feb 11, 2010 at 09:56:06AM -0500, Jeremy T. Bouse wrote:
> Then when is the release with the fix as we're not tracking CVS...
Kevin is right. You should make difference. Yes, You shouldn't build
package for every CVS update. But if the package become totally unusable
(as now) You sh
Vladimir,
We will be releasing a new version as soon as possible from the main
project. I am not sure when that will be available, so maybe you
should switch until then.
Kevin
On Feb 11, 2010, at 10:49 AM, Vladimir Stavrinov wrote:
On Thu, Feb 11, 2010 at 09:56:06AM -0500, Jeremy T. Bou
Kevin Johnson wrote:
> On Feb 11, 2010, at 10:31 AM, Jeremy T. Bouse wrote:
>> I don't have time to go tracking through CVS to figure out a patch
>> for the problem, that was not even mentioned in the initial bug report.
>
> I agree that the bug report was vague and if it had been sent to me, I
>
On Feb 11, 2010, at 10:31 AM, Jeremy T. Bouse wrote:
Maintaining packages is a volunteer effort and comes after my 2
paying
jobs.
Join the club :-) I understand it is volunteer and didn't mean to
piss in your wheaties.
I don't have time to go tracking through CVS to figure out a patch
Maintaining packages is a volunteer effort and comes after my 2 paying
jobs. I don't have time to go tracking through CVS to figure out a patch
for the problem, that was not even mentioned in the initial bug report.
It would also appear that the CVS repository is useless as far as
tagging a
I wouldn't expect you to package every CVS release. My understanding
was that you were going to try and fix the bug, in that case I thought
I would provide you with a solution that was easier then building it
yourself. I guess I don't understand the work of debian maintainers
or your busy
We track stable releases... and the last release put out was 1.4.4
which was packaged... I don't have time to track and repackage every CVS
update and the website doesn't appear to have any patch to 1.4.4 to fix
the problem already which means I have to track it down which is time I
don't h
On Thu, Feb 11, 2010 at 09:06:10AM -0500, Jeremy T. Bouse wrote:
> Could you please try to be any more vague or would it be too much to
> ask for information that actually helps identify the problem other than
> saying there's a problem. Otherwise it's just as big a waste of time as
> a snip
It just seems that if you wanted to maintain the project within
Debian, it would make sense to at least track CVS. If you are going
to fix the bug your self it would just be duplicate effort.
Kevin
On Feb 11, 2010, at 9:56 AM, Jeremy T. Bouse wrote:
Then when is the release with t
Then when is the release with the fix as we're not tracking CVS...
Kevin Johnson wrote:
> This was fixed in the CVS for the main project. You guys might want to
> check that out. :)
>
> Kevin
>
> On Feb 11, 2010, at 9:06 AM, Jeremy T. Bouse wrote:
>
>> Could you please try to be a
This was fixed in the CVS for the main project. You guys might want
to check that out. :)
Kevin
On Feb 11, 2010, at 9:06 AM, Jeremy T. Bouse wrote:
Could you please try to be any more vague or would it be too much to
ask for information that actually helps identify the problem othe
Could you please try to be any more vague or would it be too much to
ask for information that actually helps identify the problem other than
saying there's a problem. Otherwise it's just as big a waste of time as
a snipe hunt.
Vladimir Stavrinov wrote:
> Package: acidbase
> Version: 1.4.4-
Package: acidbase
Version: 1.4.4-3
Severity: normal
The recent system upgrade break down acidbase. It doesn't work with new php
version. Please, adjust Your code for new php.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testin
14 matches
Mail list logo
