Bug#919643: marked as done (transition: glusterfs)
Your message dated Fri, 18 Jan 2019 11:41:38 +0100
with message-id <0b74f01b-0d24-1abc-f0ed-26451ca16009@debian.org>
and subject line Re: Bug#919643: transition: glusterfs
has caused the Debian Bug report #919643,
regarding transition: glusterfs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
919643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919643
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@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:
uwsgi-plugin-glusterfs
samba-vfs-modules
qemu-block-extra
nfs-ganesha-gluster
libvirt-daemon-driver-storage-gluster
fio
gfio
Could I go ahead?
-- System Information:
Debian Release: 9.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On 18/01/2019 10:26, Patrick Matthäi wrote:
> 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.org@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
Yes, something like that. The bugs would not be RC until bullseye, so for now
severity:normal or so.
Also closing this as there's nothing for us to track here. But feel free to
follow up if you have any questions.
Cheers,
Emilio
--- End Message ---
Reply to: