Date: Sat, 2 Feb 2019 01:00:38 +0100 From: Martin Matuska <mm@FreeBSD.org> To: Warner Losh <imp@bsdimp.com>, Eugene Grosbein <eugen@grosbein.net> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: Status of libarchive/bsdtar maintainership Message-ID: <111540a7-5d58-715c-bad7-7b843a642af6@FreeBSD.org> In-Reply-To: <CANCZdfq%2B=wTEf4XBExo3OeSY4m6TKzsK2U2bwcs=3CDQ=mRr7w@mail.gmail.com> References: <c9111214-fd3f-cfd8-f7fc-2613b014122f@grosbein.net> <CANCZdfq-=X0mPv4GzNqrmEFwPRUrg=B4OrGz=1c1rhp0ejs4wQ@mail.gmail.com> <5C53E4FE.1010501@grosbein.net> <CANCZdfq%2B=wTEf4XBExo3OeSY4m6TKzsK2U2bwcs=3CDQ=mRr7w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Warner and Eugene, our resources at the libarchive project are currently very limited and the progress is slow. The project founder and leader Tim Kientzle is irresponsive for more than a month now. The only active core developers are me and Joerg Sonnenberger (joerg@NetBSD). At the moment Joerg deals mostly with writing bugfixes for bugs found oss-fuzz and does some pull-request reviews. I am currently reviewing and merging bugfix and some feature pull requests from GitHub and have finally managed to set up automated testing via Cirrus CI that includes FreeBSD to speed up evaluation of new pull requests. We actually do rely on code coming from external developers. The fastest way of getting code in is submitting a pull request. If possible a testable one, including tests for the bugs fixed or features implemented. Martin On 02.02.19 00:35, Warner Losh wrote: > > > On Thu, Jan 31, 2019 at 11:19 PM Eugene Grosbein <eugen@grosbein.net > <mailto:eugen@grosbein.net>> wrote: > > On 01.02.2019 11:10, Warner Losh wrote: > > > On Thu, Jan 31, 2019, 8:22 PM Eugene Grosbein > <eugen@grosbein.net <mailto:eugen@grosbein.net> > <mailto:eugen@grosbein.net <mailto:eugen@grosbein.net>> wrote: > > > >=C2=A0 =C2=A0 =C2=A0Hi! > > > >=C2=A0 =C2=A0 =C2=A0I wonder what is status of our contrib/libarch= ive and > bsdtar/bsdcpio etc. in modern versions of FreeBSD > >=C2=A0 =C2=A0 =C2=A0in a sense of serious bug fixing. Long story s= hort: I faced > a bug in the libarchive bundled with 11.2 > >=C2=A0 =C2=A0 =C2=A0that makes it impossible to create reliable ba= ckups of live > file system or its subtree > >=C2=A0 =C2=A0 =C2=A0using cron+bsdtar utility that delegate actial= work to the > libarchive that just aborts > >=C2=A0 =C2=A0 =C2=A0if a file disappears (is removed) in process (= GNU tar > continues with just warning). > > > >=C2=A0 =C2=A0 =C2=A0This is serious issue for me as I used 'tar' c= ommand to make > backups for distinct subtrees > >=C2=A0 =C2=A0 =C2=A0since FreeBSD 6.x and when my GPS+ntpd subsyst= em went insane > and shifted system clock to 3 years > >=C2=A0 =C2=A0 =C2=A0in the future, I lost data in several thousand= s of RRD > databases and looked for backups to restore them > >=C2=A0 =C2=A0 =C2=A0and found only small portion of databases in t= he tar instead > of full backup. > > > >=C2=A0 =C2=A0 =C2=A0I've create the PR > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233006 and late= r > attached a patch > >=C2=A0 =C2=A0 =C2=A0solving the problem in same way as GNU tar dea= ls with it. > > > >=C2=A0 =C2=A0 =C2=A0Martin Matuska (mm) asked me to create an issu= e at GitHub > for libarchive. > >=C2=A0 =C2=A0 =C2=A0I have no GitHub account nor I need one, and h= e was so kind > and created it himself: > >=C2=A0 =C2=A0 =C2=A0https://github.com/libarchive/libarchive/issue= s/1082 > > > >=C2=A0 =C2=A0 =C2=A0Almost 3 months have passed and no response fr= om upstream. > >=C2=A0 =C2=A0 =C2=A0Should we go ahead and fix it despite of it is= part of contrib? > > > > > > If you fix it, protocol is to submit it upstream first. > > That was done 3 months ago. > > > I see the problem report in the github, but no pull request. Did I > miss it? > =C2=A0 > > > It causes fewer problems in the long run. While it is tempting > to just fix it in FreeBSD and move on, > > almost every time we've done that in the past someone else has > had to come in and fix the mess. > > > > Do you have a fix? Can you put it up for review somewhere? > > It is attached to mentioned PR: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233006#c6 > > > Did you submit it as a pull request? That seems to be how this > upstream takes in code. > > > We are no where near a release, so there is no reason to rush > this in. > > I waited for almost 3 months already. It seems, there would be no > response at all. > > > They didn't fix it in 3 months, sure. But it wasn't clear from the > issue that you had an actual fix (I certainly missed that the first > time through when I only looked at the github and not at our bug > database). I'd try submitting a pull request and see what happens. I'd > also send an email to mm@ telling him about the pull request and > asking when he'll have time to look into=C2=A0 integrating it or commen= ting > on it. If he won't have time to get to it soon, I'd make the commit > referencing the upstream pull request so the next person who imports > things will notice if they tweak it before accepting the request. > > Warner=C2=A0
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?111540a7-5d58-715c-bad7-7b843a642af6>