Re: Pkg repository is broken...
> On 8. Mar 2020, at 00:04, Greg 'groggy' Lehey wrote: > > On Saturday, 7 March 2020 at 23:55:33 +0100, Michael Gmelin wrote: > > [More irrelevant text deleted, also dropping current@] > > Is it really so difficult to trim your replies? > >> On 7. Mar 2020, at 23:39, Greg 'groggy' Lehey wrote: > ???On Saturday, 7 March 2020 at 16:46:58 +0100, Michael Gmelin wrote: >> This was only an issue on the "latest" branch. If you don't alter >> "/etc/pkg/FreeBSD.conf", you'll get packages from the "quarterly" >> branch, which fortunately wasn't affected. > No, this isn't necessarily correct. I have never modified this file, > but I ended up with a copy of /usr/src/usr.bin/pkg/FreeBSD.conf.latest > with this revision string: > # $FreeBSD: stable/11/etc/pkg/FreeBSD.conf 263937 2014-03-30 15:24:17Z > bdrewery $ > Despite the age, this appears to identical to the current version, > according to svn blame. Arguably this should be the default anyway. >> Installing 12.1 from install media gives you quarterly. > > Yes, quite possibly. But as I said, it's not always the case. In the part you trimmed he wrote: >> I installed 12.1 on a new laptop yesterday, I have not experienced >> issues with pkg. my comment > > This was only an issue on the "latest" branch. If you don't alter > "/etc/pkg/FreeBSD.conf", you'll get packages from the "quarterly" > branch, which fortunately wasn't affected. > was a direct response to that (fresh install of a 12.1 system). This obviously doesn’t necessarily apply to systems that have been updated from previous releases. -m ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pkg repository is broken...
On Saturday, 7 March 2020 at 23:55:33 +0100, Michael Gmelin wrote: [More irrelevant text deleted, also dropping current@] Is it really so difficult to trim your replies? >> On 7. Mar 2020, at 23:39, Greg 'groggy' Lehey wrote: >> >> ???On Saturday, 7 March 2020 at 16:46:58 +0100, Michael Gmelin wrote: >>> This was only an issue on the "latest" branch. If you don't alter >>> "/etc/pkg/FreeBSD.conf", you'll get packages from the "quarterly" >>> branch, which fortunately wasn't affected. >> >> No, this isn't necessarily correct. I have never modified this file, >> but I ended up with a copy of /usr/src/usr.bin/pkg/FreeBSD.conf.latest >> with this revision string: >> >> # $FreeBSD: stable/11/etc/pkg/FreeBSD.conf 263937 2014-03-30 15:24:17Z >> bdrewery $ >> >> Despite the age, this appears to identical to the current version, >> according to svn blame. Arguably this should be the default anyway. > > Installing 12.1 from install media gives you quarterly. Yes, quite possibly. But as I said, it's not always the case. Greg -- Sent from my desktop computer. Finger g...@freebsd.org for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA signature.asc Description: PGP signature
Re: Pkg repository is broken...
> On 7. Mar 2020, at 23:39, Greg 'groggy' Lehey wrote: > > On Saturday, 7 March 2020 at 16:46:58 +0100, Michael Gmelin wrote: > > [much irrelevant text deleted] > > People, please trim your replies. Only relevant text should remain > >>> On Sat, 07 Mar 2020 11:30:58 -0400 Waitman Gobble >>> wrote: >>> >>> I installed 12.1 on a new laptop yesterday, I have not experienced >>> issues with pkg. >> >> This was only an issue on the "latest" branch. If you don't alter >> "/etc/pkg/FreeBSD.conf", you'll get packages from the "quarterly" >> branch, which fortunately wasn't affected. > > No, this isn't necessarily correct. I have never modified this file, > but I ended up with a copy of /usr/src/usr.bin/pkg/FreeBSD.conf.latest > with this revision string: > > # $FreeBSD: stable/11/etc/pkg/FreeBSD.conf 263937 2014-03-30 15:24:17Z > bdrewery $ > > Despite the age, this appears to identical to the current version, > according to svn blame. Arguably this should be the default anyway. > Installing 12.1 from install media gives you quarterly. -m > Greg > -- > Sent from my desktop computer. > Finger g...@freebsd.org for PGP public key. > See complete headers for address and phone numbers. > This message is digitally signed. If your Microsoft mail program > reports problems, please read http://lemis.com/broken-MUA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pkg repository is broken...
On Saturday, 7 March 2020 at 16:46:58 +0100, Michael Gmelin wrote: [much irrelevant text deleted] People, please trim your replies. Only relevant text should remain > On Sat, 07 Mar 2020 11:30:58 -0400 Waitman Gobble wrote: >> >> I installed 12.1 on a new laptop yesterday, I have not experienced >> issues with pkg. > > This was only an issue on the "latest" branch. If you don't alter > "/etc/pkg/FreeBSD.conf", you'll get packages from the "quarterly" > branch, which fortunately wasn't affected. No, this isn't necessarily correct. I have never modified this file, but I ended up with a copy of /usr/src/usr.bin/pkg/FreeBSD.conf.latest with this revision string: # $FreeBSD: stable/11/etc/pkg/FreeBSD.conf 263937 2014-03-30 15:24:17Z bdrewery $ Despite the age, this appears to identical to the current version, according to svn blame. Arguably this should be the default anyway. Greg -- Sent from my desktop computer. Finger g...@freebsd.org for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA signature.asc Description: PGP signature
Re: Pkg repository is broken...
> On 7 Mar 2020, at 12:23, Adam Jimerson wrote: > > > On 3/7/20 6:56 AM, Michael Gmelin wrote: >> >> I worked around the situation locally by setting ALTABI >> on `pkg update': >> >> # ALTABI=FreeBSD:12.0:amd64 pkg update -f >> >> This allowed me to run >> >> # pkg upgrade >> >> without any issues, so I assume none of the about 30 packages I updated >> contained a wrong ABI/architecture. >> >> I verified this by checking: >> >> # pkg query "%q" | sort | uniq -c >> 112 FreeBSD:12:* >> 219 FreeBSD:12:amd64 >> >> Note that you could also export ALTABI to the environment or set it >> in /usr/local/etc/pkg.conf, but I figured that I might forget it in >> there. >> >> Also, it seems like none of my packages were affected and not setting >> it on `pkg upgrade' meant that pkg checks for that (at least that's >> what I assume it does) and therefore I won't have to deal with >> different ABIs in my installed packages later. >> >> All of this should be really temporary anyway and hopefully be resolved >> soon. >> >> Cheers, >> Michael >> > > I'm not screaming either, figured it wouldn't really help speed up > fixing things and that the right people were already working on fixing > it. I am also still getting this on 12.1-RELEASE, but the ALTABI work > around worked for me. > I also figured it will get fixed eventually, and it was my decision to switch from the default quarterly repo to the latest repo, so have to expect some problems from time to time. It would be nice to have some sort of indicator as to the progress the process though, it was a little confusing to see the package build server for 121amd64 had finished a day or two before the repo actually got updated, I guess it either has to wait for all builds to be finished and sync with mirrors? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pkg repository is broken...
On Sat, 07 Mar 2020 11:30:58 -0400 Waitman Gobble wrote: > On 2020-03-07 05:10, Ronald Klop wrote: > > On Sat, 07 Mar 2020 01:38:55 +0100, Greg 'groggy' Lehey > > wrote: > > > >> On Friday, 6 March 2020 at 12:29:44 +0100, Lars Engels wrote: > >>> On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey > >>> wrote: > > Any workarounds in the meantime? This must affect a lot of > people, including those who use 12-: > > pkg: wrong architecture: FreeBSD:12.0:amd64 instead of > FreeBSD:12:amd64 > pkg: repository FreeBSD contains packages with wrong ABI: > FreeBSD:12.0:amd64 > >>> > >>> Still broken for me on 12.1. > >> > >> Strange. Mine cleared up automatically the following day. > >> > >> It's also strange how few replies I have received. Two private > >> messages (why?), yours, and that was it. You'd think that people > >> would be screaming. > >> > >> Greg > > > > > > I'm not screaming because I'm settling with the situation and > > starting to make workarounds. > > And wondering where the official communication of the community is. > > Nothing about this situation on www.freebsd.org. All information > > about the situation seems scattered through the mailinglists. > > > > Things are working for me on 13-CURRENT again, but still broken on > > 12.1-RELEASE. See attachment. > > > > Ronald. > > ___ > > freebsd-curr...@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to > > "freebsd-current-unsubscr...@freebsd.org" > > > Did you try: > pkg update -f > > > I installed 12.1 on a new laptop yesterday, I have not experienced > issues with pkg. > This was only an issue on the "latest" branch. If you don't alter "/etc/pkg/FreeBSD.conf", you'll get packages from the "quarterly" branch, which fortunately wasn't affected. Anyway, this has been fixed as of today 13:30 UTC, see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244549#c43 -m -- Michael Gmelin ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pkg repository is broken...
On 3/7/20 6:56 AM, Michael Gmelin wrote: > > I worked around the situation locally by setting ALTABI > on `pkg update': > > # ALTABI=FreeBSD:12.0:amd64 pkg update -f > > This allowed me to run > > # pkg upgrade > > without any issues, so I assume none of the about 30 packages I updated > contained a wrong ABI/architecture. > > I verified this by checking: > > # pkg query "%q" | sort | uniq -c >112 FreeBSD:12:* >219 FreeBSD:12:amd64 > > Note that you could also export ALTABI to the environment or set it > in /usr/local/etc/pkg.conf, but I figured that I might forget it in > there. > > Also, it seems like none of my packages were affected and not setting > it on `pkg upgrade' meant that pkg checks for that (at least that's > what I assume it does) and therefore I won't have to deal with > different ABIs in my installed packages later. > > All of this should be really temporary anyway and hopefully be resolved > soon. > > Cheers, > Michael > I'm not screaming either, figured it wouldn't really help speed up fixing things and that the right people were already working on fixing it. I am also still getting this on 12.1-RELEASE, but the ALTABI work around worked for me. signature.asc Description: OpenPGP digital signature
Re: Pkg repository is broken...
On Sat, 07 Mar 2020 10:10:43 +0100 "Ronald Klop" wrote: > On Sat, 07 Mar 2020 01:38:55 +0100, Greg 'groggy' Lehey > wrote: > > > On Friday, 6 March 2020 at 12:29:44 +0100, Lars Engels wrote: > >> On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey > >> wrote: > >>> > >>> Any workarounds in the meantime? This must affect a lot of > >>> people, including those who use 12-: > >>> > >>> pkg: wrong architecture: FreeBSD:12.0:amd64 instead of > >>> FreeBSD:12:amd64 > >>> pkg: repository FreeBSD contains packages with wrong ABI: > >>> FreeBSD:12.0:amd64 > >> > >> Still broken for me on 12.1. > > > > Strange. Mine cleared up automatically the following day. > > > > It's also strange how few replies I have received. Two private > > messages (why?), yours, and that was it. You'd think that people > > would be screaming. > > > > Greg > > > I'm not screaming because I'm settling with the situation and > starting to make workarounds. > And wondering where the official communication of the community is. > Nothing about this situation on www.freebsd.org. All information > about the situation seems scattered through the mailinglists. > > Things are working for me on 13-CURRENT again, but still broken on > 12.1-RELEASE. See attachment. > I worked around the situation locally by setting ALTABI on `pkg update': # ALTABI=FreeBSD:12.0:amd64 pkg update -f This allowed me to run # pkg upgrade without any issues, so I assume none of the about 30 packages I updated contained a wrong ABI/architecture. I verified this by checking: # pkg query "%q" | sort | uniq -c 112 FreeBSD:12:* 219 FreeBSD:12:amd64 Note that you could also export ALTABI to the environment or set it in /usr/local/etc/pkg.conf, but I figured that I might forget it in there. Also, it seems like none of my packages were affected and not setting it on `pkg upgrade' meant that pkg checks for that (at least that's what I assume it does) and therefore I won't have to deal with different ABIs in my installed packages later. All of this should be really temporary anyway and hopefully be resolved soon. Cheers, Michael -- Michael Gmelin ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pkg repository is broken...
Am 07.03.2020 um 08:50 schrieb sth...@nethelp.no: > > I think a lot of people are waiting for some kind of guidance on how > to fix these problems, if the repos are supposed to be okay now. It would be really great if someone in the know would send something to -announce or similar, with an ETR. Maybe even with suggestions for workarounds. A forum thread mentions a workaround for those that cannot easily start compiling their own ports: https://forums.freebsd.org/threads/pkg-wrong-architecture-freebsd-12-0-amd64-instead-of-freebsd-12-amd64.74310/page-3 > ALTABI thing must be added in /usr/local/etc/pkg.conf: ALTABI = > "FreeBSD:12.0:amd64" Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: Pkg repository is broken...
Le sam. 7 mars 20 à 1:38:55 +0100, Greg 'groggy' Lehey écrivait : > > Still broken for me on 12.1. Still broken for me on 12.1-STABLE, but with a different error: "size mismatch, fetching from remote" and then "size mismatch, cannot continue" for the first package being fetched. Same after a `pkg clean'. > Strange. Mine cleared up automatically the following day. > > It's also strange how few replies I have received. Two private > messages (why?), yours, and that was it. You'd think that people > would be screaming. I read somewhere that the packages building farm switched from 12.0 to 12.1, and I was just waiting for the dust to settle... -- Th. Thomas. signature.asc Description: PGP signature
Re: Pkg repository is broken...
On Sat, 07 Mar 2020 01:38:55 +0100, Greg 'groggy' Lehey wrote: On Friday, 6 March 2020 at 12:29:44 +0100, Lars Engels wrote: On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey wrote: Any workarounds in the meantime? This must affect a lot of people, including those who use 12-: pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64 pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:12.0:amd64 Still broken for me on 12.1. Strange. Mine cleared up automatically the following day. It's also strange how few replies I have received. Two private messages (why?), yours, and that was it. You'd think that people would be screaming. Greg I'm not screaming because I'm settling with the situation and starting to make workarounds. And wondering where the official communication of the community is. Nothing about this situation on www.freebsd.org. All information about the situation seems scattered through the mailinglists. Things are working for me on 13-CURRENT again, but still broken on 12.1-RELEASE. See attachment. Ronald.Sat Mar 7 09:06:04 UTC 2020 Updating FreeBSD repository catalogue... [freebsd12.klop.ws] Fetching meta.conf: . done [freebsd12.klop.ws] Fetching packagesite.txz: .. done Processing entries: .. pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64 pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:12.0:amd64 Processing entries... done Unable to update repository FreeBSD Error updating repositories! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pkg repository is broken...
On 3/6/20 7:41 PM, Marcin Cieslak wrote: > On Sat, 7 Mar 2020, Janky Jay, III wrote: > >> Still broken for me as well. I just figured I'd look into it when I >> got a chance. Also using FBSD 12.1 RELEASE. > > Maybe it depends on the mirror being used? Perhaps. I'm not really sure what's going on. But it's happening with multiple systems and I haven't changed anything from the defaults. Then again, it's also still using the /etc/pkg/FreeBSD.conf file (I guess) because there is no /usr/local/etc/pkg/ directory. Maybe I just need to update some other stuff. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pkg repository is broken...
On Sat, 7 Mar 2020, Janky Jay, III wrote: Still broken for me as well. I just figured I'd look into it when I got a chance. Also using FBSD 12.1 RELEASE. Maybe it depends on the mirror being used? smime.p7s Description: S/MIME Cryptographic Signature
Re: Pkg repository is broken...
Still broken for me as well. I just figured I'd look into it when I got a chance. Also using FBSD 12.1 RELEASE. Regards, Janky Jay, III On March 7, 2020 12:38:55 AM UTC, Greg 'groggy' Lehey wrote: >On Friday, 6 March 2020 at 12:29:44 +0100, Lars Engels wrote: >> On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey wrote: >>> >>> Any workarounds in the meantime? This must affect a lot of people, >>> including those who use 12-: >>> >>> pkg: wrong architecture: FreeBSD:12.0:amd64 instead of >FreeBSD:12:amd64 >>> pkg: repository FreeBSD contains packages with wrong ABI: >FreeBSD:12.0:amd64 >> >> Still broken for me on 12.1. > >Strange. Mine cleared up automatically the following day. > >It's also strange how few replies I have received. Two private >messages (why?), yours, and that was it. You'd think that people >would be screaming. > >Greg >-- >Sent from my desktop computer. >Finger g...@freebsd.org for PGP public key. >See complete headers for address and phone numbers. >This message is digitally signed. If your Microsoft mail program >reports problems, please read http://lemis.com/broken-MUA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pkg repository is broken...
Still effed here. -- Karl (on PDA) Original Message From: g...@freebsd.org Sent: March 6, 2020 18:38 To: lars.eng...@0x20.net; marco+freebsd-curr...@lordsith.net; freebsd-curr...@freebsd.org; freebsd-ports@freebsd.org Subject: Re: Pkg repository is broken... On Friday, 6 March 2020 at 12:29:44 +0100, Lars Engels wrote: > On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey wrote: >> >> Any workarounds in the meantime? This must affect a lot of people, >> including those who use 12-: >> >> pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64 >> pkg: repository FreeBSD contains packages with wrong ABI: >>FreeBSD:12.0:amd64 > > Still broken for me on 12.1. Strange. Mine cleared up automatically the following day. It's also strange how few replies I have received. Two private messages (why?), yours, and that was it. You'd think that people would be screaming. Greg -- Sent from my desktop computer. Finger g...@freebsd.org for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA smime.p7s Description: S/MIME cryptographic signature
Re: Pkg repository is broken...
On Friday, 6 March 2020 at 12:29:44 +0100, Lars Engels wrote: > On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey wrote: >> >> Any workarounds in the meantime? This must affect a lot of people, >> including those who use 12-: >> >> pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64 >> pkg: repository FreeBSD contains packages with wrong ABI: >> FreeBSD:12.0:amd64 > > Still broken for me on 12.1. Strange. Mine cleared up automatically the following day. It's also strange how few replies I have received. Two private messages (why?), yours, and that was it. You'd think that people would be screaming. Greg -- Sent from my desktop computer. Finger g...@freebsd.org for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA signature.asc Description: PGP signature
Re: Pkg repository is broken...
On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey wrote: > On Monday, 2 March 2020 at 17:58:01 +, marco wrote: > > On Sun, Mar 01, 2020 at 04:50:59PM -0500, you (Brennan Vincent) sent the > > following to [freebsd-current] : > >> Apparently something has its ABI erroneously listed as FreeBSD:13.0:amd64 > >> instead of FreeBSD:13:amd64. > >> > >> ``` > >> $ sudo pkg update -f > >> Updating FreeBSD repository catalogue... > >> Fetching meta.conf: 100%163 B 0.2kB/s00:01 > >> Fetching packagesite.txz: 100%6 MiB 6.4MB/s00:01 > >> Processing entries: 72% > >> pkg: wrong architecture: FreeBSD:13.0:amd64 instead of FreeBSD:13:amd64 > >> pkg: repository FreeBSD contains packages with wrong ABI: > >> FreeBSD:13.0:amd64 > >> Processing entries: 100% > >> Unable to update repository FreeBSD > >> Error updating repositories! > > > > Ran into this very same problem today too. > > Just learned on #freebsd that the repos are temporarily borked and > > people are working hard to fix it. > > Any workarounds in the meantime? This must affect a lot of people, > including those who use 12-: > > pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64 > pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:12.0:amd64 Still broken for me on 12.1. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pkg repository is broken...
On Monday, 2 March 2020 at 17:58:01 +, marco wrote: > On Sun, Mar 01, 2020 at 04:50:59PM -0500, you (Brennan Vincent) sent the > following to [freebsd-current] : >> Apparently something has its ABI erroneously listed as FreeBSD:13.0:amd64 >> instead of FreeBSD:13:amd64. >> >> ``` >> $ sudo pkg update -f >> Updating FreeBSD repository catalogue... >> Fetching meta.conf: 100%163 B 0.2kB/s00:01 >> Fetching packagesite.txz: 100%6 MiB 6.4MB/s00:01 >> Processing entries: 72% >> pkg: wrong architecture: FreeBSD:13.0:amd64 instead of FreeBSD:13:amd64 >> pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:13.0:amd64 >> Processing entries: 100% >> Unable to update repository FreeBSD >> Error updating repositories! > > Ran into this very same problem today too. > Just learned on #freebsd that the repos are temporarily borked and > people are working hard to fix it. Any workarounds in the meantime? This must affect a lot of people, including those who use 12-: pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64 pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:12.0:amd64 Greg -- Sent from my desktop computer. Finger g...@freebsd.org for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA signature.asc Description: PGP signature
