1 |
On Tuesday, December 20, 2016 09:59:44 AM Peter Humphrey wrote: |
2 |
> On Monday 19 Dec 2016 14:14:56 J. Roeleveld wrote: |
3 |
> > On Monday, December 19, 2016 09:45:21 AM Peter Humphrey wrote: |
4 |
> > > J. Roeleveld <joost@××××××××.org> wrote : |
5 |
> > > > On Sunday, December 18, 2016 03:11:58 PM Peter Humphrey wrote: |
6 |
> > > > > Peter Humphrey peter@××××××××××××.uk> |
7 |
> > > > |
8 |
> > > > wrote : |
9 |
> > > > > > This morning I ran my usual daily update and was presented with a |
10 |
> > > > > > long |
11 |
> > > > > > list of kde-app packages, including KMail-2. The only problem was |
12 |
> > > > > > four |
13 |
> > > > > > blocks that portage couldn't sort out on its own, so I evicted the |
14 |
> > > > > > existing versions with emerge -C and continued. |
15 |
> > > > > > |
16 |
> > > > > > Then kleopatra failed to build, as in bug 602924. The fix there |
17 |
> > > > > > worked |
18 |
> > > > |
19 |
> > > > (I |
20 |
> > > > |
21 |
> > > > > > should call it an evasion really) and kleopatra built ok. |
22 |
> > > > > |
23 |
> > > > > I should have done some more checking before writing. The fix was to |
24 |
> > > > |
25 |
> > > > emerge |
26 |
> > > > |
27 |
> > > > > -C kde-apps/gpgmepp. I don't know whether you can do that before |
28 |
> > > > > starting |
29 |
> > > > > the upgrade, but it's worth a try. It might save a lot of work. |
30 |
> > > > > |
31 |
> > > > > At any rate, there's no sign of gpgmepp being pulled back in with |
32 |
> > > > > the |
33 |
> > > > > new |
34 |
> > > > > 16.12.0 versions of kde-apps packages, now that the old versions |
35 |
> > > > > have |
36 |
> > > > |
37 |
> > > > gone. |
38 |
> > > > |
39 |
> > > > More important, how is the latest kmail behaving? |
40 |
> > > |
41 |
> > > It isn't. |
42 |
> > > |
43 |
> > > I finished the emerge -e world, then @preserved-rebuild presented me |
44 |
> > > with a whole lot of packages, resulting in the same appalling mess as |
45 |
> > > before: incompatible versions being required of numerous packages. I've |
46 |
> > > never had @preserved-rebuild follow an -e world before. |
47 |
> > |
48 |
> > Me neither, although I do wonder if it maybe caches something somewhere. |
49 |
> > I did just now have a preserved-rebuild after a depclean action. |
50 |
> > (This was after a clean update and no preserved-rebuild necessary prior to |
51 |
> > the depclean) |
52 |
> > |
53 |
> > > I've reverted to a week-old system backup, but now when I invoke KMail I |
54 |
> > > get a dialogue box saying "This will start the program kmail |
55 |
> > > -qwindowtitle %c %u. If you do not trust this program, click Cancel". |
56 |
> > > What? Of course I trust it, so I click Continue, and I get "Unable to |
57 |
> > > make the service KMail executable, aborting execution" |
58 |
> > > |
59 |
> > > What could possible go wrong with a simple offline tarring of files to |
60 |
> > > USB disk and back again? I know, I know... |
61 |
> > |
62 |
> > Did you include all the permissions in the tar during compression and |
63 |
> > extraction? |
64 |
> |
65 |
> The command in my backup script is: |
66 |
> |
67 |
> tar cpf /mnt/sda/peak/main/current/main.tar -C /mnt/main . |
68 |
> |
69 |
> /mnt/main is where my rescue system mounts the main system for backup. Do I |
70 |
> need to add --xattrs to the tar command? |
71 |
|
72 |
I do, when it comes to creating a stage4 tarfile. Not sure if this is |
73 |
necessary. |
74 |
|
75 |
Maybe that is used somewhere, or is it possible you miss something in the main |
76 |
system mount? |
77 |
|
78 |
-- |
79 |
Joost |