Greets all;
I just ran synaptic-pkexec to see if I needed any updates. On the 3 machine w/o TDE installed, no errors, however on this one, I get some, as follows:
Traceback (most recent call last): File "/usr/sbin/update-apt-xapian-index", line 102, in <module> indexer.incrementalUpdate() File "/usr/lib/pymodules/python2.7/axi/indexer.py", line 670, in incrementalUpdate self.updateIndex(dbpath) File "/usr/lib/pymodules/python2.7/axi/indexer.py", line 630, in updateIndex cache = self.aptcache() File "/usr/lib/pymodules/python2.7/axi/indexer.py", line 423, in aptcache self.apt_cache = apt.Cache(memonly=True, progress=aptprogress) File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 102, in __init__ self.open(progress) File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 147, in open self._records = apt_pkg.PackageRecords(self._cache) SystemError: E:Could not open file /var/lib/apt/lists/ppa.quickbuild.pearsoncomputing.net_trinity_trinity-r14.0.0_debian_dists_wheezy_main_binary-i386_Packages - open (2: No such file or directory)
Am I miss-configured? I would have thought that by now I would have been offered the upgrade to r14.1 but it hasn't occurred.
Thanks.
Cheers, Gene Heskett
On Sunday 09 August 2015 06:40:41 Gene Heskett wrote:
I would have thought that by now I would have been offered the upgrade to r14.1 but it hasn't occurred.
I don't think it has been officially released yet. Change to Slávek's repositories:
# Trinity preliminary stable builds deb http://mirror.xcer.cz/trinity-sb wheezy deps-r14 main-r14 deb-src http://mirror.xcer.cz/trinity-sb wheezy deps-r14 main-r14
with # apt-key adv --keyserver keys.gnupg.net --recv-key A04BE668
Though that wasn't working last weekend.
Lisi
On Sunday 09 August 2015 06:28:41 Lisi Reisz wrote:
On Sunday 09 August 2015 06:40:41 Gene Heskett wrote:
I would have thought that by now I would have been offered the upgrade to r14.1 but it hasn't occurred.
I don't think it has been officially released yet. Change to Slávek's repositories:
I thought I saw something to the effect that it was released, quite some time back. But since it wasn't in Tim's repo, I didn't switch. It wasn't a matter of looking for a specific fix as what I have seems to be working well so far except for clicking on send in kmail. But I've found the response to a ctl+return is instant, saving some mouse clicks.
# Trinity preliminary stable builds deb http://mirror.xcer.cz/trinity-sb wheezy deps-r14 main-r14 deb-src http://mirror.xcer.cz/trinity-sb wheezy deps-r14 main-r14
with # apt-key adv --keyserver keys.gnupg.net --recv-key A04BE668
Though that wasn't working last weekend.
Lisi
Thanks Lisi
Cheers, Gene Heskett
On Sunday 09 of August 2015 12:28:41 Lisi Reisz wrote:
On Sunday 09 August 2015 06:40:41 Gene Heskett wrote:
I would have thought that by now I would have been offered the upgrade to r14.1 but it hasn't occurred.
I don't think it has been officially released yet. Change to Slávek's repositories:
# Trinity preliminary stable builds deb http://mirror.xcer.cz/trinity-sb wheezy deps-r14 main-r14 deb-src http://mirror.xcer.cz/trinity-sb wheezy deps-r14 main-r14
with # apt-key adv --keyserver keys.gnupg.net --recv-key A04BE668
Though that wasn't working last weekend.
Lisi
As rightly pointed Lisi - R14.0.1 was not yet published in the official repository. For now, packages are in the preliminary stable builds apt repository. On the official build-farm building is underway. I estimate completion in order of days. After this will follow publishing.
Thank you for your patience.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
I would have thought that by now I would have been offered the upgrade to r14.1 but it hasn't occurred.
As rightly pointed Lisi - R14.0.1 was not yet published in the official repository.
Just to avoid confusion, R14.0.1 is going to be released sometime soon. This is the first maintenance release of R14.0.x series. R.14.1.x is under development and is not going to be released any time soon (we need time to develop something ;-) )
Cheers Michele
On Sunday 09 August 2015 19:49:13 Michele Calgaro wrote:
I would have thought that by now I would have been offered the upgrade to r14.1 but it hasn't occurred.
As rightly pointed Lisi - R14.0.1 was not yet published in the official repository.
Just to avoid confusion, R14.0.1 is going to be released sometime soon. This is the first maintenance release of R14.0.x series. R.14.1.x is under development and is not going to be released any time soon (we need time to develop something ;-) )
A fine but important point. Thanks for clarifying it.
Suggestion: kmails achilles heel is that its single threaded. So, if you have it going out on the network to fetch your mail on a regular schedule, you will note that it is totally non-responsive, and this includes this composer, during this time. It doesn't miss any keystrokes, but it can be 30 seconds to over a minute before the screen catches up to what you typed, and that to me is a major PIMA.
So my solution is to not setup an incoming account other than /var/spool/mail/$username.
So how do I get my incoming email? Fetchmail on a 180 second cycle.
It uses procmail for the MDA.
But before procmail delivers it, it runs the incoming thru spamassassin and clamd, rerouting the detected viri to a /var/spool/mail/virii mailfile, and one relatives messages are delivered directly to her folder in kmails Mail directory.
At the time any file in var/spool/mail is closed, inotifywatch returns the name of that file, and if its my name, sends kmail a msg over dbus to go get the mail and sort it to the correct folders, including the 'spam' folder if spamassassin gave it 5 or more stars. If it miss-sorts or miss-scores a good msg, I move that msg to the ham folder. Shortly after midnight, a cron script runs sa-learn ham/spam on those two folders, nuking tha spam folders contents when it has been done.
So basically my job is very simple. I hit the + key to read the next message, replying to it if I think I can help. Else I hit the + key and go read the next unread message. Everything else is all done for me. Whats not to like? Oh, I forgot, fetchmail sends mailfilter out first, which nukes some badass stuff off the server so it doesn't exist when fetchmail checks 3 seconds later.
Computers handle the drudgery a heck of a lot better than I do, so I write scripts to make them handle the needs a latex glove to touch stuff.
Cheers Michele
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett
-
Gene Heskett -
Lisi Reisz -
Michele Calgaro -
Slávek Banko