Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.6
> fixed 228793 3.0+pre3-2
Bug#228793: coldsync: ColdSYnc.pm not included
Bug marked as fixed in version 3.0+pre3-2.
>
End of message, stopping processing here.
Please contact me if yo
myphpmoney_1.3RC3+dfsg-5_i386.changes uploaded successfully to localhost
along with the files:
myphpmoney_1.3RC3+dfsg-5.dsc
myphpmoney_1.3RC3+dfsg-5.diff.gz
myphpmoney_1.3RC3+dfsg-5_all.deb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a s
Accepted:
myphpmoney_1.3RC3+dfsg-5.diff.gz
to pool/main/m/myphpmoney/myphpmoney_1.3RC3+dfsg-5.diff.gz
myphpmoney_1.3RC3+dfsg-5.dsc
to pool/main/m/myphpmoney/myphpmoney_1.3RC3+dfsg-5.dsc
myphpmoney_1.3RC3+dfsg-5_all.deb
to pool/main/m/myphpmoney/myphpmoney_1.3RC3+dfsg-5_all.deb
Override ent
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#434330: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#428980: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#433017: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#428878: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#428878: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#431695: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#414942: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#434265: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#432313: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#428916: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#428917: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#433473: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#312998: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#428138: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#428439: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#428980: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#432699: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#433016: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#433512: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#433994: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#312999: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#433094: fixed in myphpmoney 1.3RC3+dfsg-5
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
Your message dated Sat, 28 Jul 2007 18:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#428296: fixed in myphpmoney 1.3RC3+dfsg-5
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
Package: d4x
Version: 2.5.7.1
Kernel: Linux xeros 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007
i686 GNU/Linux
C-Lib: 2.6-4
Gnome Version: 2.18.3
libgtk: 1.1 & 2.0 both installed
Sorry for the duplicate, but I have a small update and I'm very new to
this whole bug reporting thing, being a recen
Mitchell Cannon <[EMAIL PROTECTED]> wrote:
Hi,
> Sorry for the duplicate, but I have a small update and I'm very new to
> this whole bug reporting thing, being a recent Slackware to Debian
> convert. I removed my ~/.ntrc_2/ configuration directory. Turns out
> that the problem occurs only when
FYI: The status of the wmmemmon source package
in Debian's testing distribution has changed.
Previous version: 1.0.1-3
Current version: 1.0.1-4
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more information.
-
FYI: The status of the libquota-perl source package
in Debian's testing distribution has changed.
Previous version: 1.4.9-2
Current version: 1.4.9-3
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more information
I don't know exactly how it happened, but a large number of maintainers
apparently ignored the discussions on this list and added to their
packages a dependency on update-inetd.
This is *TOTALLY WRONG* because the /usr/sbin/update-inetd interface is
guaranteed to be provided by whatever implements
FYI: The status of the giftui source package
in Debian's testing distribution has changed.
Previous version: 0.4.1-8
Current version: 0.4.1-9
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more information.
--
FYI: The status of the wmmemload source package
in Debian's testing distribution has changed.
Previous version: 0.1.6-2
Current version: 0.1.6-3
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more information.
33 matches
Mail list logo
