Re: Updates for the transifex-client package

<div><div dir="ltr">Hey Stefano, thanks for letting us know. We will coordinate with&nbsp;Jano&scaron; from here on out.<div><br></div>
<div>Cheers,</div>
<div>Ilias.</div>
<div class="gmail_extra">
<br clear="all"><div>On Fri, May 24, 2013 at 5:45 PM, Stefano Rivera <span dir="ltr">&lt;<a href="mailto:stefanor@..." target="_blank">stefanor@...</a>&gt;</span> wrote:<br>
</div>
<div class="gmail_quote"><blockquote class="gmail_quote">Hi Ilias-Dimitrios (2013.05.23_15:08:48_+0200)<br><div class="im">&gt; We noticed that you are currently maintaining a packaged version of the<br>
&gt; transifex command line client for Ubuntu.<br><br>
</div>The transifex-client package in Ubuntu follows the transifex-client<br>
package in Debian. Changes made in Debian, will flow into Ubuntu<br>
automatically, for the first half of each Ubuntu release cycle.<br><br><a href="https://wiki.ubuntu.com/DebianImportFreeze" target="_blank">https://wiki.ubuntu.com/DebianImportFreeze</a><br><a href="https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule" target="_blank">https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule</a><br><br>
So, I suggest you get in contact with the package maintainer in Debian,<br>
that's who you want to build a relationship with.<br><br><a href="http://packages.qa.debian.org/t/transifex-client.html" target="_blank">http://packages.qa.debian.org/t/transifex-client.html</a><br><span class="HOEnZb"><br>
SR<br><br>
--<br>
Stefano Rivera<br>
&nbsp; <a href="http://tumbleweed.org.za/" target="_blank">http://tumbleweed.org.za/</a><br>
&nbsp; H: <a href="tel:%2B27%2021%20461%201230" value="+27214611230">+27 21 461 1230</a> C: <a href="tel:%2B27%2072%20419%208559" value="+27724198559">+27 72 419 8559</a><br></span>
</blockquote></div>
<br>
</div>
</div></div>

Re: Updates for the transifex-client package

Hi Ilias-Dimitrios (2013.05.23_15:08:48_+0200)
> We noticed that you are currently maintaining a packaged version of the
> transifex command line client for Ubuntu.

The transifex-client package in Ubuntu follows the transifex-client
package in Debian. Changes made in Debian, will flow into Ubuntu
automatically, for the first half of each Ubuntu release cycle.

https://wiki.ubuntu.com/DebianImportFreeze
https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule

So, I suggest you get in contact with the package maintainer in Debian,
that's who you want to build a relationship with.

http://packages.qa.debian.org/t/transifex-client.html

SR

--

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  H: +27 21 461 1230 C: +27 72 419 8559

Updates for the transifex-client package

<div><div dir="ltr">
<div>Greetings,</div>
<div><br></div>
<div>We noticed that you are currently maintaining a packaged version of the transifex command line client for Ubuntu.</div>
<div>Would you like to be notified when we release new versions so you can update the packages?</div>

<div>If you want us to send the notification to an alternative email, feel free to tell us, and we will do so.</div>
<div><br></div>
<div>On behalf of all the Transifex team, thank you for taking the time to maintain this package</div>

<div>Best regards,</div>
<div>Ilias.</div>
<div><br></div>
</div></div>

Fatal error loading aolserver4-nssha1

Hi there,

In attempt to install OpenACS from scratch on ubuntu precise 12.04 I got 
the following error on aolserver4-nssha1. "could not find Ns_ModuleInit"

When I start up aolserver service I get a warning then a fatal error as 
decribed bellow:

[19/May/2013:19:27:15][18052.714974976][-main-] Notice: modload: loading 
'/usr/lib/aolserver4/bin/nssha1.so'
[19/May/2013:19:27:15][18052.714974976][-main-] Warning: modload: could 
not find Ns_ModuleInit in /usr/lib/aolserver4/bin/nssha1.so
[19/May/2013:19:27:15][18052.714974976][-main-] Fatal: modload: failed 
to load module '/usr/lib/aolserver4/bin/nssha1.so'

I verified that both files are correctly in place
/usr/lib/aolserver4/bin/nssha1.so
/usr/lib/aolserver4/lib/libnssha1.so

Furthermore, I installed aolserver packages via apt-get

I believe the package available on ubuntu repository was compiled 
without Ns_ModuleInit block.

Although, I'm reluctant to believe so I removed nssha1 and installed 
again fro tarball and the problem was solved.

Does anyone have any idea what it could be?
or if my assumption is valid?

Best wishes,
Iuri

Synaptic

Synaptic is running well, but it has a GTK Warning.
I can't say where exactly because I don't know the GTK API very well.

Synaptic is running well, but it has a GTK Warning.
I can't say where exactly because I don't know the GTK API very well.

"quake" package; suggestion

/usr/share/doc/quake/README.Debian

Suggestion. In that file, maybe add at the end of the second paragraph:
"Both the directory name and the files need to be in lower case."

The MS-DOS stuff is upper case, and the GNU/Linux quake executable
looks for lower case files.

Best regards,
Norbert

Re: Veusz version for Raring

please send replies to the mailing list.

maybe someone else will answer your mail.

On 22 April 2013 23:32, Stéphane Guillou <stephane.guillou <at> gmail.com> wrote:
> Hi Dmitrijs
>
> Thanks for your quick reply. I saw the versions in Launchpad, that's why I
> asked if the older version was going to be updated to 1.17
> But I guess you mean that this is not going to change, because "freeze" has
> already happened, right?
>
> Regards
>
> Stéphane
>
>
> On 22/04/13 18:35, Dmitrijs Ledkovs wrote:
>>
>> On 22 April 2013 07:29, Stéphane Guillou <stephane.guillou <at> gmail.com>
>> wrote:
>>>
>>> Hi there
>>>
>>> I was wondering if you were going to update the Veusz version from 1.15
>>> to
>>> 1.17 for Raring?
>>> Here is the post reporting the latest stable version:
>>> http://gna.org/forum/forum.php?forum_id=2391
>>>
>> You can check that on launchpad.
>>
>> See: https://launchpad.net/ubuntu/+source/veusz
>>
>> Regards,
>>
>> Dmitrijs.
>
>

--

-- 
Ubuntu-motu mailing list
Ubuntu-motu <at> lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: Veusz version for Raring

On 22 April 2013 07:29, Stéphane Guillou <stephane.guillou <at> gmail.com> wrote:
> Hi there
>
> I was wondering if you were going to update the Veusz version from 1.15 to
> 1.17 for Raring?
> Here is the post reporting the latest stable version:
> http://gna.org/forum/forum.php?forum_id=2391
>

You can check that on launchpad.

See: https://launchpad.net/ubuntu/+source/veusz

Regards,

Dmitrijs.

--

-- 
Ubuntu-motu mailing list
Ubuntu-motu <at> lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Veusz version for Raring

<div>
    Hi there<br><br>
    I was wondering if you were going to update the Veusz version from
    1.15 to 1.17 for Raring?<br>
    Here is the post reporting the latest stable version:
    <a href="http://gna.org/forum/forum.php?forum_id=2391">http://gna.org/forum/forum.php?forum_id=2391</a><br><br>
    Cheers<br><br>
    St&eacute;phane Guillou<br>
</div>

Bug in Ubuntu 12.10 fail2ban

<div><div class="WordSection1">
<p class="MsoNormal">Hi all<p></p></p>
<p class="MsoNormal">Fail2ban in for quantal do not block with iptables.<p></p></p>
<p class="MsoNormal">2013-04-13 14:23:19,569 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:20,570 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:22,572 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:23,573 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:24,574 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:25,575 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:26,576 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:27,577 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:28,578 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:29,580 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:30,581 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:31,582 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:32,583 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:33,584 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:34,585 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:35,586 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:36,587 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:37,588 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:38,589 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:39,590 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:40,591 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:41,592 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:42,593 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:43,595 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:44,595 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:45,596 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:46,597 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:47,598 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:48,599 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:49,600 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:50,601 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:51,602 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:52,604 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:53,605 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:54,606 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:55,606 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:56,607 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:57,608 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:58,609 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:23:59,610 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:00,611 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:01,612 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:02,613 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:03,615 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:04,616 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:05,617 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:06,618 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:07,619 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:08,620 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:09,621 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:10,622 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:11,623 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:12,625 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:13,625 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:14,626 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:15,627 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:16,628 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:17,629 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:18,630 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:19,631 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:20,633 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:21,633 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:22,635 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:23,635 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:24,636 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:25,637 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:26,638 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:27,639 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:28,640 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:29,641 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:30,643 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:31,644 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:32,646 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:33,646 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:34,647 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:35,648 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:36,649 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:37,650 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:38,651 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:39,652 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:40,653 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:41,654 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:42,655 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:43,656 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:44,657 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:45,658 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:46,660 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:47,661 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:48,661 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:49,662 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:50,663 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:51,664 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:52,666 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:53,666 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:54,667 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:55,668 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:56,670 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:57,671 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:24:58,672 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<br>2013-04-13 14:25:00,674 fail2ban.actions: WARNING [named-refused-tcp] 151.236.44.168 already banned<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">I must take the package from debian squeeze&hellip;<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Stefan<p></p></p>
</div></div>

wmctrl bug

<div>
    Can you help with a small bug ( -b add,hidden - not minimize
    window)? <a href="https://bugs.launchpad.net/ubuntu/+source/wmctrl/+bug/260875">https://bugs.launchpad.net/ubuntu/+source/wmctrl/+bug/260875</a>
    (see last comment about <span>XIconifyWindow</span>)
    <br><br>
    This is real working source code - <a href="https://github.com/geekless/wmctrl">https://github.com/geekless/wmctrl</a><br><br>
    But this working version program don't have a ubuntu repository. Who
    can help to create it ?<br>
    <br>
</div>