[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#803336: marked as done (RM: mopidy/1.1.1-1)



Your message dated Fri, 30 Oct 2015 23:16:33 +0100
with message-id <5633EC41.50400@debian.org>
and subject line Re: Bug#803336: RM: mopidy/1.1.1-1
has caused the Debian Bug report #803336,
regarding RM: mopidy/1.1.1-1
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.)


-- 
803336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803336
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: rm

Hi,
please remove mopidy as part of the gstreamer 0.10
removal. According to the PTS this should have been
auto-removed, but some reason that didn't happen:

Marked for autoremoval on 16 October:
* The removal of mopidy will also cause the removal of
  (transitive) reverse dependencies: mopidy-alsamixer
  mopidy-beets mopidy-dirble mopidy-local-sqlite mopidy-mpris
  mopidy-scrobbler mopidy-tunein mopidy-youtube

Cheers,
        Moritz

--- End Message ---
--- Begin Message ---
On 30/10/15 19:07, Moritz Mühlenhoff wrote:
> On Thu, Oct 29, 2015 at 08:48:27AM +0000, Julien Cristau wrote:
>> On Wed, Oct 28, 2015 at 23:06:07 +0100, Moritz Muehlenhoff wrote:
>>
>>> Package: release.debian.org
>>> Severity: normal
>>> User: release.debian.org@packages.debian.org
>>> Usertags: rm
>>>
>>> Hi,
>>> please remove mopidy as part of the gstreamer 0.10
>>> removal. According to the PTS this should have been
>>> auto-removed, but some reason that didn't happen:
>>>
>>> Marked for autoremoval on 16 October:
>>> * The removal of mopidy will also cause the removal of
>>>   (transitive) reverse dependencies: mopidy-alsamixer
>>>   mopidy-beets mopidy-dirble mopidy-local-sqlite mopidy-mpris
>>>   mopidy-scrobbler mopidy-tunein mopidy-youtube
>>>
>> britney says:
>>
>>     * amd64: mopidy-alsamixer, mopidy-beets, mopidy-dirble, mopidy-local-sqlite, mopidy-mpris, mopidy-scrobbler, mopidy-tunein, mopidy-youtube
>>
>> Those rdeps aren't marked for removal yet:
> 
> Oh, I thought these were removed along rightaway automatically.
> 
> Can we do that manually instead? mopidy is the last blocker for the
> removal of further gst0.10-plugins and the 0.10 python bindings from
> testing:
> 
> remove mopidy-alsamixer/1.0.3-3 mopidy-beets/2.0.0-2 mopidy-dirble/1.1.2-2 mopidy-local-sqlite/1.0.0-1 mopidy-mpris/1.3.1-1 mopidy-scrobbler/1.1.1-3 mopidy-tunein/0.2.2-2 mopidy-youtube/2.0.0-2
> remove mopidy/1.1.1-1

You forgot mopidy-podcast-*. A few have been removed in this run, the rest
(together with gst-python and -good) will go out tomorrow.

I have also removed xfce4-mixer, FWIW.

Cheers,
Emilio

--- End Message ---

Reply to: