[MacPorts] #40756: mcabber @0.9.10 and libotr @3.2.1 are outdated.
#40756: mcabber @0.9.10 and libotr @3.2.1 are outdated. ---------------------------------+---------------------------------------- Reporter: christoph_murauer@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: mcabber, loudmouth, libotr ---------------------------------+---------------------------------------- Hello ! There is a newer version of mcabber (0.10.2) available on http://mcabber.com. There is also a patched version of loudmouth available on the same site (don't know whats the difference between the other used version of loudmouth). There is also a newer version of libotr (which is a dep. for OTR) available. I find no maintainer for loudmouth and libotr - please add the required people - thanks. Thanks for updating. -- Ticket URL: <https://trac.macports.org/ticket/40756> MacPorts <http://www.macports.org/> Ports system for OS X
#40756: mcabber @0.9.10 and libotr @3.2.1 are outdated. -----------------------------------------+--------------------- Reporter: christoph_murauer@… | Owner: simon@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: mcabber, loudmouth, libotr | -----------------------------------------+--------------------- Changes (by raimue@…): * owner: macports-tickets@… => simon@… * cc: rsync@… (added) Comment: Assigning and adding maintainers to CC. -- Ticket URL: <https://trac.macports.org/ticket/40756#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#40756: mcabber @0.9.10 and libotr @3.2.1 are outdated. -----------------------------------------+--------------------- Reporter: christoph_murauer@… | Owner: simon@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: mcabber, loudmouth, libotr | -----------------------------------------+--------------------- Comment (by macports@…): Don't know if this belongs in a separate ticket, but related: loudmouth @1.4.3_2 won't build (under Mavericks) {{{ lm-sock.c:329:37: error: use of undeclared identifier 'TCP_KEEPIDLE' if (setsockopt (sock, IPPROTO_TCP, TCP_KEEPIDLE, &opt, sizeof (opt)) < 0) { ^ }}} Full log attached. -- Ticket URL: <https://trac.macports.org/ticket/40756#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#40756: mcabber @0.9.10 and libotr @3.2.1 are outdated. -----------------------------------------+--------------------- Reporter: christoph_murauer@… | Owner: simon@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mcabber, loudmouth, libotr | -----------------------------------------+--------------------- Changes (by mojca@…): * cc: mojca@… (added) * version: 2.2.0 => Comment: I committed an update to `libotr` in r121174. The weird issues are: {{{ libtool: install: warning: `../src/libotr.la' has not been installed in `/opt/local/lib' ... Warning: An activity was attempted outside sandbox: /opt/local/lib/libotr.la Warning: An activity was attempted outside sandbox: /opt/local/bin/ranlib }}} The first one seems like inability to distinguish between DESTDIR and the final location. The second one might be a missing build dependency on `cctools`, but I'm not sure. I guess dependent ports need an upgrade now. -- Ticket URL: <https://trac.macports.org/ticket/40756#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#40756: mcabber @0.9.10 and libotr @3.2.1 are outdated. -----------------------------------------+--------------------- Reporter: christoph_murauer@… | Owner: simon@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mcabber, loudmouth, libotr | -----------------------------------------+--------------------- Comment (by mojca@…): I attached a patch to upgrade `mcabber`. The problem is that `configure` now complains about {{{ configure: WARNING: unrecognized options: --without-ssl, --without-openssl }}} so it looks as if some variants would make no sense at all. But I don't use `mcabber`, so I don't know any details. After applying the patch the sandboxed build would complain about {{{ Warning: An activity was attempted outside sandbox: /.attbin/uname Warning: An activity was attempted outside sandbox: /bin;/bin/sh Warning: An activity was attempted outside sandbox: /opt/local/include/dlfcn.h Warning: An activity was attempted outside sandbox: /opt/local/lib/perl5/vendor_perl/5.16.3/darwin-thread-multi-2level/Cwd.pm Warning: An activity was attempted outside sandbox: /opt/local/lib/perl5/vendor_perl/5.16.3/darwin-thread-multi- 2level/File/Spec.pm Warning: An activity was attempted outside sandbox: /opt/local/lib/perl5/vendor_perl/5.16.3/darwin-thread-multi- 2level/File/Spec/Unix.pm Warning: An activity was attempted outside sandbox: /opt/local/lib/perl5/vendor_perl/5.16.3/darwin-thread-multi- 2level/List/Util.pm Warning: An activity was attempted outside sandbox: /opt/local/lib/perl5/vendor_perl/5.16.3/darwin-thread-multi- 2level/Scalar/Util.pm Warning: An activity was attempted outside sandbox: /opt/local/bin/hg Warning: An activity was attempted outside sandbox: /var/root/.CFUserTextEncoding Warning: An activity was attempted outside sandbox: /var/mail/macports }}} -- Ticket URL: <https://trac.macports.org/ticket/40756#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#40756: mcabber @0.9.10 and libotr @3.2.1 are outdated. -----------------------------------------+--------------------- Reporter: christoph_murauer@… | Owner: simon@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mcabber, loudmouth, libotr | -----------------------------------------+--------------------- Comment (by ryandesign@…): Replying to [comment:3 mojca@…]:
I guess dependent ports need an upgrade now.
A revision increase, at least, to rebuild against libotr.5 (previous library version was 2). However, skip bitlbee, which I've already updated, and also which doesn't build against libotr 4 yet. -- Ticket URL: <https://trac.macports.org/ticket/40756#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
#40756: mcabber @0.9.10 and libotr @3.2.1 are outdated. -----------------------------------------+--------------------- Reporter: christoph_murauer@… | Owner: simon@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mcabber, loudmouth, libotr | -----------------------------------------+--------------------- Comment (by mojca@…): I wanted the maintainer to check my patch for `mcabber` first, but he hasn't responded yet. Should I simply commit? What else still needs the revbump or upgrade? -- Ticket URL: <https://trac.macports.org/ticket/40756#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X
#40756: mcabber @0.9.10 and libotr @3.2.1 are outdated. -----------------------------------------+--------------------- Reporter: christoph_murauer@… | Owner: simon@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mcabber, loudmouth, libotr | -----------------------------------------+--------------------- Comment (by devans@…): Replying to [comment:4 mojca@…]:
I attached a patch to upgrade `mcabber`. The problem is that `configure` now complains about {{{ configure: WARNING: unrecognized options: --without-ssl, --without- openssl }}}
These options no longer exist in the updated version because the port relies on loudmouth for this functionality. The corresponding variants can be removed. -- Ticket URL: <https://trac.macports.org/ticket/40756#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X
#40756: mcabber @0.9.10 and libotr @3.2.1 are outdated. -----------------------------------------+--------------------- Reporter: christoph_murauer@… | Owner: simon@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mcabber, loudmouth, libotr | -----------------------------------------+--------------------- Comment (by devans@…): Replying to [comment:6 mojca@…]:
I wanted the maintainer to check my patch for `mcabber` first, but he hasn't responded yet. Should I simply commit?
MacPorts policy is that if the maintainer hasn't responded in 72 hours, you can go ahead and commit the patch including the phrase 'maintainer timeout' in the commit message. It's been much longer than that now and the port is otherwise broken. BTW, this patch works for me (with the superfluous variants removed). -- Ticket URL: <https://trac.macports.org/ticket/40756#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X
#40756: mcabber @0.9.10 and libotr @3.2.1 are outdated. -----------------------------------------+--------------------- Reporter: christoph_murauer@… | Owner: simon@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mcabber, loudmouth, libotr | -----------------------------------------+--------------------- Comment (by devans@…): Revised patch attached which * removes outdated configuration items --without-ssl --without-openssl * removes outdated +ssl +gnutls variants -- SSL/TLS now handled by loudmouth * adds license -- Ticket URL: <https://trac.macports.org/ticket/40756#comment:9> MacPorts <http://www.macports.org/> Ports system for OS X
#40756: mcabber @0.9.10 and libotr @3.2.1 are outdated. ---------------------------------------+--------------------- Reporter: christoph_murauer@… | Owner: simon@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: mcabber loudmouth libotr | ---------------------------------------+--------------------- Changes (by devans@…): * status: new => closed * resolution: => fixed * port: mcabber, loudmouth, libotr => mcabber loudmouth libotr Comment: mcabber updated to version 0.10.3 in r121811, maintainer timeout. -- Ticket URL: <https://trac.macports.org/ticket/40756#comment:10> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts