[PEAR-BUG] Bug #7947 [Fbk->Csd]: Bugtracker asks for password that doesn't exist

Discussion:

(too old to reply)

c***@php.net

2006-12-23 04:09:29 UTC

Edit report at http://pear.php.net/bugs/bug.php?id=7947&edit=1

ID: 7947
Updated by: ***@php.net
Reported By: wiesemann at php dot net
-Status: Feedback
+Status: Closed
Id: 7947
Type: Bug
Package: Bug System
Operating System: Irrelevant
PHP Version: Irrelevant
Assigned To: pajoye
New Comment:

apparently this is fixed

Previous Comments:
------------------------------------------------------------------------

[2006-06-20 13:44:51] wiesemann at php dot net

The question is if it is a good thing to put the developer
link in the user (which is the only) mail, or make
it a private mail.

There are two cases:

(1) If the reports is answered:

ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at
http://pear.php.net/bugs/bug.php?id=7947&edit=2

(2) The email after I wrote the report:

Edit bug report at http://pear.php.net/bugs/bug.php?id=7947&edit=2

If we have the possibility to differ between the cases whether a
developer reported the bug or somebody else, we should modify the links
accordingly. That would make life a little bit easier. ;-)

------------------------------------------------------------------------

[2006-06-20 13:34:45] pajoye at php dot net

Using different links in these two cases should be
sufficient, no need to definie separate email templates.

Yes, because you are normally not supposed to use the
second edit mode, it is only for users.

Okay, but for additional comments from myself (or the reply to your
question, which is in a different email "template" in the script), the
link is "wrong".

Using different links in these two cases should be sufficient, no need
to definie separate email templates.

------------------------------------------------------------------------

[2006-06-20 13:25:11] pajoye at php dot net

Yes, because you are normally not supposed to use the second edit mode,
it is only for users.

Not sure if it is a good thing to add the developer link to the mail
and/or to send a separate mail to the developers.

Any comment?

------------------------------------------------------------------------

[2006-06-20 13:19:26] wiesemann at php dot net

Small correction: This is true for all packages, not only for bug
system bugs.

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://pear.php.net/bugs/bug.php?id=7947

--
Edit this bug report at http://pear.php.net/bugs/bug.php?id=7947&edit=1

w***@php.net

2006-12-23 10:54:27 UTC

Permalink

Edit report at http://pear.php.net/bugs/bug.php?id=7947&edit=1

ID: 7947
Updated by: ***@php.net
Reported By: wiesemann at php dot net
-Status: Closed
+Status: Open
Type: Bug
Package: Bug System
Operating System: Irrelevant
PHP Version: Irrelevant
Assigned To: pajoye

Post by c***@php.net
apparently this is fixed

No, it is not. Mark it as "Won't fix" (because of the huge changes that
would be needed) if you want, but "Closed" is definitely wrong here, as
there was only a discussion, but no code change.

Previous Comments:
------------------------------------------------------------------------

[2006-12-22 23:09:29] cellog at php dot net

apparently this is fixed

------------------------------------------------------------------------

[2006-06-20 13:44:51] wiesemann at php dot net

Post by c***@php.net
The question is if it is a good thing to put the developer
link in the user (which is the only) mail, or make
it a private mail.

Post by c***@php.net
Using different links in these two cases should be
sufficient, no need to definie separate email templates.

Post by c***@php.net
Yes, because you are normally not supposed to use the
second edit mode, it is only for users.

Okay, but for additional comments from myself (or the reply to your
question, which is in a different email "template" in the script), the
link is "wrong".

Using different links in these two cases should be sufficient, no need
to definie separate email templates.

------------------------------------------------------------------------

[2006-06-20 13:25:11] pajoye at php dot net

Yes, because you are normally not supposed to use the second edit mode,
it is only for users.

Not sure if it is a good thing to add the developer link to the mail
and/or to send a separate mail to the developers.

Any comment?

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://pear.php.net/bugs/bug.php?id=7947

--
Edit this bug report at http://pear.php.net/bugs/bug.php?id=7947&edit=1

c***@php.net

2006-12-23 19:40:50 UTC

