Your message dated Tue, 29 Nov 2005 07:51:18 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#306098: fixed in pppoeconf 1.7
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
Processing commands for [EMAIL PROTECTED]:
> retitle 334361 pppoeconf: shouldn't mess with "auto" stanzas
Bug#334361: bug pppoeconf
Changed Bug title.
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, D
Processing commands for [EMAIL PROTECTED]:
> tags 337425 - wontfix
Bug#337425: zope-zpatterns: Uninstallabe due to zope transition
Tags were: wontfix
Tags removed: wontfix
> block 337425 by 312864
Bug#337425: zope-zpatterns: Uninstallabe due to zope transition
Was not blocked by any bugs.
Blockin
Processing commands for [EMAIL PROTECTED]:
> reassign 173662 zope-cmfcalendar1.4
Bug#173662: zope-cmfcalendar: allow more granular event control
Bug reassigned from package `zope-cmfcalendar' to `zope-cmfcalendar1.4'.
> reassign 180813 zope-cmf1.4
Bug#180813: zope-cmf: CMF Sites exported from non
reassign 173662 zope-cmfcalendar1.4
reassign 180813 zope-cmf1.4
reassign 183028 zope-cmfcalendar1.4
thanks
Please check whether these bugs are still relevant for zope-cmf1.4 and
zope-cmf1.5. (If not, they can be closed.)
Thanks!
Matej
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subj
Your message dated Tue, 29 Nov 2005 06:50:12 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:50:12 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:50:12 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:50:12 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:50:12 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:50:12 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Processing commands for [EMAIL PROTECTED]:
> clone 229059 -1 -2
Bug#229059: zope-cmf: typo in package description
Bug 229059 cloned as bugs 341193-341194.
> reassign -1 zope-cmf1.4
Bug#341193: zope-cmf: typo in package description
Bug reassigned from package `zope-cmf' to `zope-cmf1.4'.
> reassi
Your message dated Tue, 29 Nov 2005 06:15:04 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:15:04 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:15:04 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:13:43 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:13:43 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:13:43 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:13:43 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:06:56 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:06:56 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:05:35 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:04:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:04:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:06:56 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:08:50 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:04:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:04:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:08:50 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:04:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:04:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 06:04:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:41:59 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:43:40 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:57:29 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:59:20 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:51:15 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:59:20 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:57:29 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:55:24 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:53:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:41:59 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:57:29 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:55:24 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:55:24 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:51:15 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:57:29 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:53:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:53:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:48:55 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:48:55 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:48:55 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 29 Nov 2005 05:47:18 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
zopectl |0.3.4.4 | source, all
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) w
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
zope-mysqlda |2.0.8-3 | source, all
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)
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
xlander | 19920427-4 | hurd-i386
xlander | 19920427-5 | source, alpha, arm, hppa, i386, ia64, m68k, mips,
mipsel, powerpc, s390, sparc
Note that the package(s) have simply been remo
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
zope-emarket | 0.2.0a4-13 | source, all
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)
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
zope-cmf |1.3.3-2 | source, all
zope-cmfcalendar |1.3.3-2 | all
zope-cmfcore |1.3.3-2 | all
zope-cmfdefault |1.3.3-2 | all
zope-cmftopic |1.3.3-2 | all
Note that the
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
zope-znavigator |2.02-10 | source, all
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
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
zope-ldap |1.1.0-4 | source, all
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) w
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
zope-xmlmethods |1.0.0-2 | source, all
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
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
zope-parsedxml |1.3.1-6 | source, all
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(
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
zope-ldapuserfolder | 2.2-3 | source, all
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 pac
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
zope-cmfworkflow |0.4.2-5 | source, all
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 packag
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
zope-lockablefolder |0.1.0-6 | source, all
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 pac
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
zope-cmfpgforum | 1.0.0b-3 | source, all
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
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
zope-dtmlcalendar | 1.0.15-6 | source, all
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 packa
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
zope-kinterbasdbda | 1.0-4 | source, all
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 pack
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
zope-cmfldap | 2.0-2 | source, all
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)
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
zope-callprofiler | 1.4-4 | source, all
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 packa
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
libmacrosystem-dev | 0.51-7 | alpha, arm, hppa, hurd-i386, i386, ia64,
m68k, mips, mipsel, powerpc, s390, sparc
libmacrosystem0 | 0.51-7 | alpha, arm, hppa, hurd-i386, i386, ia64,
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
libregexx-dev | 0.98.1-11 | alpha, arm, hppa, hurd-i386, i386, ia64, m68k,
mips, mipsel, powerpc, s390, sparc
libregexx1 | 0.98.1-11 | alpha, arm, hppa, hurd-i386, i386, ia64, m68k, mips
FYI: The status of the libxml-ruby source package
in Debian's testing distribution has changed.
Previous version: 0.3.4-3
Current version: 0.3.4-4
--
This email is automatically generated.
See http://people.debian.org/~henning/trille/ for more information.
--
To UNSUBSCRIBE, email to [EM
tags 250428 wontfix
stop
Hello Toni,
> while trying to import squidguard into an archive for tla-buildpackage,
> I find this file which makes tla-importdsc barf:
>
> samples/.sample.conf.swp
This file is part of the upstream tarball, but is not shipped in the
binary package. I don't think it's
74 matches
Mail list logo
