[pkg-crosswire-devel] tasks for transition

[Daniel Glassey]

On Sat, Nov 3, 2018 at 11:22 PM Teus Benschop <teusjannette at gmail.com>
wrote:

> Hi Daniel,
>
> Thank you for the encouragement to continue packaging, in the other email.
>

Hi Teus,
You are welcome :)


> You have given a number of tasks required for a successful transition of
> libsword. I can do the work needed to get the transition to libsword-1.8.1
> completed.
>

Great :)


> I have taken note of all the steps you outlined in this email.
>
> You asked me to research Debian transitions. I have done that.
> There's a very good page that describes it all:
> https://wiki.debian.org/Teams/ReleaseTeam/Transitions
> 1. The wiki gives a summary of the steps in the workflow.
> 2. It then gives a fuller description of each step.
> 3. It ends with more in-depth information about how the transitions work
> in general. This is very informative, for me, to understand how it all
> works.
>

Yep, glad you found that ok.


> I think everything is clear, at this stage. I'll discuss things with the
> list where you asked that to do, or where else I might need help.
>
> One of the reverse dependencies on libsword* is Xiphos. That package
> xiphos now fails to build on architecture ppc64el.
> https://buildd.debian.org/status/package.php?p=xiphos
> This build error is new to me. Or I have not spotted it before. It used to
> builds there without problems.
> I need to look into this, and probably do a new upload to unstable, with
> the patch applied, to make it build well in the current situation.
> And do all of this before going into the transitions.
>

That kind of problem on another architecture is harder to track down
without access to the porterboxes. You are allowed to ask for permission
for that (and with hindsight that would have been a useful exercise) but I
went ahead and I think I found the problem. It is actually in a header in
sword. I included a patch for that in the version of sword in experimental
but we'll have to wait until we see if xiphos will build against that on
ppc64el.
Though, since I have access I may go onto the porterbox again and make a
manual build just to check one of these days before that.

One more thing is to email your ssh public key Ian Jackson, the maintainer
of dgit so that you are allowed to dgit push-source your DMd packages. At
least, I recently saw a blog post that that's what DMs are to do, but there
may be better info somewhere else.

Regards,
Daniel

On Sat, 3 Nov 2018 at 13:16 Daniel Glassey <dglassey at gmail.com> wrote:
>
>> Hi Teus,
>>
>> Here are some tasks to get ready for the transition.
>>
>> Please work on all the applications that have a build dependency on
>> libsword-dev.
>>
>> Create a debian/experimental branch in the salsa team git repo for the
>> application. Do the changes there along with any other changes you are
>> working on.
>>
>> Change that dependency to be on libsword-dev 1.8.1 alone but >= the
>> version in experimental. Change the changelog so that the upload will go to
>> experimental.
>>
>> If you have a Debian unstable vm or a chroot that you know how to run gui
>> applications on then build the package locally and install it and make sure
>> it works.
>>
>> Do not upload them until sword 1.8.1-6 gets through the NEW queue and all
>> the release architectures build it. Let us know before you are ready to
>> upload to experimental.
>>
>> Research Debian transitions and let us know what you find are the steps
>> we will need to go through.
>>
>> Regards,
>> Daniel
>>
> --
> Teus Benschop
> teusjannette at gmail.com
> 0318 712046
>