Permalink

Edit report at http://pear.php.net/bugs/bug.php?id=7947&edit=1

ID: 7947
Updated by: ***@php.net
Reported By: wiesemann at php dot net
-Status: Open
+Status: Closed
Type: Bug
Package: Bug System
Operating System: Irrelevant
PHP Version: Irrelevant
-Assigned To:
+Assigned To: cellog
New Comment:

I present to you evidence that this is working. Here is an email I
just received yesterday. Note that "edit=1" at the bottom

Edit report at http://pear.php.net/bugs/bug.php?id=9205&edit=1

ID: 9205
Updated by: ***@php.net
Reported By: wiesemann at php dot net
-Status: Open
+Status: Closed
Id: 9205
Type: Bug
-Package: Web Site
+Package: pearweb
Operating System: Irrelevant
PHP Version: Irrelevant
-Assigned To:
+Assigned To: cellog
New Comment:

This bug has been fixed in CVS.

If this was a documentation problem, the fix will appear on
pear.php.net by the end of next Sunday (CET).

If this was a problem with the pear.php.net website, the change should
be live shortly.

Otherwise, the fix will appear in the package's next release.

Thank you for the report and for helping us make PEAR better.

Previous Comments:
------------------------------------------------------------------------

[2006-10-31 16:34:52] wiesemann at php dot net

Description:
------------
The "quick fix" text for "fixed in release" generates for the "Web
Site" package this URL:
http://pear.php.net/get/Web Site

It should at least escape the space, but maybe also other characters.
(=> urlencode()?)

------------------------------------------------------------------------

-- Edit this bug report at
http://pear.php.net/bugs/bug.php?id=9205&edit=1

Previous Comments:
------------------------------------------------------------------------

[2006-12-23 05:54:26] wiesemann at php dot net

Post by c***@php.net
apparently this is fixed

No, it is not. Mark it as "Won't fix" (because of the huge changes that
would be needed) if you want, but "Closed" is definitely wrong here, as
there was only a discussion, but no code change.

------------------------------------------------------------------------

[2006-12-22 23:09:29] cellog at php dot net

apparently this is fixed

------------------------------------------------------------------------

[2006-06-20 13:44:51] wiesemann at php dot net

Post by c***@php.net
The question is if it is a good thing to put the developer
link in the user (which is the only) mail, or make
it a private mail.

Post by c***@php.net
Using different links in these two cases should be
sufficient, no need to definie separate email templates.

Post by c***@php.net
Yes, because you are normally not supposed to use the
second edit mode, it is only for users.

--
Edit this bug report at http://pear.php.net/bugs/bug.php?id=7947&edit=1

w***@php.net

2006-12-24 10:00:53 UTC

Permalink

Post by c***@php.net
ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at
http://pear.php.net/bugs/bug.php?id=7947&edit=2

(note the "edit=2" which is still wrong)

Previous Comments:
------------------------------------------------------------------------

[2006-12-23 14:40:50] cellog at php dot net

I present to you evidence that this is working. Here is an email I
just received yesterday. Note that "edit=1" at the bottom

Edit report at http://pear.php.net/bugs/bug.php?id=9205&edit=1

ID: 9205
Updated by: ***@php.net
Reported By: wiesemann at php dot net
-Status: Open
+Status: Closed
Id: 9205
Type: Bug
-Package: Web Site
+Package: pearweb
Operating System: Irrelevant
PHP Version: Irrelevant
-Assigned To:
+Assigned To: cellog
New Comment:

This bug has been fixed in CVS.

If this was a documentation problem, the fix will appear on
pear.php.net by the end of next Sunday (CET).

If this was a problem with the pear.php.net website, the change should
be live shortly.

Otherwise, the fix will appear in the package's next release.

Thank you for the report and for helping us make PEAR better.

Previous Comments:
------------------------------------------------------------------------

[2006-10-31 16:34:52] wiesemann at php dot net

Description:
------------
The "quick fix" text for "fixed in release" generates for the "Web
Site" package this URL:
http://pear.php.net/get/Web Site

It should at least escape the space, but maybe also other characters.
(=> urlencode()?)

