[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#502305: ulogd2 still not in Debian



On Sat, Apr 17, 2010 at 10:53:47PM +0100, Jurij Smakov wrote:
> Hello,
> 
> Over 18 months passed since the last update to this ITP, but ulogd2 is 
> still not in Debian. Recently we figured out that ulogd is completely 
> broken on sparc, and, more generally, whenever storage size of 
> long/size_t are different in kernel and in userspace (see [0] and bugs 
> merged with it). I've filed an upstream bug against ulogd, but it does 
> not look like it's going to be fixed. I would like to see a working 
> ulog solution on sparc and other arches in the next release, so it 
> looks like the only option we have is to get ulogd2 into the archive 
> ASAP. If you are no longer interested in working on it, I might find 
> interested developers and/or work on it myself, otherwise I would be 
> glad to review and test existing package, and sponsor an upload if 
> necessary.
> 
> [0] http://bugs.debian.org/265985
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=15765
> 

Hi Jurij,

I am still working on ulogd2 though I must admit I did not have much
time.
The current state is that the packages are basically working and ulogd2
seems functional (rather stable here).
However, there are still some problems:
- there is no upgrade path (and there will probably never be upstream)
  from ulogd1.
- I'd like to propose dbconfig as an option, to be able to create the
  database etc. automatically
- Current packaging was copied from another package, and is using cdbs
  (which I do not like personally), but this is a minor point unless it
  prevents from maintaining it correctly
- Things upstream are not finished, there are still some pending patches

That said, I could have uploaded something to experimental.

Temporary (old) packages can be found here:
http://www.wzdftpd.net/downloads/ulogd2-deb/
(Version numbering is not correct)

I am just about leaving Paris for vacation, so I won't be able to work
on it this week. I'll try to update the packages after.

Cheers,
Pierre





Reply to: