On 7/22/22 09:37, Sebastiaan Couwenberg wrote:
On 7/22/22 09:02, Antonio Valentino wrote:
Il 21/07/22 09:47, Sebastiaan Couwenberg ha scritto:
Because of the SONAME bump a transition will be required, hence the package should be uploaded to experimental first. Once it passes NEW it won't immediately trigger an uncoordinated transition in unstable. With the package in experimental, and automatic ben tracker will be also generated on release.debian.org, so you won't need to include ben configuration in the transition bugreport (which reportbug still generates for you).

To prepare transitions, you can use the permanent trackers on my ben instance. It shows tiff to be only rdep which makes rebuild testing quite easy:

  https://linuxminded.nl/debian/gis-transitions/html/lerc.html

See also the workflow documented in the transition documentation linked from the tracker:

  https://wiki.debian.org/Teams/ReleaseTeam/Transitions

Thanks a lot for the guidance.
Indeed I have never triggered a transition before.
I still need some time for final checks on the package.
Also, when the package will be in experimental, probably I will need to update the symbol file for architectures different form amd64.

Yes, you'll need to update the symbols for the other architectures once the package in experimental is built at least on all release architectures (ports have more limited buildd capacity for experimental).

pkgkde-symbolshelper makes this quite easy:

  # Download buildlogs
  pkgkde-getbuildlogs

  # Update symbols file
  pkgkde-symbolshelper batchpatch -v 4.0.0 lerc_experimental_logs/*

  # Remove missing symbols
  sed -i '/^#MISSING: .*/d' debian/*symbols

  # Commit changes
  dch <-i|-a> "Update symbols for other architectures."
  debcommit -a

lerc (4.0.0+ds-1~exp1) is built on all release architectures, you can update the symbols and file the transition bugreport.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1


_______________________________________________
Pkg-grass-devel mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grass-devel

Reply via email to