On Sunday 13 November 2005 04:18 pm, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > #334933: python2.4-cherrypy: New upstream release, > which was filed against the python2.4-cherrypy package.
I am confused, the wishlist item is for CherryPy-2.1.0, the patch submitted is for python-cherrypy-2.1.0 as well. But the close message for this wishitem is for 2.0.0f-2, did you back-port all the changes from 2.1 into 2.0.0f-2? Doesn't that make things confusing on tracking upstream? If I have a package that depends on cherrypy-2.1 functionality so I now need to go back and change it to 2.0.0f-2? -- Bob Tanner <[EMAIL PROTECTED]> | Phone : (952)943-8700 http://www.real-time.com, Minnesota, Linux | Fax : (952)943-8500 Key fingerprint = AB15 0BDF BCDE 4369 5B42 1973 7CF1 A709 2CC1 B288 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
