This is achieved by having multiple lines per storage file, one for each user (if the feature is enabled); each of these
lines has the same format as would be the case for the userless authentication, except that they are prepended with a
SHA-512 of the user's id.
This closes#1623, and updates _all_ channels to the corresponding
latest upstream versions.
Thanks to @wizeman for opening the pull request noted above and for
another update in between, @aristidb for fixing the patcheShebangs issue
and @shlevy for notifying me about the build failure in stdenv-updates
in the first place.
Sorry to everyone for my inactivity lately.
The following changes were needed in order to build those new releases:
* Patch out /bin/echo to allow building with all options enabled.
* Always use GN from the source tree.
* Remove import of depot_tools for version 34.
* Drop version 32 specific stuff.
With this commit, the following new upstream versions are introduced:
stable: 32.0.1700.77 -> 32.0.1700.102 (builds fine, tested)
beta: 32.0.1700.19 -> 33.0.1750.46 (builds fine, tested)
dev: 33.0.1712.4 -> 34.0.1809.0 (build broken with gnome_keyring)
The dev version requires a more recent version gnome_keyring and thus
won't build if gnomeKeyringSupport is set to true. I haven't tested this
build without gnomeKeyringSupport yet, so it might be broken and will be
fixed later.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This release contains only minor fixes, which are:
* Fix AttributeError bugs in known_hosts file (re)loading.
* Note ecdsa requirement in README.
Full changelog with credits and issue IDs can be found at:
https://github.com/paramiko/paramiko/blob/master/NEWS
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
IIUC, <nixos> is going to be deprecated someday in the future, and as
most of those references are already replaced I guess it's safe to
replace it here as well, as it is only relevant on new/updated
installations.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
The site plugins are released alongside the main Tkabber sources, so it
makes no sense to have them in a separate package (which also introduces
an impurity). In addition, both packages share the same makefile
structure, so it really makes sense to merge them.
Before people might get worried about my decision to enable those
plugins by default: Since version 1.0, Tkabber is no longer loading
_all_ available plugins, but gives you a menu (Plugins Management) to
selectively enable plugins (whereas all plugins are disabled by
default).
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Alongside "tkabber", there is also "tkabber-remote", which uses the same
variables as the main script and thus needs to be wrapped the same way
as well.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
If people still want the ocean-deep theme, it can still be set by using:
tkabber.override { theme = "ocean-deep"; }
But by default we should not set a theme, so the user will get the same
result as everyone who installs the upstream version.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
After several years, Tkabber finally got a new release.
The highlights are:
* Completely rewritten Tkabber internals
* Dropped Tcl/Tk 8.3 support. Now Tcl/Tk 8.4 is required
* Partial IPv6 support (requires Tcl/Tk 8.6)
* Switched from TclGPGME to TclGPG for encryption and signing
* Added new connection method BOSH (XEP-0124 and XEP-0206)
* Disabled SSLv2 and enabled TLSv1 TLS options
* Added user nicknames (XEP-0172) support.
* Updated the CAPTCHA forms (XEP-0158) support
* Added metacontacts (XEP-0209) support
* Implemented multiple proxy profiles
* Implemented remote controlling from a locally executed script
* Added new plugins: floatingcontact, poker
* Rewritten most plugins to support disabling and unloading on the fly
* A few interface enhancements (search in MUC affiliations lists, proxy
management)
* Many fixes and enhancements
The detailed changelogs can be found at:
http://svn.xmpp.ru/repos/tkabber/tags/1.0/tkabber/ChangeLoghttp://svn.xmpp.ru/repos/tkabber/tags/1.0/tkabber-plugins/ChangeLog
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
I'm unsure about
- is it ok to apply this patch globally, or should it be overridden for tigervnc only?
- how many rebuilds it triggers
- whether it was neccessary to update to latest dev version (seems to work)
The bug report indicates that others distros just includes this patch (?)
Cf. #1498. vcunat: the patch should be usable globally, as e.g. Arch does it.
Using autoreconfHook doesn't work for me, maybe --force is bad for it.
- asn1-encoding: add version 0.8.1.2
- asn1-parse: add version 0.8.1
- x509-store: add version 1.4.3
- x509-system: add version 1.4.2
- x509-validation: add version 1.5.0
- x509: add version 1.4.7
