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 as it appears there was no 1.4.4 release tag made so I couldn't even generate a diff from CVS between the released tarball version and the current CVS HEAD that supposedly fixes the problem.
Kevin Johnson wrote: > 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 schedules. ;-) > > Kevin > > > On Feb 11, 2010, at 10:18 AM, Jeremy T. Bouse wrote: > >> 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 have. I'll mark this bug as "wishlist" and "upstream" and when a >> release is made it'll be included. >> >> Kevin Johnson wrote: >>> 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 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 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-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, 'testing'), (500, 'stable') >>>>>>> Architecture: i386 (i686) >>>>>>> >>>>>>> Kernel: Linux 2.6.32-trunk-686 (SMP w/4 CPU cores) >>>>>>> Locale: LANG=C, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) >>>>>>> Shell: /bin/sh linked to /bin/bash >>>>>>> >>>>>>> Versions of packages acidbase depends on: >>>>>>> ii dbconfig-common 1.8.43 common framework for >>>>>>> packaging dat >>>>>>> ii debconf [debconf-2.0] 1.5.28 Debian configuration >>>>>>> management sy >>>>>>> ii libphp-adodb 5.09a-1 The ADOdb database >>>>>>> abstraction lay >>>>>>> ii libwww-perl 5.834-1 Perl HTTP/WWW >>>>>>> client/server librar >>>>>>> ii mysql-client-5.1 [virtual-mys 5.1.43-1 MySQL database client >>>>>>> binaries >>>>>>> ii php-mail 1.1.14-2 PHP PEAR module for >>>>>>> sending email >>>>>>> ii php-mail-mime 1.5.3-0.1 PHP PEAR module for >>>>>>> creating MIME >>>>>>> ii php5 5.3.1-3 server-side, >>>>>>> HTML-embedded scripti >>>>>>> ii postgresql-client-8.4 [postgr 8.4.2-2 front-end programs for >>>>>>> PostgreSQL >>>>>>> >>>>>>> acidbase recommends no packages. >>>>>>> >>>>>>> Versions of packages acidbase suggests: >>>>>>> ii snort-mysql 2.8.5.2-2 flexible Network >>>>>>> Intrusion Detecti >>>>>>> >>>>>>> -- debconf information: >>>>>>> * acidbase/mysql/admin-user: root >>>>>>> acidbase/internal/reconfiguring: false >>>>>>> acidbase/pgsql/authmethod-user: >>>>>>> acidbase/db/basepath: >>>>>>> * acidbase/db/app-user: snort >>>>>>> * acidbase/webserver: Apache2 >>>>>>> acidbase/dbconfig-install: true >>>>>>> acidbase/dbconfig-upgrade: true >>>>>>> acidbase/upgrade-error: abort >>>>>>> acidbase/internal/skip-preseed: false >>>>>>> acidbase/install-error: abort >>>>>>> acidbase/upgrade-backup: true >>>>>>> acidbase/pgsql/method: unix socket >>>>>>> acidbase/pgsql/admin-user: postgres >>>>>>> acidbase/pgsql/authmethod-admin: ident >>>>>>> * acidbase/mysql/method: unix socket >>>>>>> * acidbase/database-type: mysql >>>>>>> acidbase/dbconfig-reinstall: false >>>>>>> acidbase/pgsql/changeconf: false >>>>>>> acidbase/dbconfig-remove: >>>>>>> * acidbase/db/dbname: snort >>>>>>> acidbase/pgsql/no-empty-passwords: >>>>>>> acidbase/remote/host: >>>>>>> * acidbase/base_advisory: >>>>>>> acidbase/missing-db-package-error: abort >>>>>>> acidbase/pgsql/manualconf: >>>>>>> acidbase/passwords-do-not-match: >>>>>>> acidbase/remove-error: abort >>>>>>> acidbase/remote/newhost: >>>>>>> acidbase/remote/port: >>>>>>> acidbase/purge: false >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >>> >>> >> >> > > >
signature.asc
Description: OpenPGP digital signature
