Am 18.01.2019 um 10:20 schrieb Emilio Pozuelo Monfort: > On 18/01/2019 09:33, Patrick Matthäi wrote: >> Package: release.debian.org >> Severity: normal >> User: release.debian....@packages.debian.org >> Usertags: transition >> >> Hello, >> >> glusterfs 5.2-2 has been accepted in experimental. >> For closing #918503 and #881526, which makes life of other maintainers easier >> and smaller dependencies on standard systems I would like to upload it to sid >> along with the new bugfix release 5.3 and have the changes in buster. >> There is no soname change, but now the libraries are seperated in single >> packages and I also provide libglusterfs-dev again. >> >> The reverse dependencies just have to switch their build dependency from >> glusterfs-common to libglusterfs-dev: > Can't you make glusterfs-common depend on libglusterfs-dev (until the buster > release) so that rdeps don't fail to build if you upload this? Then they can > update their build-dep asynchronously. > > Just considering this because there's no real transition per se, particularly > if > you address that concern. > > Cheers, > Emili
So you mean: * 5.3-1: upload to sid with glusterfs-common depending on libglusterfs-dev * Let 5.3-1 migrate to buster and filling bugs against rdeps to change their deps * If all bugs are closed make a new upload removing the -commong -> -dev dep If you mean this I would start with it -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */