Hi Dirk,
On Sun, 18 Feb 2007 at 20:01 +0100, Dirk Nehring wrote:
> On Sun, Feb 18, 2007 at 06:58:42PM +0100, Waldemar Brodkorb wrote:
> > Hi Dirk,
> > On Sun, 18 Feb 2007 at 15:20 +0100, Dirk Nehring wrote:
> > > On Sun, Feb 18, 2007 at 02:50:20PM +0100, Waldemar Brodkorb wrote:
> > > > Hi Dirk,
> > > > On Sat, 17 Feb 2007 at 22:20 +0100, [EMAIL PROTECTED] wrote:
> > > > > Author: dnehring
> > > > > Date: 2007-02-17 22:20:08 +0100 (Sat, 17 Feb 2007)
> > > > > New Revision: 2052
> > > > >
> > > > > Added:
> > > > > trunk/freewrt/package/libevent/patches/
> > > > > trunk/freewrt/package/libevent/patches/patch-event_c
> > > > > Modified:
> > > > > trunk/freewrt/package/libevent/Makefile
> > > > > Log:
> > > > > Update to latest version for new tor.
> > > >
> > > > This breaks tor and other packages, which use libevent. If you
> > > > update a library always build a full-build to see if you break
> > > > something.
> > > >
> > > > Either revert or fix the allmodconfig build. Very soon we will have
> > > > a automatic buildsystem, where every commit will be checked..
> > >
> > > Hi Waldemar,
> > >
> > > since days I'm doing full builds all the time to fix bugs from me and
> > > other developers. Please don't say I'm not testing!
> >
> > I have not said you are not testing, read my mail :p
> > I just said make full builds if you change libraries. Sometimes
> > changes to the ADK are sitting more than 2 weeks in one of my
> > workspaces, before they get committed. I just want to tell every
> > developer to do intensively testing before commit. If something is
> > not ready, just let it sit some time on your disk. Or send a patch
> > to the list and ask for help.
>
> I even have patches sitting for weeks in my repository, like wlan
> scripts or binutils updates. The later I'm currently testing 3 weeks!
> I do not understand your comment above: I say I update the library
> because of tor, and you say it breaks tor? No further hint,
Yes, sorry. Stupid mail from me. That was a rather good example for a very very
bad bug
report. But at least I reported it :}
After 12 hour day with a lot of shitfucking asterisk and ISDN
problems, I should not try new stuff from anybody and complain.
So sorry for that. The Asterisk-ISDN problems driving me crazy and
you got in the way.
> nothing. Hey, come on, you can believe me I have tested my checkin
> before, so you should provide a little bit more detailed information.
Yes, you are right.
> > > Currently, I cannot build asterisk-14 (Plattform: WRT54G3G). Can you fix
> > > this stuff?
> >
> > No. I only fix bugs I know of :}
>
> ? What do you mean here? You say it works for you??
> > If you find bugs, please either use our fine ticket system or
> > mailinglist to report them. Others do the same.
> > So do not be angry if you find bugs, just report them via mail or
> > trac. I do the same every day.
>
> This was a bug report. You don't need to teach me how to do it. We all
> want a working repository, so please clean up the bugs first. I suggest
> to make full build with all targets to see the remaining errors.
So please make better bug reports than I do.
"Geh mit guten Beispiel voran"
thanks and have a nice evening
Waldemar
--
don't open your wrt, free it
http://www.freewrt.org
_______________________________________________
freewrt-developers mailing list
[email protected]
https://www.freewrt.org/lists/listinfo/freewrt-developers
