public inbox for bzip2-devel@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Santiago Ruano Rincón" <santiago@debian.org>
Cc: bzip2-devel@sourceware.org,
	Anibal Monsalve Salazar <anibal@debian.org>,
	Anthony Fok <foka@debian.org>,
	Federico Mena Quintero <federico@gnome.org>
Subject: Re: [PATCH] bzip2: Fix return value when combining --test,-t and -q.
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <c55e001242b3e6c33d429c2f5dab2fcd132bcb6b.camel@klomp.org> (raw)
In-Reply-To: <20190624083116.GN6125@bartik>

On Mon, 2019-06-24 at 10:31 +0200, Santiago Ruano Rincón wrote:
> For information, Federico Mena (in CC) is taking over the development
> of
> bzip2: https://people.gnome.org/~federico/blog/maintaining-bzip2.html
> 
> You should consider coordinating your efforts!

Thanks. I assumed Federico was already on the bzip2-devel mailinglist.
We did email earlier to discuss bzip2 maintenance and that all the
infrastructure was already setup on the new sourceware.org bzip2
project. But it seems we did some duplicate work. Sorry for the
miscommunication.

It looks like we picked at least similar patches for the C sources, so
those look mostly identical. I'll go over the remaining differences and
try to cherry-pick or merge them into the bzip2 git repo.

Some other files have been moved around, so it is harder to see whether
we did the same for the manual and other docs. And I explicitly didn't
touch the build system. I was looking at the autotools setup opensuse
uses, but that also uses libtool which would mean changing the bzip.so
verion/name. Which would be OK for Fedora and OpenSuse, since they
already changed it long ago, but it would not be good for Debian, which
uses the upstream libbz2.so.1.0 name. Also the buildbot, release
scripts and the automatic updating of the homepage/manual is somewhat
tied to the current setup.

So I was thinking, first do a new 1.0.7 release with just the distro
fixes and the updated project home, and then look at updating the rest
of the build infrastructure.

Cheers,

Mark

  reply	other threads:[~2019-06-24  9:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01  0:00 Mark Wielaard
2019-01-01  0:00 ` Santiago Ruano Rincón
2019-01-01  0:00   ` Mark Wielaard [this message]
2019-01-01  0:00     ` Some cherry-picks (Was: [PATCH] bzip2: Fix return value when combining --test,-t and -q.) Mark Wielaard
2019-01-01  0:00       ` Federico Mena Quintero
2019-01-01  0:00     ` Releasing bzip2 1.0.7 and 1.1.0 ? Was: [PATCH] bzip2: Fix return value when combining --test,-t and -q Mark Wielaard
2019-01-01  0:00       ` Mark Wielaard
2019-01-01  0:00         ` Federico Mena Quintero
2019-01-01  0:00           ` Mark Wielaard
2019-01-01  0:00             ` Federico Mena Quintero
2019-01-01  0:00               ` Mark Wielaard
2019-01-01  0:00                 ` Mark Wielaard
2019-01-01  0:00                   ` Federico Mena Quintero
2019-01-01  0:00                     ` Mark Wielaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c55e001242b3e6c33d429c2f5dab2fcd132bcb6b.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=anibal@debian.org \
    --cc=bzip2-devel@sourceware.org \
    --cc=federico@gnome.org \
    --cc=foka@debian.org \
    --cc=santiago@debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).