Your message dated Sun, 12 Mar 2006 17:35:45 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#350221: fixed has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: ftp.debian.org Severity: normal On Sun, May 30, 2004 at 06:40:32PM +0200, Ove Kaaven wrote: > søn, 30.05.2004 kl. 13.37 skrev Guus Sliepen: > > I am planning to upload libgmime2 with just the Maintainer: field > > changed, and a new libgmime2.1 package. However, there are also packages > > in unstable for libgmime0 and libgmime1. As far as apt-cache rdepends > > can tell me, there are no Debian packages depending on them, so I'm > > inclined to send an email to ftp-master to have them removed. However, > > if you know that there still are people using those Debian packages, > > I'll continue maintaining them. > > I have no idea. Like you, anyone using this library is apparently doing > it for their own projects, not for Debian. But if you want my opinion, > you can almost certainly remove libgmime0. However, I wouldn't want to > remove libgmime1 yet - at least not before sarge is released (with it), > in any case, and maybe not even before people start thinking about > removing libglib1.2 itself from Debian. It's difficult to be sure > without user feedback, for sure. Maybe not even http//popcon.debian.org/ > (seems to down at the moment) would help much here... ftp-master: please remove libgmime0 and libgmime0-dev from unstable. Ove: there is an FTBFS bug filed against gmime1 (#306610). If you don't want to maintain this package anymore, please ask the ftp-masters to remove gmime1 as well. -- Met vriendelijke groet / with kind regards, Guus Sliepen <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: gmime1 | 1.0.8-1 | source libgmime1 | 1.0.8-1 | alpha, arm, hppa, hurd-i386, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc libgmime1-dev | 1.0.8-1 | alpha, arm, hppa, hurd-i386, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive (ftp-master.debian.org) and will not propagate to any mirrors (ftp.debian.org included) until the next cron.daily run at the earliest. Packages are never removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED] This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED] Debian distribution maintenance software pp. Jeroen van Wolffelaar (the ftpmaster behind the curtain)
--- End Message ---
