[Pkg-crosswire-devel] RFS: bibledit/5.0.105-1 [NMU]

[Roberto C. Sánchez]

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 pushed
> >    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 local
> >    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
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel


-- 
Roberto C. Sánchez
-------------- next part --------------
N: Using profile debian/main.
N: Setting up lab in /tmp/temp-lintian-lab-CN2tjhb1Gd ...
N: Unpacking packages in group bibledit/5.0.140-1
N: ----
N: Processing changes file bibledit (version 5.0.140-1, arch source all amd64) ...
N: ----
N: Processing source package bibledit (version 5.0.140-1, arch source) ...
N: ----
N: Processing binary package bibledit-data (version 5.0.140-1, arch all) ...
W: bibledit-data: debian-changelog-line-too-long line 16
N: 
N:    The given line of the latest changelog entry is over 80 columns. Such
N:    changelog entries may look poor in terminal windows and mail messages
N:    and be annoying to read. Please wrap changelog entries at 80 columns or
N:    less where possible.
N:    
N:    Severity: normal, Certainty: certain
N:    
N:    Check: changelog-file, Type: binary
N: 
N: ----
N: Processing binary package bibledit-dbgsym (version 5.0.140-1, arch amd64) ...
N: ----
N: Processing binary package bibledit (version 5.0.140-1, arch amd64) ...
W: bibledit: debian-changelog-line-too-long line 16
N: 33 tags overridden (2 errors, 31 info)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-crosswire-devel/attachments/20170403/1af7eccc/attachment.sig>