Age | Commit message (Collapse) | Author | Files | Lines |
|
Fix PR pkg/48777
|
|
|
|
|
|
|
|
NetBSD 6, requested by tron.
|
|
Recursively bump package revisions again after the "freetype2" and
"fontconfig" handling was fixed.
|
|
to address issues with NetBSD-6(and earlier)'s fontconfig not being
new enough for pango.
While doing that, also bump freetype2 dependency to current pkgsrc
version.
Suggested by tron in PR 47882
|
|
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
are called p5-*.
I hope that's all of them.
|
|
|
|
requested by Thomas Klausner.
|
|
(additionaly, reset PKGREVISION of qt4-* sub packages from base qt4 update)
|
|
|
|
24 Aug 2012:
- Release 4.0.0
21 Jun 2012:
- Fixed an issue that happened when enabling the OTR plugin while a
conversation is open.
- Release 4.0.0-beta2
7 Jun 2012:
- The plugin now supports multiple OTR conversations with the same
buddy who is logged in at multiple locations. In this case, a new
OTR menu will appear, which allows you to select which session an
outgoing message is indended for. Note that concurrent SMP
authentications with the same buddy who is logged in multiple times
is not yet supported (starting a second authentication will end the
first).
- During a private conversation with a buddy, an incoming unencrypted
message will now trigger the regular incoming message notifications.
In Pidgin this includes showing the message in the top-right
notification area, if it is normally configured to do so.
- New Italian, Swedish, Polish and Vietnamese translations. Updates to
the French translation.
- When a private conversation begins, the plugin will indicate whether
Pidgin is configured to log the conversation.
- By default, OTR conversations will not be logged by Pidgin.
- Fingerprints in the manual authentication dialog are now selectable
- The plugin will no longer delete the OTR menus if a non-foreground
conversation window is closed.
- Except on WIN32, the plugin will now set the umask to 0077 before
creating the otr.* files in the purple directory so that they end up
mode 0600.
- The menu item now says "Reauthenticate buddy" when the buddy is
already authenticated.
- Release 4.0.0-beta1
|
|
|
|
2012-05-14
* INSTALL: Fixing typo and updating reference to CVS.
* Makefile.mingw, packaging/windows/pidgin-otr.nsi:
Updating to support building the win32 installer on
GNU/Linux.
2012-05-12
* otr-plugin.c: Fixing a format string vulnerability.
Identified by intrigeri <intrigeri@boum.org>.
* Makefile.mingw, README, configure.ac, pidgin-otr.nsi:
Bumped version number to 3.2.1.
2010-03-02
* po/vi.po: Vietnamese translation from Lyndon Johnson
<lyndon.johnson58@gmail.com>
2009-11-14
* gtk-dialog.c (add_to_vbox_verify_fingerprint): Make
the fingerprints in the manual authentication dialog
selectable (but not selected by default).
2009-08-24
* po/fr.po: Fixed \n errors
2009-07-20
* po/fr.po: Complete French translation from Solveig
<perso@solveig.org>
2009-06-24
* po/fr.po: Spelling correction from intrigeri
<intrigeri@boum.org>
2009-03-18
* po/sv.po: Swedish translation from Daniel Nylander
<po@danielnylander.se>
2009-01-18
* po/pl.po: Polish translation from Paweł Czochański
<czochanski@gmail.com>
2008-09-24
* po/it.po: Italian translation from Vincenzo Reale
<smart2128@baslug.org>.
2008-07-10
* otr-plugin.c: Use /dev/urandom to generate keys instead of
/dev/random. [Really: on non-Win32, call
gcry_control(GCRYCTL_ENABLE_QUICK_RANDOM, 0); before OTRL_INIT;.]
2008-07-07
* gtk-conv.c: Don't delete the OTR menus if a non-foreground
conversation window is closed.
2008-06-19
* Makefile.static: Forgot to add tooltipmenu.o to
Makefile.static. Fixed.
2008-06-17
* otr-plugin.c: Except on WIN32, set the umask to 0077 before
creating the otr.* files in the purple directory so that they
end up mode 0600. Based on a patch from Caspar Clemens Mierau
<damokles@ubuntu.com>.
* po/de.po: Updated German translation from Michael Meier
<mail@code.mmsources.de>.
|
|
|
|
py-* not affected, since it built different versions depending on the
setting already.
|
|
|
|
|
|
a) tiff update to 4.0 (shlib major change)
b) glib2 update 2.30.2 (adds libffi dependency to buildlink3.mk)
Enjoy.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
version, and bump all depends.
Per discussion on pkgsrc-changes.
|
|
Also add some patches to remove use of deprecated symbols and fix other
problems when looking for or compiling against libpng-1.4.x.
|
|
|
|
|
|
|
|
Add BUILDLINK_API_DEPENDS.libotr due to:
configure: error: libotr 3.2.0 or newer is required.
The real problem was undefined reference to gcry_cipher_setkey
and gcry_cipher_setctr. Looked at various versions on different
architectures and it appears even though the headers were there,
they weren't defined in the library until libgcrypt-1.4.3 --
so define BUILDLINK_ABI_DEPENDS.libgcrypt.
Bump PKGREVISION.
|
|
Bump PKGREVISION of non-bundled plug-ins.
Changes for 2.5.0 (08/17/2008) since 2.4.3:
libpurple + pidgin:
- Lots of bug fixes and improvements for the MSN protocol
(MSNP15 support) and MSN "bunny icon" (?).
- Miscellaneous bug fixes, a few new icons, etc.
- The following API changes:
libpurple:
Added:
* Connection flag PURPLE_CONNECTION_ALLOW_CUSTOM_SMILEY to indicate
that the connection supports sending and receiving custom smileys.
* PurpleSmiley and the Smiley API.
* purple_serv_got_join_chat_failed
* chat-join-failed signal (see conversation-signals.dox)
* chat-invite-blocked and blocked-im-msg signals (see
converation-signals.dox) (Thanks to Stefan Ott)
* purple_blist_update_node_icon
* purple_buddy_icons_node_has_custom_icon
* purple_buddy_icons_node_find_custom_icon
* purple_buddy_icons_node_set_custom_icon
* purple_buddy_icons_node_set_custom_icon_from_file
* purple_notify_user_info_prepend_section_break
* purple_notify_user_info_prepend_section_header
* "website" and "dev_website" items to the ui_info hash table
* purple_cmds_get_handle, purple_cmds_init, purple_cmds_uninit
* cmd-added and cmd-removed signals
* purple_get_host_name
* purple_util_fetch_url_len (temporary function overload to add max_len
param)
* purple_util_fetch_url_request_len
* purple_prpl_send_attention
* purple_prpl_got_attention
* purple_prpl_got_attention_in_chat
Deprecated:
* purple_blist_update_buddy_icon
* purple_buddy_icons_has_custom_icon
* purple_buddy_icons_find_custom_icon
* purple_buddy_icons_set_custom_icon
* pidgin_set_custom_buddy_icon
* purple_util_fetch_url_len
* purple_util_fetch_url_request_len
* serv_send_attention
* serv_got_attention
Changed:
* xmlnode_copy now copies the prefix and namespace map for nodes.
pidgin:
Added:
* gtk_imhtml_smiley_create, gtk_imhtml_smiley_reload and
gtk_imhtml_smiley_destroy to deal with GtkIMHtmlSmiley's.
* pidgin_pixbuf_from_imgstore to create a GdkPixbuf from a
PurpleStoredImage.
* pidgin_themes_smiley_themeize_custom to associate custom smileys to
a GtkIMHtml widget.
* GTK_IMHTML_CUSTOM_SMILEY flag for GtkIMHtml.
* GTK+ Custom Smiley API.
|
|
28 May 2008:
- The functionality of the OTR button has now moved to a menu. There's
an "OTR" menu, as well as an icon showing the current OTR state of
each active conversation in the window.
- New OTR icons from <cyrus_xiii@yahoo.com>
- OTR icons show up inline in the conversation window when the OTR
status changes.
- Buddy authentication has been revamped, based on the user study
published in SOUPS 2008. The default is now to choose a question and
an answer only you and the buddy should know. The question is
displayed to the buddy, who is prompted for the answer. The "shared
secret" and "fingerprint" authentication methods are still available.
|
|
|
|
|
|
Bump PKGREVISION.
|
|
|
|
|
|
This is the OTR plugin for Pidgin.
Off-the-Record (OTR) Messaging allows you to have private
conversations over instant messaging by providing:
Encryption
No one else can read your instant messages.
Authentication
You are assured the correspondent is who you think it is.
Deniability
The messages you send do not have digital signatures that are
checkable by a third party. Anyone can forge messages after a
conversation to make them look like they came from you. However,
during a conversation, your correspondent is assured the messages
he sees are authentic and unmodified.
Perfect forward secrecy
If you lose control of your private keys, no previous conversation
is compromised.
|