citizenaspirant
/
PyBitmessage
1
0
Fork 0
Code Issues 1 Pull Requests Releases Wiki Activity

Remove invalid characters from debian/changelog

This commit is contained in:
fuzzgun 2013-06-03 20:22:02 +01:00
parent eb2d16c574
commit b296d9d39f
2 changed files with 48 additions and 48 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Makefile
View File

@ -1,5 +1,5 @@
APP=pybitmessage APP=pybitmessage
VERSION=0.3.211 VERSION=0.3.2
DEST_SHARE=$(DESTDIR)/usr/share DEST_SHARE=$(DESTDIR)/usr/share
DEST_APP=$(DEST_SHARE)/$(APP) DEST_APP=$(DEST_SHARE)/$(APP)

12
debian/changelog vendored
View File

@ -4,8 +4,8 @@ pybitmessage (0.3.2-1) raring; urgency=low
* Refactored message status-related code. API function getStatus * Refactored message status-related code. API function getStatus
now returns one of these strings: notfound, msgqueued, now returns one of these strings: notfound, msgqueued,
broadcastqueued, broadcastsent, doingpubkeypow, awaitingpubkey, broadcastqueued, broadcastsent, doingpubkeypow, awaitingpubkey,
doingmsgpow, msgsent, or ackreceived doingmsgpow, msgsent, or ackreceived
* Moved proof of work to low-priority multi-threaded child * Moved proof of work to low-priority multi-threaded child
processes processes
@ -19,7 +19,7 @@ pybitmessage (0.3.2-1) raring; urgency=low
* Store tray icons in bitmessage_icons_rc.py * Store tray icons in bitmessage_icons_rc.py
-- Jonathan Warren (4096 bits) <jonathan@bitmessage.org> Mon, 03 June 2013 12:06:00 +0100 -- Bob Mottram (4096 bits) <bob@robotics.uk.to> Mon, 03 June 2013 20:17:00 +0100
pybitmessage (0.3.1-1) raring; urgency=low pybitmessage (0.3.1-1) raring; urgency=low
@ -31,12 +31,12 @@ pybitmessage (0.3.1-1) raring; urgency=low
* Don't update the time we last communicated with a node unless * Don't update the time we last communicated with a node unless
the connection is fully established. This will allow us to the connection is fully established. This will allow us to
forget about active but non-Bitmessage nodes which have made forget about active but non-Bitmessage nodes which have made
it into our knownNodes file. it into our knownNodes file.
* Prevent incoming connection flooding from crashing * Prevent incoming connection flooding from crashing
singleListener thread. Client will now only accept one singleListener thread. Client will now only accept one
connection per remote node IP connection per remote node IP
* Bugfix: Worker thread crashed when doing a POW to send out * Bugfix: Worker thread crashed when doing a POW to send out
a v2 pubkey (bug introduced in 0.3.0) a v2 pubkey (bug introduced in 0.3.0)