From: Eric Wong <e@80x24.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: meta@public-inbox.org
Subject: Re: public-inbox in Debian
Date: Thu, 4 Mar 2021 18:57:35 +0000 [thread overview]
Message-ID: <20210304185735.GB19350@dcvr> (raw)
In-Reply-To: <20210304092124.ssx2bgduyuqojzh2@pengutronix.de>
Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
> Hello Eric,
>
> On Thu, Mar 04, 2021 at 08:12:35AM +0000, Eric Wong wrote:
> > Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
> > > Hello,
> > >
> > > just a quick note to let you know that I uploaded public-inbox to
> > > Debian. The required review process by the ftp team was completed very
> > > quickly and the public-inbox package already landed in Debian sid.
> >
> > Awesome, thank you. I guess the next release (bullseye) is
> > starting to freeze.
>
> For bullseye it's already too late, see
> https://release.debian.org/bullseye/freeze_policy.html#soft
Ah, no worries. Maybe backports if there's demand (though 1.7
will support distro-agnostic "make install-symlinks" for
non-root users)
> > I've been trying to get a new release out ASAP but there's too
> > much left to do :<
> >
> > > https://tracker.debian.org/news/1234849/accepted-public-inbox-160-1-all-source-into-unstable-unstable/
> >
> > Any particular reason the package is 1.6.0-1 despite the
> >
> > "* Include changes from upstream bugfix release 1.6.1"
> >
> > change entry? Anyways, no big deal and thanks again for all
> > your work.
>
> Funny you ask. I chose to do it that way because I expected that an
> eventual 1.7.0 release won't include 1.6.1 as an ancestor and I thought
> it a good idea to have my upstream branch to be fast-forward only.
Actually, I merged 1.6.1 back into the tip of whatever branch
I was using and pushed it to master:
d49c0789d208e66121bfb68ff0c48d7612a7cd8e ("Merge remote-tracking branch 'origin/lei' into eidx")
8862c33ae93eea1af6246cd3c7a81e0a122186bf ("Merge tag 'v1.6.1' into eidx")
> Just before seeing your mail I already asked around for a nicer
> solution in the corresponding Debian irc channel, maybe I just have to
> accept a non-ff upstream branch. Shouldn't be a big deal.
>
> Your mail is just another confirmation that the currently used scheme is
> a bad idea. (Another is that the packaging page[1] nags that there is
> another upstream release that should be packaged.)
Right, no big deal.
Btw, since there's bb928d88ed4c72241a8d76bc792cdbd798e44470
("www: use PublicInbox::WwwStream") sitting in the stable-1.6
branch, would it be helpful to release v1.6.2 at some point?
I think 8b39c0757a7d6d62ff7f432c13ef4c497f1c804e
("ds: import croak properly") is worth pushing to stable-1.6,
maybe others...
Also, I'd appreciate if you or anybody else helps writing
release notes (in the form of what's in Documentation/RelNotes/)
since it's a bit of a drag for me.
> [1] https://tracker.debian.org/pkg/public-inbox
next prev parent reply other threads:[~2021-03-04 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 7:06 public-inbox in Debian Uwe Kleine-König
2021-03-04 8:12 ` Eric Wong
2021-03-04 9:21 ` Uwe Kleine-König
2021-03-04 18:57 ` Eric Wong [this message]
2021-03-04 20:33 ` Uwe Kleine-König
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210304185735.GB19350@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).