[Pkg-crosswire-devel] RFS: bibledit/5.0.105-1 [NMU]
teusjannette at gmail.com
Wed Apr 5 11:04:15 BST 2017
Thanks for looking at the package, and for the quick feedback.
The lintian warning about the debian/changelog was now fixed, the line was
shortened a bit to stay within the 80 character limit.
To make the transition from the old bibledit-gtk to the new bibledit
easier, package bibledit-gtk was introduced again, as transitional dummy
package to bibledit, and in a similar way bibledit-gtk-data as a
transitional dummy package to bibledit-data.
I tested the upgrade cycle from bibledit-gtk 4.9 in Debian sid to the new
bibledit 5.x. It works okay now, after the fields Depends, Replaces, and
Breaks, were added to debian/control.
The debian/changelog now uploads to the experimental pool of packages,
rather than to the unstable distribution. I had not realized that Debian 9
Stretch is so close to release now. Yup, good plan to upload this first
release to experimental.
After stretch gets frozen, the next upload could be targetted at unstable
again, even before release, or it needs to wait till after the release of
(Extra, unrelated, but perhaps interesting, info: There is also
"bibledit-desktop" (https://github.com/postiffm/bibledit-desktop), which
really is a continuation from bibledit-gtk, renamed to -desktop, and is
being developed independently by another developer.)
On Mon, 3 Apr 2017 at 19:42 Roberto C. Sánchez <roberto at debian.org> wrote:
> With attachment this time.
> On Mon, Apr 03, 2017 at 01:37:44PM -0400, Roberto C. Sánchez wrote:
> > On Mon, Apr 03, 2017 at 04:46:05PM +0000, Teus Benschop wrote:
> > > Hi Roberto,
> > > Indeed, I had not thought of pushing the upstream and pristine-tar
> > > branches to the remote repository. Those two branches have now been
> > > to the remote, and I expect it now to work fine. I did a quick check
> > > whether the file "bibledit_5.0.140.orig.tar.gz.delta" exists in the
> > > repo, and it does exists there, so now after pushing them, I expect
> it to
> > > be okay now.
> > > Thanks for spotting the issue, and for recommending the fix, and for
> > > trying to build from Alioth.
> > > Regards,
> > > Teus.
> > Hi Teus,
> > No problem at all on my end. Thank you for getting everything corrected
> > so quickly.
> > There are two additional items that need to be addressed before we can
> > upload:
> > - the debian/changelog causes lintian to complain (see attached)
> > - we will need a transitional dummy package for bibledit-gtk
> > I should have realized earlier that a transitional package would be
> > needed. Basically, we want to make sure that users don't end up with
> > orphaned packages on their systems. Right now if someone has
> > bibledit-gtk installed, when the new bibledit package becomes available,
> > the user will not see that it is the logical upgrade from bibledit-gtk.
> > The way to handle this is to add the bibledit-gtk package back to
> > debian/control and make it depend on bibledit. That will ensure that
> > the right thing happens. We will need to have that transitional package
> > in place until after the release of buster, at which time it can be
> > removed.
> > Please make sure that you have tested the install -> upgrade cycle from
> > the bibledit-gtk 4.9 packages to the new bibledit 5.0 packages. That
> > will ensure that upgrades work properly for users.
> > Also, one additional question: is unstable the intended target for this
> > upload? Since we are so close to release of stretch, it might be better
> > to target the first upload to experimental.
> > Regards,
> > -Roberto
> > --
> > Roberto C. Sánchez
> > _______________________________________________
> > Pkg-crosswire-devel mailing list
> > Pkg-crosswire-devel at lists.alioth.debian.org
> Roberto C. Sánchez
> Pkg-crosswire-devel mailing list
> Pkg-crosswire-devel at lists.alioth.debian.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pkg-crosswire-devel