dear Harvard University and President, please remove David Holland from his function. he is at this department: http://www.hcs.harvard.edu/~dholland/
he does this: http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=47488 combined with this: find some extra behavior his, below at this e-mail. (this is just exemplary, i am not going to hunt his misbehavior) thanks and high regards, Noud, B.ICT A.P. deBROUWER Jr. Voldijkje 13 NL-5053AG GOIRLE (NB) the Netherlands On Wed, 2013-01-23 at 10:05 +0000, David Holland wrote: > The following reply was made to PR pkg/47488; it has been noted by GNATS. > > From: David Holland <dholland-pb...@netbsd.org> > To: gnats-b...@netbsd.org > Cc: > Subject: Re: pkg/47488: textproc/xalan-c got removed; find replacement in > wip/xalan-c > Date: Wed, 23 Jan 2013 10:00:00 +0000 > > On Tue, Jan 22, 2013 at 02:55:03PM +0000, Jonathan A. Kollasch wrote: > > From: "Jonathan A. Kollasch" <jakll...@kollasch.net> > > To: gnats-b...@netbsd.org > > Cc: pkg-mana...@netbsd.org, gnats-ad...@netbsd.org, pkgsrc-b...@netbsd.org > > Subject: Re: pkg/47488: textproc/xalan-c got removed; find replacement in > > wip/xalan-c > > Date: Tue, 22 Jan 2013 08:50:49 -0600 > > > > See > > http://mail-index.netbsd.org/pkgsrc-changes/2011/02/23/msg052329.html > > , is textproc/xqilla not a sufficient successor? > > xqilla was a successor for libpathan, not xalan-c. > > I don't think any explanation or discussion of the removal of xalan-c > ever appeared, other than it was (perhaps>) failing in (some?) bulk > builds. > > That said, it was nearly two years ago... > > -- > David A. Holland > dholl...@netbsd.org > Conversation with #pkgsrc on Fri Feb 1 07:30:12 2013: (07:30:12) The topic for #pkgsrc is: pkgsrc.org & pkgsrc-wip.sourceforge.net. The portable packaging system from The NetBSD Foundation. Welcome pkgsrc-2012Q4! Meet us in Berlin: http://www.pkgsrc.org/pkgsrcCon/2013/ (07:30:19) noud1: ha (07:30:57) noud1: is http://www.libssh.org/2013/01/22/libssh-0-5-4-security-release/comment-page-1/ already fixed?? (07:31:36) noud1: http://mail-index.netbsd.org/tech-pkg/2013/02/01/msg010723.html (07:33:47) You are now known as noud48 (07:48:23) ASau left the room (quit: Quit: off). (08:24:46) sh4rm4 left the room (quit: Remote host closed the connection). (08:28:01) sh4rm4 [~sh4rm@gateway/tor-sasl/sh4rm4] entered the room. (09:20:36) petar [~pe...@84-73-24-140.dclient.hispeed.ch] entered the room. (09:30:02) GitHub [~git...@sh2.rs.github.com] entered the room. (09:30:02) GitHub: [pkgsrc] jsonn pushed 4 new commits to trunk: http://git.io/7R4Tfg (09:30:02) GitHub: pkgsrc/trunk 1183da7 hans: Revert previous, jperkin says it's wrong. (09:30:02) GitHub: pkgsrc/trunk 9bc45a3 reed: move from pkgsrc wip... (09:30:02) GitHub: pkgsrc/trunk 27b0f74 reed: added x11/lxsession (from wip) (09:30:02) GitHub left the room. (10:13:22) agj left the room (quit: *.net *.split). (10:16:07) petar left the room (quit: Quit: Lost terminal). (10:16:21) agj [~a...@a.mx.ohess.org] entered the room. (11:13:06) tm left the room (quit: Read error: Connection reset by peer). (11:13:14) tm [~tm@2a03:2900:2:1::b8] entered the room. (11:13:20) DGASAU left the room (quit: Quit: fosdem). (11:13:39) tm is now known as Guest24198 (11:15:45) Woodstock: jperkin: i meant, does smartos use /usr/lib/amd64, or is the 64bit stuff in /usr/lib? (11:21:12) jperkin: Woodstock: base platform is the same as illumos, yes. (11:21:56) theglass [~theglass@unaffiliated/theglass] entered the room. (11:33:38) Woodstock: jperkin: ok, so where exactly does pkgsrc set LIBABISUFFIX for sunos? i didn't see it anywhere, so i want to add it to mk/platform/SunOS.mk --- (11:58:03) The topic for #pkgsrc is: pkgsrc.org & pkgsrc-wip.sourceforge.net. The portable packaging system from The NetBSD Foundation. Welcome pkgsrc-2012Q4! Meet us in Berlin: http://www.pkgsrc.org/pkgsrcCon/2013/ 328: http://www.pkgsrc.org (12:07:37) jperkin: Woodstock: it doesn't need to, iirc ld already knows to do the right thing. (12:07:44) jperkin: what problem are you seeing? (12:14:19) Woodstock: i see that builtins are searched in the wrong directories, and that -L/usr/lib/amd64 isn't removed from the command lines as it should be (12:15:07) jperkin: isn't that just a case of not setting PREFER_PKGSRC correctly? (12:15:44) Woodstock: no, it's just generally wrong if libraries are picked up in /usr/lib instead of /usr/lib/amd64 for a 64bit build (12:15:58) jperkin: do you have an example package I can verify against? we set PREFER_PKGSRC=yes and only set native for a few bits, so should be able to compare REQUIRES between 32/64 (12:17:02) Woodstock: openssl is such a case, it creates .pc files that point to /usr/lib (12:17:13) Woodstock: but stuff like that is easy to fix once LIBABISUFFIX is set correctly (12:17:30) Woodstock: there's also a bunch of infrastructure stuff that uses it, like find-libs.mk etc. (12:18:10) Woodstock: so i intend to set that, it shouldn't do any harm to you if you don't use it at all (12:20:25) jperkin: I'd like to see bulk builds done first, as I don't see such issues and I'd be worried of breakage (12:21:11) Woodstock: you probably don't see the issues since you don't use builtins (12:21:42) Woodstock: but here's my results with those patches: http://www.headcrashers.org/pkgsrc/reports/current/OpenIndiana/oi151a/x86_64/20130118.0918/meta/report.html (12:21:58) jperkin: oh you mean you're using builtin openssl (12:22:03) Woodstock: and the same for i386, which doesn't set LIBABISUFFIX: http://www.headcrashers.org/pkgsrc/reports/current/OpenIndiana/oi151a/i386/20130118.0913/meta/report.html (12:22:17) Woodstock: it's not only builtin openssl (12:23:54) jperkin: ok, put it in and I'll do complete rebuilds for my next upstream-trunk* builds (12:23:59) Woodstock: ok (12:24:14) jperkin: as I'd like to verify the gmp stuff too anyway (12:26:37) jperkin: btw the p5-glib2 failure is just MAKE_JOBS, is fixed in trunk, if you're on 2012Q4 you probably want to pull that up (12:27:20) Woodstock: in trunk? pull up? (12:27:28) Woodstock: i just build on cvs -HEAD (12:27:40) jperkin: ok, so next build will pick it up :) (12:27:45) Woodstock: great :) (12:28:25) noud1: Woodstock, would you pls check for http://www.libssh.org/2013/01/22/libssh-0-5-4-security-release/comment-page-1/ too? thanks (12:31:07) noud1: noud {Friday February 1, 2013 @ 1:56 am} NetBSD refuses to update to this version. (12:31:07) noud1: http://mail-index.netbsd.org/tech-pkg/2013/01/31/msg010721.html (12:31:48) noud1: CVE-2012-4559 Fixed multiple double free() flaws. CVE-2012-4560 Fixed multiple buffer overflow flaws. CVE-2012-4561 Fixed multiple invalid free() flaws. and CVE-2013-0176 ? NULL dereference leads to denial of service are in effect (12:32:01) You are now known as noud48 (12:32:29) noud48: Woodstock, http://www.libssh.org/2013/01/22/libssh-0-5-4-security-release/comment-page-1/ pkgsrc/security/libssh (12:32:39) noud48: NetBSD refuses to update to this version. (12:32:39) noud48: (12:31:07) noud1: http://mail-index.netbsd.org/tech-pkg/2013/01/31/msg010721.html (12:32:54) noud48: that all in reference to CVE-2012-4559 Fixed multiple double free() flaws. CVE-2012-4560 Fixed multiple buffer overflow flaws. CVE-2012-4561 Fixed multiple invalid free() flaws. and CVE-2013-0176 ? NULL dereference leads to denial of service are in effect (12:33:10) Woodstock: noud48: fyi, there are people working on that. you can stop making a fuss about it. (12:33:15) noud48: Woodstock, pkgsrc/security/libssh is in your build too? (12:33:25) noud48: o working on it.. nice super (12:33:35) noud48: idea when them will be done? (12:33:56) noud48: or and, how long till i should must make fuss again cause if nothing happens?? (12:34:34) jperkin: you shouldn't ever make a fuss like the one you made, it was completely unacceptable (12:34:36) Woodstock: instead of making a fuss you could have just provided a patch to fix it, or at least politely ask (12:35:03) noud48: no, it was very acceptable, and to my and us all knowledge nothing yet has been done to it! (12:35:19) noud48: i did make the patch total replace pkg in wip/libssh (12:35:32) noud48: and brought it to attention, and did ask pull-up (12:35:47) noud48: result: 4 to 6 hours of yelling i got, and now still nothing done (12:35:52) noud48: 24hour later (12:36:04) noud48: and lie maybe? it is being addressed now (12:38:01) noud48: Woodstock, can maybe someone from the nbsd project contact me and tell me!!?? (12:38:48) Woodstock: if you look closely to the mails on the mailinglist you might find clues (12:39:00) noud48: not at all, have looked (12:39:05) noud48: refering to wut? (12:39:37) noud48: where do i in there see the actions taken? and ..i do not see any actions underway inthere as well (12:39:56) noud48: Woodstock..this evening, Apache given xalan-c removal (12:40:17) noud48: http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=47488 (12:40:35) noud48: or not, if fixed before or if i get right to fix myself, ofcourse (12:41:02) jperkin: Woodstock: btw, I'm hoping to land openssl 1.0.1c upgrade soon so you will want PREFER_PKGSRC then, it gives significant AES-NI improvement. (12:41:50) noud48: shall i already check the outstanding openssl exploits?? (12:42:22) Woodstock: jperkin: thats what it just committed (PREFER.openssl?=pkgsrc), i just want builtin detection to work in any case (12:43:11) noud48: Woodstock, them are not willing to fix 4 CVEs let alone some minor total other thing? (12:44:21) noud48: okay openssl seems current: Fixed in OpenSSL 1.0.1c (Affected 1.0.1b, 1.0.1a, 1.0.1) (12:44:46) noud48: jperkin, land that soon?? or A.S.A.P.?? (12:45:57) noud48: oho, it's the same SHIT: grep OPENSSL_VERS * (12:45:57) noud48: Makefile:OPENSSL_VERS?= 0.9.8x (12:46:04) noud48: so that is: (12:47:50) noud48: CVE-2012-2333, CVE-2012-0884, CVE-2012-0050, CVE-2012-0027, CVE-2011-4619, CVE-2011-4577, .. must i go on w this SHIT?? (12:48:45) noud48: Woodstock, shake hands for half (i supply the fix myself to nbsd, but them do not apply) (12:49:27) jperkin: noud48: you appear to have completely missed the fact that this is a volunteer project. it is unacceptable to demand that people work to your timescales and to abuse them when they do not. if you are unhappy with this, then you have complete freedom to fork your own. (12:49:48) noud48: Woodstock you can indeed _be_ safe: OpenSSL 0.9.8x (12:50:04) noud48: no jperkin, you total miss my voluteering (12:50:19) noud48: wip/libssh and wip/xalan-c for instance (12:50:29) noud48: no demand, sollution made and given (12:50:55) noud48: no abuse done, the yelling in my direction was abuse. (12:52:23) noud48: jperkin, is nice you pamper Woodstock, but and you might as well take already solved problems too. (12:52:51) jperkin: as Woodstock told you, people are working on it. the package provided in wip/libssh as it stands is broken and needs work to integrate. abusing people who are volunteering their time to integrate your contributions is, again, unacceptable. (12:52:52) noud48: Woodstock, in regard how much sponcor money is it?? (12:52:53) Guest24198 is now known as tm (12:53:10) noud48: working on it, informal telling, nobody did tell me, nor do i see movenment. (12:53:14) Woodstock: noud48: http://www.youtube.com/watch?v=kzw1_2b-I7A (12:53:28) noud48: exact pullup and rebuild does take 15minutes (12:53:34) noud48: did that myself here local already (12:53:51) noud48: you all are now bashing me from yesterday around this time and nothing done yet (12:54:06) noud48: Woodstock..i watch maybe okay (12:54:33) noud48: am not interested in Maraton Man vid (12:54:53) Woodstock: well, is it safe? (12:54:58) petar [~pe...@84-73-24-140.dclient.hispeed.ch] entered the room. (12:55:02) noud48: told you already it ain (12:55:21) noud48: ain't ..global well known CVEs are not being addressed while total fix given. (12:55:40) noud48: total disrespect there users, except users that pay big sponcor money (12:55:50) noud48: and even them get services too late (13:00:46) noud48: Woodstock..now you do the math okay..listen good: (13:00:57) noud48: 0.9.8x does not exist yet!! (13:01:08) noud48: ftp://ftp.openssl.org/source/ does not exist (13:01:24) noud48: and !! ftp://sunsite.cnlab-switch.ch/mirror/openssl/source/ is not from openssl (13:01:38) noud48: Woodstock, understand now ?? !! ???? (13:02:37) Woodstock: it's an authorized mirror, see http://www.openssl.org/source/ (13:02:56) noud48: it is an authorized overtaken mirror (13:03:10) Woodstock: oh really? (13:03:17) Woodstock: anyway, i'm going to get me some pizza. bbl. (13:03:25) noud48: yes, there is no 0.9.8x at openssl (13:03:40) noud48: you look http://www.openssl.org/source/ ..no 0.9.8x at openssl (13:03:50) noud48: enjoy the pizza (13:03:52) jperkin: you mean http://ftp.openssl.org/source/openssl-0.9.8x.tar.gz ? (13:04:30) noud48: then immediate correct MASTER_SITES= ftp://ftp.openssl.org/source/ \ (13:04:49) noud48: cause it only takes it from the second one: malisious: MASTER_SITES= ftp://ftp.openssl.org/source/ \ (13:04:49) noud48: ftp://sunsite.cnlab-switch.ch/mirror/openssl/source/ \ (13:05:27) jperkin: it's hard to understand exactly what you are asserting, but are you saying that cnlab-switch.ch has an exploited openssl tarball? (13:05:50) jperkin: in which case, unless they have successfully collided SHA1 and RMD160, the checksum will fail. (13:05:53) noud48: no i am saying MASTER_SITES= ftp://ftp.openssl.org/source/ \ in pkgsrc Makefile does total not exist (13:06:04) noud48: i will put it in PR okay (13:06:17) noud48: and will publish that as well somewhere then (13:06:37) noud48: given how you OS handles such up till now okay (13:06:43) jperkin: so it's just that the first site doesn't exist, it's not that the second one (which does) is unreliable? (13:06:56) noud48: is the first one okay yet? (13:07:05) noud48: do i have to look over that error in something else? (13:07:55) noud48: and we are going to stretch all these dialogs in time and not take on the addressed? (13:08:12) noud48: jperkin, you think the world will notice? (13:09:09) jperkin: I'm sorry, I cannot parse what you are saying (13:10:01) noud48: jperkin, you say first fetch address is invalid but as well you say you will not address it (13:11:31) noud48: jperkin, where are the mirrors openssl listed? (13:13:02) jperkin: I haven't said I won't address it, I'm still at the stage of trying to understand exactly what you are asserting. You use words such as 'overtaken' and 'malisious' [sic] to suggest a completely different problem to the first one not working (13:13:29) jperkin: if it's simply that the first listed mirror is broken, just say 'the first mirror for openssl doesn't work, please fix/remove it', and then it's perfectly clear. (13:13:39) noud48: then fix the first problem, the not working (13:13:45) noud48: am already editing the PR (13:16:39) jperkin: anyway, I have fixed it. (13:18:11) noud48: super (13:18:14) noud48: i check (13:19:28) noud48: it is not yet on anon cvsweb.netbsd.org: (13:19:29) noud48: Makefile 1.170 3 months asau Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days. (13:19:43) jperkin: well, no, that takes some time to sync. (13:19:52) noud48: i know.. 1 to 2 hours (13:20:02) noud48: can you already show a copy the work done? (13:20:16) sh4rm4 left the room (quit: Remote host closed the connection). (13:21:09) jperkin: cvs diff -r1.170 -r1.171 security/openssl/Makefile (13:21:25) noud48: content pls (13:21:50) morr: checkout pkgsrc yourself (13:21:57) jperkin: I changed ftp://ftp.openssl.org/source/ to http://ftp.openssl.org/source/ (13:22:05) noud48: super that's still wrong (13:22:17) jperkin: curl disagrees with you (13:22:52) noud48: no ..but paste curl output here then (13:23:03) noud48: you will see..takes next mastersite that is wrong (13:23:15) noud48: plus..you did not paste exact change (13:23:25) noud48: and the change you mention, is exact wrong as well (13:23:36) noud48: http://ftp.openssl.org/source/, times out..so next site used (13:23:45) morr: works for me (13:23:49) noud48: jperkin, you are shitting the whole (13:23:58) noud48: works, show curl output then (13:24:23) noud48: i file the PR just as hard in 2 hours w this shit (13:25:02) morr: http://pastebin.com/ANsB7zvv (13:26:06) noud48: okay. thanks ajusting. (13:26:46) morr: now go away, or we will replace you with VERY little bash script. (13:26:57) noud48: haha ;) (13:27:17) noud48: i'll hush for moment ;) and thanks the correction (13:27:42) noud48: do not forget to update PKGREVISION (13:27:51) noud48: pls (13:33:31) juhuchapa [~juhuchapa@200.13.124.36] entered the room. (14:06:14) jperkin: PKGREVISION is not necessary, there is no change in the binary package (14:11:54) noud48: there is a big change in the fetch (14:12:25) noud48: not in the bniary package, but in the tarball fetched (14:12:51) jperkin: the tarball is identical (14:13:13) noud48: it's fetched from different source (14:14:15) jperkin: you're doing that thing again where you aren't being specific about the problem. currently, the tarball from the first master site and the SHA1 and RMD160 in distinfo are perfectly matched. please be specific about what you believe to be the problem. (14:14:39) noud48: such numbers can mathematical collide (14:14:50) noud48: nice big guessw.but can still collide (14:21:28) morr: noud: a /usr/pkg/bin/bash script, ASCII text executable (14:21:37) morr: % wc -l noud (14:21:37) morr: 4 noud (14:21:38) noud48: no no pls (14:21:42) morr: it is very little (14:21:46) noud48: yes (14:22:00) noud48: and not even truely bash (14:23:01) noud48: or wait, what is the script content itself?? (14:23:06) noud48: if i may ask (14:23:28) noud48: 4 times echo (14:23:36) noud48: 'he is right and correct' (14:23:37) noud48: that maybe (14:23:48) noud48: i'll hush again (14:23:49) jperkin: 'exit 1' (14:23:49) noud48: mm (14:23:57) GitHub [~git...@sh2.rs.github.com] entered the room. (14:23:57) GitHub: [pkgsrc] jsonn pushed 13 new commits to trunk: http://git.io/Dm5vHg (14:23:57) GitHub: pkgsrc/trunk 6d44758 wen: Update to 1.232... (14:23:57) GitHub: pkgsrc/trunk 7755e8e wen: Updated time/p5-Time-Interval to 1.232 (14:23:57) GitHub: pkgsrc/trunk a57b0a1 wen: Update to 1.10... (14:23:57) GitHub left the room. (15:07:56) nimred left the room (quit: Quit: leaving). (15:11:16) noud48: jperkin, thanks super: Makefile 1.171 114 minutes jperkin Fix the first master site. (15:12:00) jperkin: you're welcome. (15:12:08) noud48: mm (15:12:21) noud48: cvs update -dP now (15:15:05) jakllsch: argh, somehow i unignored GitHub (15:15:39) noud48: jakllsch, what does that say?, if i may ask? to learn (15:17:09) noud48: it's fuck still addressing the mirror!!!!! : Connected to mimas-nxge0.switch.ch. (15:17:44) noud48: and we do not know if it's a blessed official mirror (15:18:09) morr: noud48; bash (15:18:41) noud48: seemingly, it is still not fixed (15:22:46) noud48: http://www.openssl.org/source/, mirrors sunsite.cnlab-switch.ch not found (15:24:09) noud48: so why is it in the Makefile?? and why are the official mirrors minus one not in the Makefile? (15:24:18) noud48: i'll PR okay (15:24:20) noud48: moment (15:24:50) Woodstock: $host sunsite.cnlab-switch.ch (15:24:51) Woodstock: sunsite.cnlab-switch.ch is an alias for mirror.switch.ch. (15:24:57) Woodstock: now look again. (15:25:02) noud48: okay (15:25:59) noud48: correct is alias, so now name the correct one (15:26:28) Woodstock: well, i wont, maybe someone else cares. (15:27:32) noud48: people that want most easy way to check if it's correct (15:27:49) noud48: i'll put PR, prio very low (15:28:04) nbjoerg: it's not a bug (15:34:03) noud48: true, it's cutting corners (15:34:47) noud48: and not notifying upstream about ftp://ftp.openssl.org/source/ [DE] (15:57:22) matthiasr [~matthi...@p5b16adce.dip.t-dialin.net] entered the room. (16:01:45) matthiasr left the room (quit: Ping timeout: 244 seconds). (16:07:34) petar left the room (quit: Quit: Lost terminal). (16:09:10) petar [~pe...@84-73-24-140.dclient.hispeed.ch] entered the room. (16:28:25) noud48: jperkin, while you are at it: http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=47521 (16:33:14) asarch [~asarch@189.151.16.71] entered the room. (16:44:51) jperkin: noud48: I don't mean to be rude, but everything about that PR is wrong. 1) PKGREVISION does not need to be bumped 2) there is no need for all those mirrors 3) linking two separate bug databases together is a bad idea 4) including openssl-dev is wrong 5) there's no need to contact openssl about it at all 6) as you are not a member of TNF you should not give the impression that you speak on behalf of the project (16:45:16) noud48: jperkin, did you already inform upstream?? (16:45:49) jperkin: there is no need to inform upstream (16:46:03) noud48: that's pretty impolite from you (16:46:09) nbjoerg: use RAII! (16:46:16) nbjoerg: not here (16:46:21) noud48: oardon..goog RAI (16:46:27) noud48: +I (16:52:42) noud48: 3) linking two separate bug databases together is a very good idea (16:53:03) noud48: 4) including openssl-dev because them selfs say warning is experimental (17:02:22) noud48: 6) as you are not a member of TNF you should not give the impression that you speak on behalf of the project SO TILL THIS IS FIXED NEVER EVER DROP ME THE LINE ANYMORE TO FIRST CONTACT UPSTEAM, AND THAT WITHOUT THE NBSD BADGE FOR YEARS. (17:12:47) juhuchapa left the room (quit: Ping timeout: 245 seconds). (17:17:21) sh4rm4 [~sh4rm@gateway/tor-sasl/sh4rm4] entered the room. (17:24:26) petar left the room (quit: Quit: Lost terminal). (17:26:10) petar [~pe...@84-73-24-140.dclient.hispeed.ch] entered the room. (17:29:28) _0bitcount [~ulise...@82.158.2.173.dyn.user.ono.com] entered the room. (17:38:12) xdmb left the room (quit: ). (17:44:47) meton left the room (quit: Ping timeout: 264 seconds). (17:50:36) meton [g...@lakka.kapsi.fi] entered the room. (18:23:17) bgpepi [~bgp...@ip-62-235-246-229.dsl.scarlet.be] entered the room. (18:32:16) GitHub [~git...@sh2.rs.github.com] entered the room. (18:32:17) GitHub: [pkgsrc] jsonn pushed 13 new commits to trunk: http://git.io/KVq2tw (18:32:17) GitHub: pkgsrc/trunk 5635de9 obache: Update libqt4 RPMs to 4.7.4-19.17.1 for CVE-2012-6093.... (18:32:17) GitHub: pkgsrc/trunk 6f7ca9c obache: Updated emulators/suse121_qt4 to 12.1nb2 (18:32:17) GitHub: pkgsrc/trunk 83441a2 hans: Use .tar.bz2 distfile so that no extra dependency on archivers/xz is... (18:32:17) GitHub left the room. (18:46:38) noud48: anyone already addressing pkg/47488: textproc/xalan-c got removed; find replacement in wip/xalan-c by chance? (18:46:45) noud48: saves me a post at there mail list (18:49:31) petar left the room (quit: Quit: Lost terminal). (18:50:38) Riastradh [~riastradh@fsf/member/riastradh] entered the room. (19:02:48) nimred [~nim...@srv229.dedi64.de] entered the room. (19:02:48) nimred left the room (quit: Changing host). (19:02:48) nimred [~nimred@unaffiliated/nahra] entered the room. (19:15:52) asarch left the room (quit: Quit: Ex-Chat). (19:25:11) nimred left the room (quit: Quit: leaving). (19:27:26) nimred [~nimred@unaffiliated/nahra] entered the room. (19:29:31) nimred left the room (quit: Client Quit). (19:32:23) noud48: (not so fun: Phone directory of the CS Department * BLOCKED *) (19:33:38) matthiasr [~matthiasr@2001:6f8:1c35:0:9407:e1b3:1da1:f03d] entered the room. (19:37:47) matthiasr left the room (quit: Ping timeout: 245 seconds). (19:44:41) xdmb [u2fsdgv...@ma.sdf.org] entered the room. (20:00:06) dh_work [~dholl...@macaran.eecs.harvard.edu] entered the room. (20:01:32) nimred [~nim...@srv229.dedi64.de] entered the room. (20:01:33) nimred left the room (quit: Changing host). (20:01:33) nimred [~nimred@unaffiliated/nahra] entered the room. (20:28:23) noud48: tada http://mail-index.netbsd.org/tech-pkg/2013/02/01/msg010732.html (20:29:26) [Sno] [~Sno]@p578b540c.dip0.t-ipconnect.de] entered the room. (20:29:33) dh_work: yes very nice, didn't you even read the comment I made like two weeks ago? (20:31:01) noud48: is it already back in? (20:31:16) noud48: is the comment somewhere relevant? i am just asking (20:32:31) noud48: and hi btw, i appreciate your nbsd work very much (20:53:44) morr: noud48; please don't send mails to third parties, what we are adding or removing is entirely our decision (20:54:11) nimred left the room (quit: Quit: leaving). (20:56:04) dh_work: "xqilla was a successor for libpathan, not xalan-c" (20:56:06) noud48: morr get me n...@netbsd.org (20:56:11) dh_work: right in the link to the PR that you included (20:56:24) noud48: dh_work, exact (20:57:47) noud48: and i did also mention, it's in wip/xalan-c to pull-up (just so nobody thinks i am _asking_ for work done for me) (20:58:28) nimred [~nim...@srv229.dedi64.de] entered the room. (20:58:29) nimred left the room (quit: Changing host). (20:58:29) nimred [~nimred@unaffiliated/nahra] entered the room. (20:58:35) noud48: |nobody thinks|not anybody must think| (21:00:45) dh_work: as I said in the PR, I have no idea why it was removed (21:01:07) dh_work: and it's now two years later during which time nobody asked to have it back (21:01:28) noud48: i know, no idea, nor me .. well, i take it to a mistake (21:01:53) noud48: by the person doing that, dunno top mind whom did, is non-relevant, or and for sure not to me. (21:01:54) _0bitcount left the room (quit: Quit: Leaving). (21:02:03) noud48: i'm asking now (21:02:17) noud48: not only now, already for over a week? (21:02:28) dh_work: anyway you'd be much more likely to get someone to do what you want if you don't go crashing about like a loose cannon (21:03:42) noud48: i did first ask full motivated and pollite and with work done just to pull-up, (21:03:57) noud48: if then someone does not do because s/he does not understand (21:04:17) noud48: and that not on 1 PR but near everything that does not touch a simple pkgsrc/Makefile (21:04:21) noud48: and that for years (21:04:26) noud48: well ..not years (21:04:30) noud48: but way to much (21:04:33) noud48: then wut (21:04:51) noud48: i'll forward you the mbalmer dialog (21:05:08) noud48: is already planed to paste it after the PR is close to the PR (21:06:16) noud48: and the shit keeps coming btw, see lateron (21:08:09) noud48: dh, voila, see for yourself (21:08:31) noud48: is@ has it as well also..but seems half to care (21:09:10) dh_work: like I said, you'd be much more likely to get someone to do what you want if you don't go crashing about like a loose cannon (21:09:41) noud48: i'll work back ward into older PRs as well where i can okay (21:10:00) noud48: plus i now have oval, work on all unix CVEs as well okay (21:10:19) noud48: CVE numbers seem to work very good i notice now (21:10:30) noud48: already for half a day or longer (21:10:39) noud48: already i guess for 1 or 2 days (21:10:54) noud48: is super motivating thing to get fixes and bumps (21:11:18) noud48: if not, see xalan-c at the moment, it moves again less (21:11:24) noud48: is my impression the week (21:11:25) noud48: so far (21:13:40) dh_work: shouting at people like you have been about xalan-c doesn't get things done. (21:13:48) dh_work: to be blunt: please stop. (21:14:51) noud48: i wish them all PRs where not taken as blunt, that too (21:15:03) noud48: and yes, just correct and stop (21:15:24) noud48: my whole intend was positive-constructive (21:15:41) _riz_: noud48: nobody understands you, and more to the point, nobody is going to make the effort because of the way you behave. (21:15:51) noud48: i did make the wip/replacement things remember (21:16:06) noud48: _riz_ i do not think so (21:16:35) noud48: and further, is not about me, is about the project how it shows and acts to and toward and with out-side. (21:16:56) noud48: serious damit: (21:16:57) noud48: (21:40:52) noud48: Marc, serious, what makes no sense of CVE-2013-0176, CVE-2012-4559, CVE-2012-4560, CVE-2012-4561 and CVE-2012-4562 and CVE-2013-0422 ?? (21:16:57) noud48: (21:41:48) mbalmer: seek help. I am done with you. (21:16:57) noud48: (21:41:58) noud48: are you now real telling the general global public that CVE-2013-0176, CVE-2012-4559, CVE-2012-4560, CVE-2012-4561 and CVE-2012-4562 and CVE-2013-0422 make no sense? (21:17:38) nimred left the room (quit: Read error: Connection reset by peer). (21:17:50) nimred [~nim...@srv229.dedi64.de] entered the room. (21:17:50) nimred left the room (quit: Changing host). (21:17:50) nimred [~nimred@unaffiliated/nahra] entered the room. (21:17:56) jperkin: noud48: no, he's right. it's great that you are passionate, and that you want to help pkgsrc, but the way you approach that is unacceptable. it would be great to have positive contributions from you, so all we ask is that you calm down, respect netiquette, and again realise that this is a volunteer project and if a PR you raise doesn't get done in 100 years, that still gives you no reason to shout at people. (21:17:58) noud48: and mind i am working toward a complete pullup nbsd exploits toward mitre.org (21:18:44) noud48: yes now understand !!!! the whole vulnerabilities and exploits base known to OSS (21:18:51) noud48: i down that, run it agains nbsd (21:18:57) noud48: and ask a f pull-up that all (21:19:04) noud48: at here, but sure at there as well (21:19:31) noud48: now pls any more comment on your own all behavior the most peeps that spoke out yes (21:20:22) dh_work: that doesn't make any sense. (21:21:08) noud48: it sure does (21:21:37) noud48: and if not, you are not up-to-date your vulnerabilities and exploits base known to OSS (21:21:45) noud48: capital unix and linux (21:21:54) dh_work: it does not. (21:22:07) dh_work: perhaps because it's lost in translation to english, but it does not make sense. (21:22:10) noud48: i can down it in xml, run it using tools, get reports (21:22:36) noud48: ow yes, those tools output them will be lost in translation. i do not think so. (21:23:08) noud48: just and only the nbsd audit will be minimal maybe, if it comes to local support (21:23:15) noud48: maybe (21:23:52) noud48: plus maybe better to talk in 6 hours innt (21:26:40) noud48: plus the 'english translation shit remark' is already near 2 centuries old in nbsd (21:29:01) noud48: general remark, if the one PR does not get fixed i still paste the bashing transcript at it (21:30:01) orz_ [~o...@amberdon.eecs.harvard.edu] entered the room. (21:32:06) dh_work: what do you mean by "english translation shit remark"? (21:33:19) noud48: are you now trying to bash me? (21:33:41) dh_work: no, I'm trying to explain to you that you are making no sense. (21:34:27) noud48: are you trying to get me in the closet? (21:34:43) dh_work: that question makes no sense. (21:34:51) noud48: well good then others do understand and do not understand you do not understand (21:34:58) noud48: nor point out what you not understand (21:35:21) noud48: and, you make a habit out of treathing peeps like this? (21:35:41) noud48: That's very demeaning (21:35:43) dh_work: I'm trying to understand what you're trying to say. (21:36:16) qjsgkem: noud48: been trying to understand you for many hour, but now a leg broke off my parsing table. back after coffee break. (21:36:18) noud48: And I also do not kick in and am not buying that/this (21:36:38) noud48: yea same at libssh.org and xalan.apache.org (21:36:40) dh_work: that statement does not make sense. (21:36:53) dh_work: (the "And I also do not kick in and am not buying that/this") (21:36:56) noud48: it sure does in this whole context (21:37:01) dh_work: it does not. (21:37:18) noud48: then you are hardly able to read and understand plain clear english (21:37:30) noud48: could be deformation a part you (21:37:31) dh_work: Um. (21:37:36) noud48: yep (21:37:49) dh_work: I happen to be a native English speaker. (21:37:50) qjsgkem: and noud48, please try to reread and process what jperkin wrote above. I couldn't express it better. (21:37:51) dh_work: Are you? (21:38:23) noud48: i take a random other example okay..hold on.. (21:38:46) noud48: http://theory.cs.uni-bonn.de/~ignatios/ is he for instance a native english speaking person (21:39:01) dh_work: I don't know. How is that relevant? (21:39:16) noud48: and dh, you yourself? and how would i know? are you welcome to show your own paper(s) and yiou your family in book? (21:39:34) dh_work: "yiou your family in book"? (21:39:37) dh_work: ENOPARSE. (21:39:42) qjsgkem: dh_work: oh, don't worry about that. I'm not a native speaker either, still I don't understand a lot of what noud48 says. (21:39:58) noud48: dh..you did write "I don't know." <-------- (21:40:07) dh_work: yes. (21:40:17) dh_work: I have no idea if Ignatios is a native English speaker. (21:40:39) dh_work: The question does not normally arise; he is perfectly understandable. (21:40:41) noud48: me neighter, and i guess not and i did already address you about you yourself in it (21:41:04) dh_work: My question remains: are *you* a native English speaker? (21:41:18) noud48: _he_ has a very shit evening today doing the PRs work (21:41:20) noud48: at the moment (21:41:27) noud48: thanks to your all behavior (21:42:20) dh_work: My question remains: are *you* a native English speaker? (21:42:25) noud48: yes (21:42:37) dh_work: All right then. (21:42:50) noud48: good. thanks..took you a long time to find out (21:43:06) noud48: wut state did you think i'm from? (21:44:05) dh_work: So then I have to conclude that when you make incoherent statements, it's because you aren't thinking clearly, not because they're coherent statements improperly translated from another language. (21:44:35) dh_work: Is that a reasonable conclusion? (21:44:48) noud48: no mudhole, Georgia, now understand (21:45:05) dh_work: I repeat: Is that a reasonable conclusion? (21:45:15) htodd [~ht...@75-148-87-25-oregon.hfc.comcastbusiness.net] entered the room. (21:45:46) noud48: sute your self your own conclusions, however wrong. (21:45:56) dh_work: That is not the question. (21:45:57) dh_work: I repeat: Is that a reasonable conclusion? (21:46:01) noud48: i do not care your sick perverted tormented idea about me (21:46:24) noud48: what conclusion? able to now repeat me the conclusion yours? (21:46:36) dh_work: <dh_work> So then I have to conclude that when you make incoherent statements, it's because you aren't thinking clearly, not because they're coherent statements improperly translated from another language. (21:46:42) dh_work: <dh_work> Is that a reasonable conclusion? (21:47:00) noud48: you are plain wrong in your conclusion (21:47:15) noud48: there is not even a QUAD ECO in it (21:47:24) dh_work: Ok, it is wrong. How is it wrong? (21:47:31) noud48: bye (21:47:41) dh_work: You say you are a native speaker of English. (21:47:44) noud48: just wrong is okay for the moment (21:47:46) noud48: okay (21:47:50) noud48: a-okay? (21:47:55) noud48: or still shitting?? (21:47:56) dh_work: Therefore, what you say cannot be the result of translation. (21:48:02) dh_work: No, it is not okay. Please explain. (21:48:05) noud48: pfffffffffffffffffff (21:48:22) noud48: hold on..need now a moment for person me and laughter (21:48:31) noud48: and to reflex this ;) (21:48:34) orz_: Too many times explaining the silly words. (21:49:04) dh_work: Really, please explain. (21:49:44) qjsgkem: I've seen many English speakers, native ones and nonnative ones. I have a hard time trying to remember one whose utterances were comparably hard to parse. (21:49:46) noud48: no explenation, darn i am shit in spelling there you got me, but yea you are right, this all from my side is indeed w/o translation (21:49:56) noud48: no translator needed on this all (21:50:06) noud48: here there an here local strange word (21:50:21) noud48: or vewwy vewwy wierd pronounchionation (21:50:33) noud48: there shitty spelling again (i guess) (21:50:46) noud48: i should activate one the spellers in pidgin (21:50:55) dh_work: Spelling isn't the problem. (21:50:58) noud48: and be able to deactivate and such (21:51:12) noud48: still the festival speach synth thing is buggy -( me bad (21:51:23) noud48: o spelling is doable, good (21:51:25) noud48: thanks (21:51:28) noud48: 2 down (21:51:47) dh_work: You say things like "And I also do not kick in and am not buying that/this" that are correctly spelled, and have more or less correct English grammar, but make no sense. (21:52:29) noud48: that is a very old nbsd trick too, question the this and thats (21:52:32) noud48: the references (21:52:34) noud48: i know (21:52:42) dh_work: There is no 'trick' here. (21:52:51) dh_work: I am *trying* to communicate with you. (21:52:56) noud48: okay, let's say, it shows (21:53:23) noud48: okay, but lets shift up-ward toward *communicate* (21:53:40) orz_: Why explaining? You are not a *camper*! You are too *hard*! (21:55:46) dh_work: All right, let's communicate. (21:56:19) dh_work: Can you communicate to me what you meant by "now pls any more comment on your own all behavior the most peeps that (21:56:23) dh_work: +spoke out yes"? (21:57:04) noud48: i did already take transcript this minus the your last 3 lines.. (21:57:11) noud48: ..i'll take that too okay (21:59:07) dh_work: Are you interested in communicating? (21:59:44) orz_: Is it time for *playing* yet? (22:00:30) noud48: yea, lets play ball and wall (22:00:37) dh_work: What is that? (22:00:51) noud48: is a ball, a wall..and your and my hand (22:01:04) noud48: like squash..but then ..just hand ball and wall (22:01:17) noud48: is also an expression..you guess why (22:01:21) noud48: are you uk?? (22:01:56) Woodstock: i really wonder why pdksh on SunOS occasionally gets so confused when it reads a script from stdin (22:01:59) Woodstock: pdksh: <stdin>[9]: no closing quote (22:02:07) Woodstock: jperkin: did you ever see that in your builds? (22:02:19) dh_work: probably because both pdksh and solaris are trash :-) (22:02:20) jperkin: I don't recall that one (22:02:34) noud48: Woodstock those are just syntax errors thos script that shows up (22:02:48) noud48: those* (22:02:49) Woodstock: dh_work: you're entering a world of pain... :) (22:03:22) Woodstock: it's not, it's gone when trying again. basically, pdksh inserts a line break at a random point in the insert and then gets utterly confused about it. (22:03:37) dh_work: that sounds like the bug we had in sh (22:03:49) noud48: no like a script bug (22:03:50) noud48: for sure (22:03:54) dh_work: you sure it's pdksh? it seems unlikely for that issue to reappear in a different code base (22:03:58) noud48: send to no...@home.nl (22:04:44) Woodstock: dh_work: yes, it's pdksh. i've seen it ever since i started doing bulk builds on sunos. (22:05:18) dh_work: weird. (22:05:55) jperkin: mmm bash (22:06:11) Woodstock: yes, but i've seen funny stuff with bash too, on 5.10 at least :) (22:06:11) noud48: side step one and side step 2 (22:06:17) Woodstock: like random segfaults (22:08:04) noud48: o bash things, you can send the history things as well, is okay (22:08:56) noud48: euuu, if you do not want to transport that i transport myself (maybe) (22:13:56) qjsgkem left the room (quit: Ping timeout: 252 seconds). (22:15:44) qjsgkem [bernh...@p4fc543d1.dip.t-dialin.net] entered the room. (22:23:20) Riastradh left the room (quit: Ping timeout: 276 seconds). (22:38:43) Riastradh [~riastradh@fsf/member/riastradh] entered the room. (22:45:56) GitHub [~git...@sh4.rs.github.com] entered the room. (22:45:56) GitHub: [pkgsrc] jsonn pushed 2 new commits to trunk: http://git.io/NrMh4w (22:45:56) GitHub: pkgsrc/trunk fde7922 jperkin: Spell XTHREAD_CPPFLAGS correctly. This is confirmed required on Solaris, so... (22:45:56) GitHub: pkgsrc/trunk d03ac43 is: Commit missing file, and fix the version gate. Thanks to Noud de Brouwer... (22:45:56) GitHub left the room. -- noud
