Bug#376135: closed by Yves-Alexis Perez [EMAIL PROTECTED] (Re: [Pkg-xfce-devel] Bug#376135: xfce4-systray: uninstallable in sid)
On Fri, Jun 30, 2006 at 03:25:23PM +0100, Simon Huggins wrote: On Fri, Jun 30, 2006 at 04:01:23PM +0200, Bill Allombert wrote: On Fri, Jun 30, 2006 at 06:33:57AM -0700, Debian Bug Tracking System wrote: Why not keep this bug open until the package is actually removed ? At least it let people know about the problem and the fix. If they didn't get the hint from the Conflicts:/Replaces: on xfce4-panel is there really much hope that they'll check bugs.d.o ? ;) I'm not really bothered either way to be honest. I think a better thing would be for the BTS to report ftp.d.o bugs on the package pages as well and will file a bug for that. I wonder if such bug could not be assigned to ftp.debian.org, xfce4-systray. Can I ask why you wanted it installed or how you got into a situation where your apt frontend tried to install it? I did not do that. I looked at the testing propagation stats and saw that xfce4-systray was not moving to testing without apparent reason (no RC bug, no missing binary etc.) so I investigated and filled this report. Now, I am not very experimented with checking testing propagation, but certainly if packages that _must not_ move to testing all carried a RC bug, it would be much easier to spot packages needing hints, and it is always smarter to allow less experimented people to deal with the system. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#376135: closed by Yves-Alexis Perez [EMAIL PROTECTED] (Re: [Pkg-xfce-devel] Bug#376135: xfce4-systray: uninstallable in sid)
On Fri, Jun 30, 2006 at 06:33:57AM -0700, Debian Bug Tracking System wrote: On Fri, 2006-06-30 at 14:44 +0200, Bill Allombert wrote: Package: xfce4-systray Version: 4.2.3-1 Severity: serious Hello Debian Xfce Maintainers, xfce4-systray is uninstallable in sid: xfce4-systray: Depends: libxfce4util-1 (= 4.2.0) xfce4-systray doesnt need to be installed anymore. It has been replaced by xfce4-panel. xfce4-systray will be removed from unstable, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=37 Why not keep this bug open until the package is actually removed ? At least it let people know about the problem and the fix. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#376135: closed by Yves-Alexis Perez [EMAIL PROTECTED] (Re: [Pkg-xfce-devel] Bug#376135: xfce4-systray: uninstallable in sid)
On Fri, Jun 30, 2006 at 04:01:23PM +0200, Bill Allombert wrote: On Fri, Jun 30, 2006 at 06:33:57AM -0700, Debian Bug Tracking System wrote: On Fri, 2006-06-30 at 14:44 +0200, Bill Allombert wrote: Package: xfce4-systray Version: 4.2.3-1 Severity: serious Hello Debian Xfce Maintainers, xfce4-systray is uninstallable in sid: xfce4-systray: Depends: libxfce4util-1 (= 4.2.0) xfce4-systray doesnt need to be installed anymore. It has been replaced by xfce4-panel. xfce4-systray will be removed from unstable, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=37 Why not keep this bug open until the package is actually removed ? At least it let people know about the problem and the fix. If they didn't get the hint from the Conflicts:/Replaces: on xfce4-panel is there really much hope that they'll check bugs.d.o ? ;) I'm not really bothered either way to be honest. I think a better thing would be for the BTS to report ftp.d.o bugs on the package pages as well and will file a bug for that. Can I ask why you wanted it installed or how you got into a situation where your apt frontend tried to install it? Simon. -- UK based domain, email and web hosting ***/ And what have they ever /* http://www.blackcatnetworks.co.uk/ **/ given us in return? The /** [EMAIL PROTECTED] */ aqueduct? /*** Black Cat Networks / / -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
