* [gentoo-user] Digest errors in an overlay, but only in one box
@ 2013-09-01 13:07 Mick
2013-09-01 14:45 ` Alan McKinnon
0 siblings, 1 reply; 6+ messages in thread
From: Mick @ 2013-09-01 13:07 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: Text/Plain, Size: 1414 bytes --]
Hi All,
I updated the enlightenment overlay on two PCs. The first which incidentally
I use as a portage mirror for my LAN works as expected, while the second PC is
coming up with these type of errors:
# emerge -uaDv world
These are the packages that would be merged, in order:
Calculating dependencies - * Missing digest for
'/var/lib/layman/enlightenment/media-libs/ethumb/ethumb-1.7.1.ebuild'
- * Digest verification failed:
* /var/lib/layman/enlightenment/x11-plugins/e_modules-forecasts/e_modules-
forecasts-9999.ebuild
* Reason: Filesize does not match recorded size
* Got: 442
* Expected: 436
| * Digest verification failed:
* /var/lib/layman/enlightenment/x11-plugins/e_modules-tclock/e_modules-
tclock-9999.ebuild
* Reason: Filesize does not match recorded size
* Got: 385
* Expected: 379
[snip ...]
I removed everything below /var/lib/layman/enlightenment/* and resync'ed. I
keep getting the same errors. The layman/overlay on the two PCs is set the
same way as far as I can recall, the only difference being one is x86 and the
other amd64 arch.
Can you please give me some pointers in troubleshooting this? Why are the
digests wrong and if so why is this being picked up on one machine only and
not the other?
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-user] Digest errors in an overlay, but only in one box
2013-09-01 13:07 [gentoo-user] Digest errors in an overlay, but only in one box Mick
@ 2013-09-01 14:45 ` Alan McKinnon
2013-09-01 16:41 ` Mick
0 siblings, 1 reply; 6+ messages in thread
From: Alan McKinnon @ 2013-09-01 14:45 UTC (permalink / raw
To: gentoo-user
On 01/09/2013 15:07, Mick wrote:
> Hi All,
>
> I updated the enlightenment overlay on two PCs. The first which incidentally
> I use as a portage mirror for my LAN works as expected, while the second PC is
> coming up with these type of errors:
>
> # emerge -uaDv world
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies - * Missing digest for
> '/var/lib/layman/enlightenment/media-libs/ethumb/ethumb-1.7.1.ebuild'
> - * Digest verification failed:
> * /var/lib/layman/enlightenment/x11-plugins/e_modules-forecasts/e_modules-
> forecasts-9999.ebuild
> * Reason: Filesize does not match recorded size
> * Got: 442
> * Expected: 436
> | * Digest verification failed:
> * /var/lib/layman/enlightenment/x11-plugins/e_modules-tclock/e_modules-
> tclock-9999.ebuild
> * Reason: Filesize does not match recorded size
> * Got: 385
> * Expected: 379
> [snip ...]
>
> I removed everything below /var/lib/layman/enlightenment/* and resync'ed. I
> keep getting the same errors. The layman/overlay on the two PCs is set the
> same way as far as I can recall, the only difference being one is x86 and the
> other amd64 arch.
>
> Can you please give me some pointers in troubleshooting this? Why are the
> digests wrong and if so why is this being picked up on one machine only and
> not the other?
>
What's the contents of the Manifest file in those two directories?
What does "ls -al" say ebuild the supposedly faulty ebuilds?
I also note the error reported in both cases is exactly 6 bytes.
Might be significant, let's keep that in mind
--
Alan McKinnon
alan.mckinnon@gmail.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-user] Digest errors in an overlay, but only in one box
2013-09-01 14:45 ` Alan McKinnon
@ 2013-09-01 16:41 ` Mick
2013-09-01 18:25 ` Alan McKinnon
0 siblings, 1 reply; 6+ messages in thread
From: Mick @ 2013-09-01 16:41 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1.1: Type: Text/Plain, Size: 5752 bytes --]
On Sunday 01 Sep 2013 15:45:05 Alan McKinnon wrote:
> What's the contents of the Manifest file in those two directories?
> What does "ls -al" say ebuild the supposedly faulty ebuilds?
>
> I also note the error reported in both cases is exactly 6 bytes.
> Might be significant, let's keep that in mind
Thanks Alan, it's not just these two ebuilds digests that come up with errors.
I attach the complete error. I compared the corresponding Manifests between
the two PCs and there no differences. For example:
Good PC:
=======
# sha1sum /var/lib/layman/enlightenment/x11-plugins/e_modules-
forecasts/Manifest
d058dc5e9f6443a9f4e3a02f32c8dde9c2ae1844 /var/lib/layman/enlightenment/x11-
plugins/e_modules-forecasts/Manifest
Bad PC:
======
$ sha1sum /var/lib/layman/enlightenment/x11-plugins/e_modules-
forecasts/Manifest
d058dc5e9f6443a9f4e3a02f32c8dde9c2ae1844 /var/lib/layman/enlightenment/x11-
plugins/e_modules-forecasts/Manifest
Similarly, there's no difference between the checksums of the ebuilds in the
two PCs.
Here is the content of the e_modules-forecasts Manifest:
=======================================================
$ cat /var/lib/layman/enlightenment/x11-plugins/e_modules-forecasts/Manifest
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
EBUILD e_modules-forecasts-9999.ebuild 436 SHA256
66c7fd87b666ec5b29e3756b36ed3fcd3140c267a02757fe29997e912ad8fc05 SHA512
952910877f0cc2f36fb9980822b3088652c4f813de6ed1fa584fa9c9737c832000a5e7ffdce00bc9c255cf1663cc0efd76ec6910ba504e515303be44b9d792bc
WHIRLPOOL
8f7ba88d7658257d6cf9a9655a7152ed7bf6b126dade35a3f6304451bd2f16621e36298ac10b8c8420259dfae14e28289ba20bbec84373c25ed5f538df5bc8f1
MISC ChangeLog 225 SHA256
e4290d34b0e8936f485adee22ec8e596fdeff60ed041c03f0a6925bcdc973c2f SHA512
48819cea3e04612f94feeb8511cc79a583e777fa1de438ca287f8f8289301537b4ff4df5c1fe96d8edd6a10bc1f0a0dd76020e30b4e2210ff5e119239ce33664
WHIRLPOOL
41478a52980a23476d21eec41a32d77dada0ced86b7baadd59bc8db9adbf06ae3c7d38b55516dec57a60a4ad67bae9d2d3aae6066f6ad6589b34ee6499420b52
MISC metadata.xml 228 SHA256
42ea435327140212f3beb05aafebad5053cbad84532f9bb78987de8540c6459a SHA512
5b1191ceaa7bcaa10b4b28d5b80cbb214da3e5857c2897f7b8001d3ac7ef3491c2dbb8a51583677c79770c106368297c16698d7a10b5ba85ce211412a61ae8bd
WHIRLPOOL
ed7fa6aacaa62a04fd1d184fc7a86eff8bd65a29664dca293f6723db14d1b8c22e5707cb0c1a0c7405cf2da2e0af1c031f7c9406fda5dfe74df3421b47b1cbf3
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iJwEAQEIAAYFAlDewwEACgkQG7kqcTWJkGfjiAP+OKqYKSf8DefFXND/+MWK5Zk1
ib+e0yc1nF+QpmrO8G1GhsR2lNu/zTpBh0qyL9w4lfsFz39lUu8/+AqVVR0CRyfS
pzagurDvQ5Rw+/h2qY/6uyUzPSSQxY7t5JUyzP70P8EPETqX934Nwl8KjpWktiHL
d0M80h8apliu6eYI14Y=
=h2o0
-----END PGP SIGNATURE-----
=======================================================
On the good PC I am able to emerge tclock:
=========================================
# emerge -1aDv x11-plugins/e_modules-tclock
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N *] x11-plugins/e_modules-tclock-9999::enlightenment USE="nls -
doc" 0 kB
Total: 1 package (1 new), Size of downloads: 0 kB
The following keyword changes are necessary to proceed:
(see "package.accept_keywords" in the portage(5) man page for more details)
# required by x11-plugins/e_modules-tclock (argument)
=x11-plugins/e_modules-tclock-9999 **
NOTE: The --autounmask-keep-masks option will prevent emerge
from creating package.unmask or ** keyword changes.
Use --autounmask-write to write changes to config files (honoring
CONFIG_PROTECT). Carefully examine the list of proposed changes,
paying special attention to mask or keyword changes that may expose
experimental or unstable packages.
=========================================
On the bad PC it complaints of corrupt files:
============================================
# emerge -1aDv x11-plugins/e_modules-tclock
These are the packages that would be merged, in order:
Calculating dependencies \ * Digest verification failed:
* /var/lib/layman/enlightenment/x11-plugins/e_modules-tclock/e_modules-
tclock-9999.ebuild
* Reason: Filesize does not match recorded size
* Got: 385
* Expected: 379
... done!
!!! All ebuilds that could satisfy "x11-plugins/e_modules-tclock" have been
masked.
!!! One of the following masked packages is required to complete your request:
- x11-plugins/e_modules-tclock-9999::enlightenment (masked by: corruption)
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
============================================
The content of two overlay package directories listed here as an example, from
the bad PC:
# ls -la /var/lib/layman/enlightenment/x11-plugins/e_modules-tclock
total 24
drwxr-xr-x 2 root root 4096 Sep 1 17:33 .
drwxr-xr-x 39 root root 4096 Sep 1 17:33 ..
-rw-r--r-- 1 root root 219 Sep 1 17:33 ChangeLog
-rw-r--r-- 1 root root 1487 Sep 1 17:33 Manifest
-rw-r--r-- 1 root root 385 Sep 1 17:33 e_modules-tclock-9999.ebuild
-rw-r--r-- 1 root root 228 Sep 1 17:33 metadata.xml
# ls -la /var/lib/layman/enlightenment/x11-plugins/e_modules-forecasts/total
24
drwxr-xr-x 2 root root 4096 Sep 1 17:33 .
drwxr-xr-x 39 root root 4096 Sep 1 17:33 ..
-rw-r--r-- 1 root root 225 Sep 1 17:33 ChangeLog
-rw-r--r-- 1 root root 1490 Sep 1 17:33 Manifest
-rw-r--r-- 1 root root 442 Sep 1 17:33 e_modules-forecasts-9999.ebuild
-rw-r--r-- 1 root root 228 Sep 1 17:33 metadata.xml
I am completely confused with this. :-/
--
Regards,
Mick
[-- Attachment #1.2: overlay_digest_errors.txt --]
[-- Type: text/plain, Size: 2835 bytes --]
# emerge -uaDv world
These are the packages that would be merged, in order:
Calculating dependencies |
* Missing digest for '/var/lib/layman/enlightenment/x11-wm/enlightenment/enlightenment-0.17.9999.ebuild'
* Digest verification failed:
* /var/lib/layman/enlightenment/media-libs/imlib2/imlib2-9999.ebuild
* Reason: Filesize does not match recorded size
* Got: 1436
* Expected: 1387
* Digest verification failed:
* /var/lib/layman/enlightenment/dev-libs/eet/eet-9999.ebuild
* Reason: Filesize does not match recorded size
* Got: 1488
* Expected: 1417
* Digest verification failed:
* /var/lib/layman/enlightenment/dev-libs/efreet/efreet-9999.ebuild
* Reason: Filesize does not match recorded size
* Got: 472
* Expected: 401
* Digest verification failed:
* /var/lib/layman/enlightenment/dev-libs/eeze/eeze-9999.ebuild
* Reason: Filesize does not match recorded size
* Got: 611
* Expected: 540
* Digest verification failed:
* /var/lib/layman/enlightenment/dev-libs/e_dbus/e_dbus-9999.ebuild
* Reason: Filesize does not match recorded size
* Got: 1532
* Expected: 1461
* Digest verification failed:
* /var/lib/layman/enlightenment/media-libs/edje/edje-9999.ebuild
* Reason: Filesize does not match recorded size
* Got: 1081
* Expected: 1010
* Missing digest for '/var/lib/layman/enlightenment/dev-libs/eio/eio-9999.ebuild'
* Digest verification failed:
* /var/lib/layman/enlightenment/dev-libs/eina/eina-9999.ebuild
* Reason: Filesize does not match recorded size
* Got: 2061
* Expected: 1990
* Missing digest for '/var/lib/layman/enlightenment/media-libs/emotion/emotion-9999.ebuild' / * Digest verification failed:
* /var/lib/layman/enlightenment/dev-libs/ecore/ecore-9999.ebuild
* Reason: Filesize does not match recorded size
* Got: 4471
* Expected: 4400
* Digest verification failed:
* /var/lib/layman/enlightenment/media-libs/evas/evas-9999.ebuild
* Reason: Filesize does not match recorded size
* Got: 3813
* Expected: 3742
* Digest verification failed:
* /var/lib/layman/enlightenment/dev-libs/embryo/embryo-9999.ebuild
* Reason: Filesize does not match recorded size
* Got: 373
* Expected: 302
* Missing digest for '/var/lib/layman/enlightenment/media-libs/ethumb/ethumb-9999.ebuild'
* Digest verification failed:
* /var/lib/layman/enlightenment/media-libs/elementary/elementary-9999.ebuild
* Reason: Filesize does not match recorded size
* Got: 1056
* Expected: 987
... done!
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-user] Digest errors in an overlay, but only in one box
2013-09-01 16:41 ` Mick
@ 2013-09-01 18:25 ` Alan McKinnon
2013-09-01 19:18 ` Mick
0 siblings, 1 reply; 6+ messages in thread
From: Alan McKinnon @ 2013-09-01 18:25 UTC (permalink / raw
To: gentoo-user
That overlay hasn't been manifested properly, the checksums and file
sizes don't match. You have two options:
redigest every ebuild in the entire overlay
resync and hope it's fixed (maybe report a bug)
Just to confirm, this is vapier's overlay you are using? Not niifaq?
I recall manifest problems with niifaq overlay a while ago, but can't
recall issues with vapier's. It isn't the portage tree though, so I
imagine it can be easy to forget the manifest step when committing files.
What I can't explain is why one pc is happy using the overlay files and
the other not. AFAIK portage doesn't allow digest checks to be disabled.
On 01/09/2013 18:41, Mick wrote:
> On Sunday 01 Sep 2013 15:45:05 Alan McKinnon wrote:
>
>> What's the contents of the Manifest file in those two directories?
>> What does "ls -al" say ebuild the supposedly faulty ebuilds?
>>
>> I also note the error reported in both cases is exactly 6 bytes.
>> Might be significant, let's keep that in mind
>
> Thanks Alan, it's not just these two ebuilds digests that come up with errors.
> I attach the complete error. I compared the corresponding Manifests between
> the two PCs and there no differences. For example:
>
> Good PC:
> =======
> # sha1sum /var/lib/layman/enlightenment/x11-plugins/e_modules-
> forecasts/Manifest
> d058dc5e9f6443a9f4e3a02f32c8dde9c2ae1844 /var/lib/layman/enlightenment/x11-
> plugins/e_modules-forecasts/Manifest
>
>
> Bad PC:
> ======
> $ sha1sum /var/lib/layman/enlightenment/x11-plugins/e_modules-
> forecasts/Manifest
> d058dc5e9f6443a9f4e3a02f32c8dde9c2ae1844 /var/lib/layman/enlightenment/x11-
> plugins/e_modules-forecasts/Manifest
>
>
> Similarly, there's no difference between the checksums of the ebuilds in the
> two PCs.
>
>
> Here is the content of the e_modules-forecasts Manifest:
> =======================================================
> $ cat /var/lib/layman/enlightenment/x11-plugins/e_modules-forecasts/Manifest
> EBUILD e_modules-forecasts-9999.ebuild 436 SHA256
> 66c7fd87b666ec5b29e3756b36ed3fcd3140c267a02757fe29997e912ad8fc05 SHA512
> 952910877f0cc2f36fb9980822b3088652c4f813de6ed1fa584fa9c9737c832000a5e7ffdce00bc9c255cf1663cc0efd76ec6910ba504e515303be44b9d792bc
> WHIRLPOOL
> 8f7ba88d7658257d6cf9a9655a7152ed7bf6b126dade35a3f6304451bd2f16621e36298ac10b8c8420259dfae14e28289ba20bbec84373c25ed5f538df5bc8f1
> MISC ChangeLog 225 SHA256
> e4290d34b0e8936f485adee22ec8e596fdeff60ed041c03f0a6925bcdc973c2f SHA512
> 48819cea3e04612f94feeb8511cc79a583e777fa1de438ca287f8f8289301537b4ff4df5c1fe96d8edd6a10bc1f0a0dd76020e30b4e2210ff5e119239ce33664
> WHIRLPOOL
> 41478a52980a23476d21eec41a32d77dada0ced86b7baadd59bc8db9adbf06ae3c7d38b55516dec57a60a4ad67bae9d2d3aae6066f6ad6589b34ee6499420b52
> MISC metadata.xml 228 SHA256
> 42ea435327140212f3beb05aafebad5053cbad84532f9bb78987de8540c6459a SHA512
> 5b1191ceaa7bcaa10b4b28d5b80cbb214da3e5857c2897f7b8001d3ac7ef3491c2dbb8a51583677c79770c106368297c16698d7a10b5ba85ce211412a61ae8bd
> WHIRLPOOL
> ed7fa6aacaa62a04fd1d184fc7a86eff8bd65a29664dca293f6723db14d1b8c22e5707cb0c1a0c7405cf2da2e0af1c031f7c9406fda5dfe74df3421b47b1cbf3
> =======================================================
>
>
> On the good PC I am able to emerge tclock:
> =========================================
> # emerge -1aDv x11-plugins/e_modules-tclock
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild N *] x11-plugins/e_modules-tclock-9999::enlightenment USE="nls -
> doc" 0 kB
>
> Total: 1 package (1 new), Size of downloads: 0 kB
>
> The following keyword changes are necessary to proceed:
> (see "package.accept_keywords" in the portage(5) man page for more details)
> # required by x11-plugins/e_modules-tclock (argument)
> =x11-plugins/e_modules-tclock-9999 **
>
> NOTE: The --autounmask-keep-masks option will prevent emerge
> from creating package.unmask or ** keyword changes.
>
> Use --autounmask-write to write changes to config files (honoring
> CONFIG_PROTECT). Carefully examine the list of proposed changes,
> paying special attention to mask or keyword changes that may expose
> experimental or unstable packages.
> =========================================
>
>
> On the bad PC it complaints of corrupt files:
> ============================================
> # emerge -1aDv x11-plugins/e_modules-tclock
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies \ * Digest verification failed:
> * /var/lib/layman/enlightenment/x11-plugins/e_modules-tclock/e_modules-
> tclock-9999.ebuild
> * Reason: Filesize does not match recorded size
> * Got: 385
> * Expected: 379
> ... done!
>
> !!! All ebuilds that could satisfy "x11-plugins/e_modules-tclock" have been
> masked.
> !!! One of the following masked packages is required to complete your request:
> - x11-plugins/e_modules-tclock-9999::enlightenment (masked by: corruption)
>
> For more information, see the MASKED PACKAGES section in the emerge
> man page or refer to the Gentoo Handbook.
> ============================================
>
> The content of two overlay package directories listed here as an example, from
> the bad PC:
>
> # ls -la /var/lib/layman/enlightenment/x11-plugins/e_modules-tclock
> total 24
> drwxr-xr-x 2 root root 4096 Sep 1 17:33 .
> drwxr-xr-x 39 root root 4096 Sep 1 17:33 ..
> -rw-r--r-- 1 root root 219 Sep 1 17:33 ChangeLog
> -rw-r--r-- 1 root root 1487 Sep 1 17:33 Manifest
> -rw-r--r-- 1 root root 385 Sep 1 17:33 e_modules-tclock-9999.ebuild
> -rw-r--r-- 1 root root 228 Sep 1 17:33 metadata.xml
>
> # ls -la /var/lib/layman/enlightenment/x11-plugins/e_modules-forecasts/total
> 24
> drwxr-xr-x 2 root root 4096 Sep 1 17:33 .
> drwxr-xr-x 39 root root 4096 Sep 1 17:33 ..
> -rw-r--r-- 1 root root 225 Sep 1 17:33 ChangeLog
> -rw-r--r-- 1 root root 1490 Sep 1 17:33 Manifest
> -rw-r--r-- 1 root root 442 Sep 1 17:33 e_modules-forecasts-9999.ebuild
> -rw-r--r-- 1 root root 228 Sep 1 17:33 metadata.xml
>
>
> I am completely confused with this. :-/
>
--
Alan McKinnon
Systems Engineer^W Technician
Infrastructure Services
Internet Solutions
+27 11 575 7585
--
Alan McKinnon
alan.mckinnon@gmail.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-user] Digest errors in an overlay, but only in one box
2013-09-01 18:25 ` Alan McKinnon
@ 2013-09-01 19:18 ` Mick
2013-09-02 5:45 ` Mick
0 siblings, 1 reply; 6+ messages in thread
From: Mick @ 2013-09-01 19:18 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: Text/Plain, Size: 1383 bytes --]
On Sunday 01 Sep 2013 19:25:45 Alan McKinnon wrote:
> That overlay hasn't been manifested properly, the checksums and file
> sizes don't match. You have two options:
>
> redigest every ebuild in the entire overlay
I wasn't going to do this, given that one machine is happy.
> resync and hope it's fixed (maybe report a bug)
Right, I tried that already, but I can wait a bit longer and resync again.
With regards to filing a bug, I spoke to Thomas Sachau and he can't reproduce
the problem on his side. Hence I ended up blaming something being wrong with
my machine ...
> Just to confirm, this is vapier's overlay you are using? Not niifaq?
Yes, this is vapier's overlay.
> I recall manifest problems with niifaq overlay a while ago, but can't
> recall issues with vapier's. It isn't the portage tree though, so I
> imagine it can be easy to forget the manifest step when committing files.
>
> What I can't explain is why one pc is happy using the overlay files and
> the other not. AFAIK portage doesn't allow digest checks to be disabled.
Right, I can't explain this either. It's not as if each machine is using a
somehow unique digest mechanism. I really don't understand how this can be
happening, especially when I removed the whole /var/lib/layman/enlightenment/*
tree on the dodgy PC and resync'ed.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-user] Digest errors in an overlay, but only in one box
2013-09-01 19:18 ` Mick
@ 2013-09-02 5:45 ` Mick
0 siblings, 0 replies; 6+ messages in thread
From: Mick @ 2013-09-02 5:45 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: Text/Plain, Size: 342 bytes --]
On Sunday 01 Sep 2013 20:18:54 you wrote:
> On Sunday 01 Sep 2013 19:25:45 Alan McKinnon wrote:
> > Just to confirm, this is vapier's overlay you are using? Not niifaq?
>
> Yes, this is vapier's overlay.
I think I got to the bottom of it.
I reinstalled layman and all errors seem to have gone for now. :-)
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-09-02 5:46 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-09-01 13:07 [gentoo-user] Digest errors in an overlay, but only in one box Mick
2013-09-01 14:45 ` Alan McKinnon
2013-09-01 16:41 ` Mick
2013-09-01 18:25 ` Alan McKinnon
2013-09-01 19:18 ` Mick
2013-09-02 5:45 ` Mick
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox