From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2181 invoked by alias); 12 Jul 2019 07:50:40 -0000 Mailing-List: contact bzip2-devel-help@sourceware.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Sender: bzip2-devel-owner@sourceware.org Received: (qmail 2171 invoked by uid 89); 12 Jul 2019 07:50:39 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.100.3 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-26.9 required=5.0 tests=BAYES_00,GIT_PATCH_0,GIT_PATCH_1,GIT_PATCH_2,GIT_PATCH_3 autolearn=ham version=3.3.1 spammy=HTo:U*mark, para, quality, website X-Spam-Status: No, score=-26.9 required=5.0 tests=BAYES_00,GIT_PATCH_0,GIT_PATCH_1,GIT_PATCH_2,GIT_PATCH_3 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on sourceware.org X-Spam-Level: X-HELO: black.bookofsand.co.uk DKIM-Filter: OpenDKIM Filter v2.11.0 squarecat1.vs.mythic-beasts.com BDFB52E9A6 DKIM-Filter: OpenDKIM Filter v2.11.0 mail.kestrel.ws 6AE22244D2 Reply-To: jseward@acm.org Subject: Re: [PATCH] Replace project contact email with bzip2-devel@sourceware.org. To: Mark Wielaard , bzip2-devel@sourceware.org References: <1562868211-28019-1-git-send-email-mark@klomp.org> From: Julian Seward Message-ID: <06d57235-b5c4-fd7c-6471-656735420e8c@acm.org> Date: Tue, 01 Jan 2019 00:00:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: <1562868211-28019-1-git-send-email-mark@klomp.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-SW-Source: 2019-q3/txt/msg00028.txt.bz2 Hi Mark, That's all absolutely fine. Please do update as per your patch. J On 11/07/2019 20:03, Mark Wielaard wrote: > Hi Julian, > > As discussed on irc this updates the contact information to the > community mailinglist instead of it all going to you personally. > I'll update the website and generated manual too. I'll also remove > this paragraph from the website: > > If you can be bothered, please > email me to say you've got a > copy. It's nice to know where this stuff gets to. > > Unless you want to keep that. > > Cheers, > > Mark > > Keep Julian's email as author information, but redirect general > project feedback in the code and manual to the community mailinglist. > --- > README | 4 ++-- > bzip2.c | 8 ++++---- > bzlib.c | 4 ++-- > entities.xml | 3 ++- > manual.xml | 8 ++++---- > 5 files changed, 14 insertions(+), 13 deletions(-) > > diff --git a/README b/README > index 64873f9..42543d1 100644 > --- a/README > +++ b/README > @@ -165,8 +165,8 @@ WHAT'S NEW IN 1.0.x ? > > See the CHANGES file. > > -I hope you find bzip2 useful. Feel free to contact me at > - jseward@acm.org > +I hope you find bzip2 useful. Feel free to contact the developers at > + bzip2-devel@sourceware.org > if you have any suggestions or queries. Many people mailed me with > comments, suggestions and patches after the releases of bzip-0.15, > bzip-0.21, and bzip2 versions 0.1pl2, 0.9.0, 0.9.5, 1.0.0, 1.0.1, > diff --git a/bzip2.c b/bzip2.c > index 76c6c94..01a41d2 100644 > --- a/bzip2.c > +++ b/bzip2.c > @@ -748,8 +748,8 @@ void panic ( const Char* s ) > fprintf ( stderr, > "\n%s: PANIC -- internal consistency error:\n" > "\t%s\n" > - "\tThis is a BUG. Please report it to me at:\n" > - "\tjseward@acm.org\n", > + "\tThis is a BUG. Please report it to:\n" > + "\tbzip2-devel@sourceware.org\n", > progName, s ); > showFileNames(); > cleanUpAndFail( 3 ); > @@ -829,7 +829,7 @@ void mySIGSEGVorSIGBUScatcher ( IntNative n ) > " The user's manual, Section 4.3, has more info on (1) and (2).\n" > " \n" > " If you suspect this is a bug in bzip2, or are unsure about (1)\n" > - " or (2), feel free to report it to me at: jseward@acm.org.\n" > + " or (2), feel free to report it to: bzip2-devel@sourceware.org.\n" > " Section 4.3 of the user's manual describes the info a useful\n" > " bug report should have. If the manual is available on your\n" > " system, please try and read it before mailing me. If you don't\n" > @@ -852,7 +852,7 @@ void mySIGSEGVorSIGBUScatcher ( IntNative n ) > " The user's manual, Section 4.3, has more info on (2) and (3).\n" > " \n" > " If you suspect this is a bug in bzip2, or are unsure about (2)\n" > - " or (3), feel free to report it to me at: jseward@acm.org.\n" > + " or (3), feel free to report it to: bzip2-devel@sourceware.org.\n" > " Section 4.3 of the user's manual describes the info a useful\n" > " bug report should have. If the manual is available on your\n" > " system, please try and read it before mailing me. If you don't\n" > diff --git a/bzlib.c b/bzlib.c > index f9da295..2dbe666 100644 > --- a/bzlib.c > +++ b/bzlib.c > @@ -43,12 +43,12 @@ void BZ2_bz__AssertH__fail ( int errcode ) > fprintf(stderr, > "\n\nbzip2/libbzip2: internal error number %d.\n" > "This is a bug in bzip2/libbzip2, %s.\n" > - "Please report it to me at: jseward@acm.org. If this happened\n" > + "Please report it to: bzip2-devel@sourceware.org. If this happened\n" > "when you were using some program which uses libbzip2 as a\n" > "component, you should also report this bug to the author(s)\n" > "of that program. Please make an effort to report this bug;\n" > "timely and accurate bug reports eventually lead to higher\n" > - "quality software. Thanks. Julian Seward, 10 December 2007.\n\n", > + "quality software. Thanks.\n\n", > errcode, > BZ2_bzlibVersion() > ); > diff --git a/entities.xml b/entities.xml > index 3016674..a415062 100644 > --- a/entities.xml > +++ b/entities.xml > @@ -1,6 +1,7 @@ > > > - > + > + > > > > diff --git a/manual.xml b/manual.xml > index b177bbf..b99e480 100644 > --- a/manual.xml > +++ b/manual.xml > @@ -653,7 +653,7 @@ unsigned 64-bit integer. > AUTHOR > > Julian Seward, > -&bz-email; > +&bz-author; > > The ideas embodied in > bzip2 are due to (at least) the > @@ -2487,12 +2487,12 @@ message: >
> bzip2/libbzip2: internal error number N. > This is a bug in bzip2/libbzip2, &bz-version; of &bz-date;. > -Please report it to me at: &bz-email;. If this happened > +Please report it to: &bz-email;. If this happened > when you were using some program which uses libbzip2 as a > component, you should also report this bug to the author(s) > of that program. Please make an effort to report this bug; > timely and accurate bug reports eventually lead to higher > -quality software. Thanks. Julian Seward, &bz-date;. > +quality software. Thanks. >
> > where N is some error code > @@ -2537,7 +2537,7 @@ recovered from. > Everything related to Windows has been contributed by > Yoshioka Tsuneo > (tsuneo@rr.iij4u.or.jp), so > -you should send your queries to him (but perhaps Cc: me, > +you should send your queries to him (but please Cc: > &bz-email;). > > My vague understanding of what to do is: using Visual C++ > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 36748 invoked by alias); 11 Jul 2019 18:13:44 -0000 Mailing-List: contact bzip2-devel-help@sourceware.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Sender: bzip2-devel-owner@sourceware.org Received: (qmail 36738 invoked by uid 89); 11 Jul 2019 18:13:44 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.100.3 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy= X-Spam-Status: No, score=-6.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on sourceware.org X-Spam-Level: X-HELO: gnu.wildebeest.org Message-ID: <38c77651b5696da99560f36d5285741ca9d1b514.camel@klomp.org> Subject: Re: [PATCH] Replace project contact email with bzip2-devel@sourceware.org. From: Mark Wielaard To: bzip2-devel@sourceware.org Cc: Julian Seward Date: Tue, 01 Jan 2019 00:00:00 -0000 In-Reply-To: <1562868211-28019-1-git-send-email-mark@klomp.org> References: <1562868211-28019-1-git-send-email-mark@klomp.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-2.el7) Mime-Version: 1.0 X-Spam-Flag: NO X-SW-Source: 2019-q3/txt/msg00024.txt.bz2 On Thu, 2019-07-11 at 20:03 +0200, Mark Wielaard wrote: > @@ -829,7 +829,7 @@ void mySIGSEGVorSIGBUScatcher ( IntNative n ) > " The user's manual, Section 4.3, has more info on (1) and (2).\= n" > " \n" > " If you suspect this is a bug in bzip2, or are unsure about (1)= \n" > - " or (2), feel free to report it to me at: jseward@acm.org.\n" > + " or (2), feel free to report it to: bzip2-devel@sourceware.org.= \n" > " Section 4.3 of the user's manual describes the info a useful\n" > " bug report should have. If the manual is available on your\n" > " system, please try and read it before mailing me. If you don'= t\n" > @@ -852,7 +852,7 @@ void mySIGSEGVorSIGBUScatcher ( IntNative n ) > " The user's manual, Section 4.3, has more info on (2) and (3).\= n" > " \n" > " If you suspect this is a bug in bzip2, or are unsure about (2)= \n" > - " or (3), feel free to report it to me at: jseward@acm.org.\n" > + " or (3), feel free to report it to: bzip2-devel@sourceware.org.= \n" > " Section 4.3 of the user's manual describes the info a useful\n" > " bug report should have. If the manual is available on your\n" > " system, please try and read it before mailing me. If you don'= t\n" BTW. This SIGSEGV/BUS signal handler might be why we haven't seen more crashers when fuzzing bzip2 directly. That is another reason to introduce targeted fuzzer entry points. Cheers, Mark From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 129683 invoked by alias); 12 Jul 2019 18:51:53 -0000 Mailing-List: contact bzip2-devel-help@sourceware.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Sender: bzip2-devel-owner@sourceware.org Received: (qmail 129674 invoked by uid 89); 12 Jul 2019 18:51:52 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.100.3 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=invasive, configurations X-Spam-Status: No, score=-6.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on sourceware.org X-Spam-Level: X-HELO: gnu.wildebeest.org Message-ID: Subject: 1.0.8 release (Was: [PATCH] Replace project contact email with bzip2-devel@sourceware.org) From: Mark Wielaard To: jseward@acm.org, bzip2-devel@sourceware.org Date: Tue, 01 Jan 2019 00:00:00 -0000 In-Reply-To: <06d57235-b5c4-fd7c-6471-656735420e8c@acm.org> References: <1562868211-28019-1-git-send-email-mark@klomp.org> <06d57235-b5c4-fd7c-6471-656735420e8c@acm.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-2.el7) Mime-Version: 1.0 X-Spam-Flag: NO X-SW-Source: 2019-q3/txt/msg00029.txt.bz2 Hi, On Fri, 2019-07-12 at 09:50 +0200, Julian Seward wrote: > That's all absolutely fine. Please do update as per your patch. Thanks. I also applied the last three distro patches for the bzgrep and bzdiff script cleanups. There are not many updates since 1.0.7, but that seems good if we just intend this to be a fixup release to. The nSelectors relaxation is probably something we want to get out asap, so people can unbzip2 all files again they could before (even if they were technically "broken"). Unless someone objects I would like to do a 1.0.8 release this weekend. With the updates this should all be automated now by running and following the instructions with the ./prepare-release.sh 1.0.8 and ./release-update.sh 1.0.8 scripts. I feel we did lots of testing now and the integration of the bzip2- tests in the buildbot really helps. I have been using a fuzzer (afl) for a week on various configurations, but did not find any issues. I am working on better fuzzer targets for better coverage, but that can wait till after the release (it is also a bit invasive since it requires new build targets). The one thing that might have been nice to integrate is the O_CLOEXEC fix, especially for multi-threaded programs that use libbzip2 and might fork/exec. But while O_CLOEXEC is now in POSIX, the fopen "e" mode as used in the proposed patches is GNU/Linux specific. I don't believe the guards proposed (just define BZ_UNIX to 1 and hope for the best) is the most conservative option possible. In summary the (important) fixes for 1.0.8 are: * Accept as many selectors as the file format allows. This relaxes the fix for CVE-2019-12900 from 1.0.7 so that bzip2 allows decompression of bz2 that use (too) many selectors again. * Fix handling of large (> 4GB) files on Windows. * Cleanup of bzdiff and bzgrep scripts so they don't use any bash extensions and handle multiple archives correctly. * There is now a bz2-files testsuite at https://sourceware.org/git/bzip2-tests.git Cheers, Mark From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 114906 invoked by alias); 11 Jul 2019 18:04:14 -0000 Mailing-List: contact bzip2-devel-help@sourceware.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Sender: bzip2-devel-owner@sourceware.org Received: (qmail 114836 invoked by uid 89); 11 Jul 2019 18:04:14 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.100.3 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-19.0 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_0,GIT_PATCH_1,GIT_PATCH_2,GIT_PATCH_3,SPF_PASS autolearn=ham version=3.3.1 spammy=december, December, recovered, blockquote X-Spam-Status: No, score=-19.0 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_0,GIT_PATCH_1,GIT_PATCH_2,GIT_PATCH_3,SPF_PASS autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on sourceware.org X-Spam-Level: X-HELO: gnu.wildebeest.org From: Mark Wielaard To: bzip2-devel@sourceware.org Cc: Julian Seward , Mark Wielaard Subject: [PATCH] Replace project contact email with bzip2-devel@sourceware.org. Date: Tue, 01 Jan 2019 00:00:00 -0000 Message-Id: <1562868211-28019-1-git-send-email-mark@klomp.org> X-Mailer: git-send-email 1.8.3.1 X-Spam-Flag: NO X-SW-Source: 2019-q3/txt/msg00022.txt.bz2 Hi Julian, As discussed on irc this updates the contact information to the community mailinglist instead of it all going to you personally. I'll update the website and generated manual too. I'll also remove this paragraph from the website: If you can be bothered, please email me to say you've got a copy. It's nice to know where this stuff gets to. Unless you want to keep that. Cheers, Mark Keep Julian's email as author information, but redirect general project feedback in the code and manual to the community mailinglist. --- README | 4 ++-- bzip2.c | 8 ++++---- bzlib.c | 4 ++-- entities.xml | 3 ++- manual.xml | 8 ++++---- 5 files changed, 14 insertions(+), 13 deletions(-) diff --git a/README b/README index 64873f9..42543d1 100644 --- a/README +++ b/README @@ -165,8 +165,8 @@ WHAT'S NEW IN 1.0.x ? See the CHANGES file. -I hope you find bzip2 useful. Feel free to contact me at - jseward@acm.org +I hope you find bzip2 useful. Feel free to contact the developers at + bzip2-devel@sourceware.org if you have any suggestions or queries. Many people mailed me with comments, suggestions and patches after the releases of bzip-0.15, bzip-0.21, and bzip2 versions 0.1pl2, 0.9.0, 0.9.5, 1.0.0, 1.0.1, diff --git a/bzip2.c b/bzip2.c index 76c6c94..01a41d2 100644 --- a/bzip2.c +++ b/bzip2.c @@ -748,8 +748,8 @@ void panic ( const Char* s ) fprintf ( stderr, "\n%s: PANIC -- internal consistency error:\n" "\t%s\n" - "\tThis is a BUG. Please report it to me at:\n" - "\tjseward@acm.org\n", + "\tThis is a BUG. Please report it to:\n" + "\tbzip2-devel@sourceware.org\n", progName, s ); showFileNames(); cleanUpAndFail( 3 ); @@ -829,7 +829,7 @@ void mySIGSEGVorSIGBUScatcher ( IntNative n ) " The user's manual, Section 4.3, has more info on (1) and (2).\n" " \n" " If you suspect this is a bug in bzip2, or are unsure about (1)\n" - " or (2), feel free to report it to me at: jseward@acm.org.\n" + " or (2), feel free to report it to: bzip2-devel@sourceware.org.\n" " Section 4.3 of the user's manual describes the info a useful\n" " bug report should have. If the manual is available on your\n" " system, please try and read it before mailing me. If you don't\n" @@ -852,7 +852,7 @@ void mySIGSEGVorSIGBUScatcher ( IntNative n ) " The user's manual, Section 4.3, has more info on (2) and (3).\n" " \n" " If you suspect this is a bug in bzip2, or are unsure about (2)\n" - " or (3), feel free to report it to me at: jseward@acm.org.\n" + " or (3), feel free to report it to: bzip2-devel@sourceware.org.\n" " Section 4.3 of the user's manual describes the info a useful\n" " bug report should have. If the manual is available on your\n" " system, please try and read it before mailing me. If you don't\n" diff --git a/bzlib.c b/bzlib.c index f9da295..2dbe666 100644 --- a/bzlib.c +++ b/bzlib.c @@ -43,12 +43,12 @@ void BZ2_bz__AssertH__fail ( int errcode ) fprintf(stderr, "\n\nbzip2/libbzip2: internal error number %d.\n" "This is a bug in bzip2/libbzip2, %s.\n" - "Please report it to me at: jseward@acm.org. If this happened\n" + "Please report it to: bzip2-devel@sourceware.org. If this happened\n" "when you were using some program which uses libbzip2 as a\n" "component, you should also report this bug to the author(s)\n" "of that program. Please make an effort to report this bug;\n" "timely and accurate bug reports eventually lead to higher\n" - "quality software. Thanks. Julian Seward, 10 December 2007.\n\n", + "quality software. Thanks.\n\n", errcode, BZ2_bzlibVersion() ); diff --git a/entities.xml b/entities.xml index 3016674..a415062 100644 --- a/entities.xml +++ b/entities.xml @@ -1,6 +1,7 @@ - + + diff --git a/manual.xml b/manual.xml index b177bbf..b99e480 100644 --- a/manual.xml +++ b/manual.xml @@ -653,7 +653,7 @@ unsigned 64-bit integer. AUTHOR Julian Seward, -&bz-email; +&bz-author; The ideas embodied in bzip2 are due to (at least) the @@ -2487,12 +2487,12 @@ message:
bzip2/libbzip2: internal error number N. This is a bug in bzip2/libbzip2, &bz-version; of &bz-date;. -Please report it to me at: &bz-email;. If this happened +Please report it to: &bz-email;. If this happened when you were using some program which uses libbzip2 as a component, you should also report this bug to the author(s) of that program. Please make an effort to report this bug; timely and accurate bug reports eventually lead to higher -quality software. Thanks. Julian Seward, &bz-date;. +quality software. Thanks.
where N is some error code @@ -2537,7 +2537,7 @@ recovered from. Everything related to Windows has been contributed by Yoshioka Tsuneo (tsuneo@rr.iij4u.or.jp), so -you should send your queries to him (but perhaps Cc: me, +you should send your queries to him (but please Cc: &bz-email;). My vague understanding of what to do is: using Visual C++ -- 1.8.3.1