------------------------------------------------------------------------

-- Edit this bug report at
http://pear.php.net/bugs/bug.php?id=9205&edit=1

------------------------------------------------------------------------

[2006-12-23 05:54:26] wiesemann at php dot net

Post by c***@php.net
apparently this is fixed

No, it is not. Mark it as "Won't fix" (because of the huge changes that
would be needed) if you want, but "Closed" is definitely wrong here, as
there was only a discussion, but no code change.

------------------------------------------------------------------------

[2006-12-22 23:09:29] cellog at php dot net

apparently this is fixed

------------------------------------------------------------------------

[2006-06-20 13:44:51] wiesemann at php dot net

Post by c***@php.net
The question is if it is a good thing to put the developer
link in the user (which is the only) mail, or make
it a private mail.

Post by c***@php.net
Using different links in these two cases should be
sufficient, no need to definie separate email templates.

The question is if it is a good thing to put the developer link in the
user (which is the only) mail, or make it a private mail.

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://pear.php.net/bugs/bug.php?id=7947

--
Edit this bug report at http://pear.php.net/bugs/bug.php?id=7947&edit=1

c***@php.net

2006-12-24 18:43:50 UTC

Permalink

Edit report at http://pear.php.net/bugs/bug.php?id=7947&edit=1

ID: 7947
Updated by: ***@php.net
Reported By: wiesemann at php dot net
Status: Closed
Type: Bug
Package: Bug System
Operating System: Irrelevant
PHP Version: Irrelevant
Assigned To: cellog
New Comment:

ok, now you're starting to make sense - I didn't realize it was for
bugs you had reported. I have fixed this in CVS, and it will appear in
the next release of pearweb

Previous Comments:
------------------------------------------------------------------------

[2006-12-24 05:00:52] wiesemann at php dot net

Keep it closed if you want, but the information mail that I've got

Post by c***@php.net
ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at
http://pear.php.net/bugs/bug.php?id=7947&edit=2

(note the "edit=2" which is still wrong)

------------------------------------------------------------------------

[2006-12-23 14:40:50] cellog at php dot net

I present to you evidence that this is working. Here is an email I
just received yesterday. Note that "edit=1" at the bottom

Edit report at http://pear.php.net/bugs/bug.php?id=9205&edit=1

ID: 9205
Updated by: ***@php.net
Reported By: wiesemann at php dot net
-Status: Open
+Status: Closed
Id: 9205
Type: Bug
-Package: Web Site
+Package: pearweb
Operating System: Irrelevant
PHP Version: Irrelevant
-Assigned To:
+Assigned To: cellog
New Comment:

This bug has been fixed in CVS.

If this was a documentation problem, the fix will appear on
pear.php.net by the end of next Sunday (CET).

If this was a problem with the pear.php.net website, the change should
be live shortly.

Otherwise, the fix will appear in the package's next release.

Thank you for the report and for helping us make PEAR better.

Previous Comments:
------------------------------------------------------------------------

[2006-10-31 16:34:52] wiesemann at php dot net

Description:
------------
The "quick fix" text for "fixed in release" generates for the "Web
Site" package this URL:
http://pear.php.net/get/Web Site

It should at least escape the space, but maybe also other characters.
(=> urlencode()?)

------------------------------------------------------------------------

-- Edit this bug report at
http://pear.php.net/bugs/bug.php?id=9205&edit=1

------------------------------------------------------------------------

[2006-12-23 05:54:26] wiesemann at php dot net

Post by c***@php.net
apparently this is fixed

No, it is not. Mark it as "Won't fix" (because of the huge changes that
would be needed) if you want, but "Closed" is definitely wrong here, as
there was only a discussion, but no code change.

------------------------------------------------------------------------

[2006-12-22 23:09:29] cellog at php dot net

apparently this is fixed

------------------------------------------------------------------------

[2006-06-20 13:44:51] wiesemann at php dot net

Post by c***@php.net
The question is if it is a good thing to put the developer
link in the user (which is the only) mail, or make
it a private mail.

--
Edit this bug report at http://pear.php.net/bugs/bug.php?id=7947&edit=1