Re: [Mono-list] Repository problem (Mono-devel-list Digest, Vol 154, Issue 25)
Jo Shields <[email protected]> Tue, 27 Feb 2018 08:17:35 -0500
| Newsgroups | gmane.comp.gnome.mono.devel |
|---|---|
| Message-ID | <[email protected]> |
--===============6363384903311260289== Content-Type: multipart/alternative; boundary=Apple-Mail-20521F17-84AA-4EAC-A639-C434B01D2BA2 Content-Transfer-Encoding: 7bit --Apple-Mail-20521F17-84AA-4EAC-A639-C434B01D2BA2 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable The warning is unfixable with the repository management software we use on t= he server. Sent from my iPhone > On 27 Feb 2018, at 07:46, Guy <[email protected]> wrote: >=20 > Many thanks for taking the time to answer! And sorry for not having read t= hat part of the manual. Your suggestion in deed this solves the "untrusted s= ource" problem. >=20 > However, during apt-get update I now get this warning instead: > W: Conflicting distribution: http://download.mono-project.com/repo/debian w= heezy/snapshots/4.2.3 InRelease (expected wheezy/snapshots/4.2.3 but got whe= ezy) >=20 > The wrong deb line I used before can be found on different internet sites a= s a "remedy" for the conflicting distribution warning. That might explai= n how that wrong line way found its into the instructions I got. >=20 > Am I right that the "conflicting distribution" warning would need to be fi= xed on the repo server? Though I can live with the warning message, a fix wo= uld be nice, if ever possible. >=20 > Thanks >=20 > Guy >=20 >=20 >> On 26/02/2018 20:34, Jo Shields wrote: >> The instructions on http://www.mono-project.com/docs/getting-started/inst= all/linux/#accessing-older-releases say "If for some reason you want to pin a= n older version of Mono rather than updating to the latest, you can modify t= he Debian repository to =E2=80=9Cwheezy/snapshots/X.XX.X=E2=80=9D instead of= =E2=80=9Cwheezy=E2=80=9D. For example, =E2=80=9Cwheezy/snapshots/3.10.0=E2=80= =9D will lock you to that version." >>=20 >> Hence: >> deb http://download.mono-project.com/repo/debian wheezy/snapshots/4.2.3 m= ain >>=20 >> Just like it says in the instructions. I'm not sure where you got your in= structions from, but the formatting of spaces and slashes matters, and was w= rong in your instructions. >>=20 >>> On 23/02/18 12:28, guy wrote: >>> Thanks for the answer, Jimmy, I know that the repo you indicated works f= ine.=20 >>>=20 >>> However, I specifically need snapshot 4.2.3 for Wheezy.=20 >>>=20 >>> Anyone willing to try / to solve the problem on the repo server?=20 >>>=20 >>> Guy=20 >>>=20 >>>=20 >>>> On 23.02.2018 17:02, Jimmy Tang wrote:=20 >>>> Hi Guy,=20 >>>>=20 >>>> You may try the instructions at http://www.mono-project.com/download/st= able/#download-lin-debian=20 >>>>=20 >>>> I just tested that the URL "http://download.mono-project.com/repo/debia= n wheezy main" works for me=20 >>>>=20 >>>> On Fri, Feb 23, 2018 at 8:48 AM, Guy <[email protected] <mailto:develop= @faert.net>> wrote:=20 >>>>=20 >>>> Hm, no one likes to answer my answer below??=20 >>>>=20 >>>> Then the same question asked differently: What is the correct line=20= >>>> for adding wheezy snapshot 4.2.3 to my /etc/apt/sources.list?=20 >>>>=20 >>>> I haven't found a way around the problem of the missing repo files=20= >>>> yet.=20 >>>>=20 >>>> Guy=20 >>>>=20 >>>>=20 >>>> __________________________________________________________________=20= >>>>=20 >>>>=20 >>>>=20 >>>> This thread originally had been started on the packagers list, but=20= >>>> I was told to move to this place.=20 >>>>=20 >>>> Jo, the verification that you made probably referred to a=20 >>>> different directory. I was told to=20 >>>>=20 >>>> sudo add-apt-repository "deb http://download.mono-project.com/rep= o/debian=20 >>>> <http://download.mono-project.com/repo/debian> wheezy/snapshots=20 >>>> 4.2.3/main"=20 >>>>=20 >>>> And yes, I also added the GPG key and called apt-get update.=20 >>>>=20 >>>> However, I get messages related to=EF=BF=BD "untrusted source" and "= cannot=20 >>>> be authenticated".=20 >>>>=20 >>>> As far as I observed, the add-apt-repository command from above=20 >>>> makes my system access=20 >>>> http://download.mono-project.com/repo/debian/dists/wheezy/snapshots= /4.2.3/main/binary-amd64/ >>>> <http://download.mono-project.com/repo/debian/dists/wheezy/snapshot= s/4.2.3/main/binary-amd64/> >>>> and there, some things are missing:=20 >>>> - The file Release doesn't contain the hashes of Release itself,=20= >>>> nor those of Packages and Packages.gz=20 >>>> - Release.gpg is missing=20 >>>>=20 >>>> Now, what's wrong?=20 >>>> - Does the add-apt-repository command point to the wrong location?=20= >>>> - Or is there a problem on the server?=20 >>>>=20 >>>> Thank you in advance!=20 >>>>=20 >>>> Guy=20 >>>>=20 >>>>=20 >>>>=20 >>>>> On 02.02.2018 21:26, Jo Shields wrote:=20 >>>>> Yeah. Or Gitter.=20 >>>>>=20 >>>>> As for the issue at hand, I don't see a problem?=20 >>>>>=20 >>>>> directhex@origin-download:/srv/www/mono/repo/debian/dists$ gpg=20 >>>>> --verify wheezy/snapshots/4.2.3/Release.gpg=20 >>>>> wheezy/snapshots/4.2.3/Release=20 >>>>> gpg: Signature made Mon 13 Jun 2016 10:26:19 AM UTC using RSA key=20= >>>>> ID D3D831EF=20 >>>>> directhex@origin-download:/srv/www/mono/repo/debian/dists$ grep=20= >>>>> binary-amd64/Packages.gz wheezy/snapshots/4.2.3/Release=20 >>>>> 6208b41daa29eb86cad4b1b463457f49 56477 main/binary-amd64/Packages.= gz=20 >>>>> 3b150372db6f7726d5084f260123fdb949af0dae 56477=20 >>>>> main/binary-amd64/Packages.gz=20 >>>>> 4a96f46b972662fbb942306f6bbc15624456f3da2c4e44632628522f9292f83c=20= >>>>> 56477 main/binary-amd64/Packages.gz=20 >>>>> directhex@origin-download:/srv/www/mono/repo/debian/dists$ md5sum=20= >>>>> wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz=20 >>>>> 6208b41daa29eb86cad4b1b463457f49=20 >>>>> wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz=20 >>>>> directhex@origin-download:/srv/www/mono/repo/debian/dists$=20 >>>>> sha1sum wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz=20 >>>>> 3b150372db6f7726d5084f260123fdb949af0dae=20 >>>>> wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz=20 >>>>> directhex@origin-download:/srv/www/mono/repo/debian/dists$=20 >>>>> sha256sum wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz=20 >>>>> 4a96f46b972662fbb942306f6bbc15624456f3da2c4e44632628522f9292f83c=20= >>>>> wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz=20 >>>>>=20 >>>>> Are you sure apt trusts the GPG key? Use:=20 >>>>> apt-key adv --keyserver hkp://keyserver.ubuntu.com=20 >>>>> <http://keyserver.ubuntu.com>:80--recv-keys=20 >>>>> 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF=20 >>>>>=20 >>>>> Sent from Outlook <http://aka.ms/weboutlook>=20 >>>>>=20 >>>>> ------------------------------------------------------------------= ------=20 >>>>> *From:* Alexander K=EF=BF=BDplinger=20 >>>>> *Sent:* 02 February 2018 15:18=20 >>>>> *To:* Guy=20 >>>>> *Cc:* Jo Shields; [email protected]=20 >>>>> <mailto:[email protected]>=20 >>>>> *Subject:* Re: [Mono-list] Repository problem=20 >>>>> I added Jo in CC who is our Linux packaging expert.=20 >>>>>=20 >>>>> @Jo: should we direct users to the mono-devel list instead?=20 >>>>>=20 >>>>> - Alex=20 >>>>>=20 >>>>> > On 2 Feb 2018, at 10:30, Guy <[email protected]>=20 >>>>> <mailto:[email protected]> wrote:=20 >>>>> >=20 >>>>> > Hello list members,=20 >>>>> >=20 >>>>> > There's a problem with the repository for Debian Wheezy. I=20 >>>>> reported that problem on the mono-packagers-list a few days ago=20= >>>>> (see below) but I didn't get an answer. It looks tome as if that=20= >>>>> list is not followed by any packager any longer.=20 >>>>> >=20 >>>>> > What would be the right place for reporting the problem?=20 >>>>> >=20 >>>>> > Kind regards=20 >>>>> >=20 >>>>> > Guy=20 >>>>> >=20 >>>>> >=20 >>>>> > ___________________________________________________=20 >>>>> >=20 >>>>> >=20 >>>>> > Hello everybody,=20 >>>>> >=20 >>>>> > I hope this is the right list for a problem I have. When trying=20= >>>>> to install Mono from repo=20 >>>>> https://na01.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F%2Fd= ownload.mono-project.com%2Frepo%2Fubuntu&data=3D02%7C01%7Calkpli%40microsoft= .com%7C0169e9678e7f4a8b799208d56a1fac9f%7Cee3303d7fb734b0c8589bcd847f1c277%7= C1%7C0%7C636531606648190055&sdata=3DmUjiKDza47GUhS0sTEp9knpVUQV6KgX1tYLT7kNn= GG4%3D&reserved=3D0 >>>>> <https://na01.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F%2= Fdownload.mono-project.com%2Frepo%2Fubuntu&data=3D02%7C01%7Calkpli%40microso= ft.com%7C0169e9678e7f4a8b799208d56a1fac9f%7Cee3303d7fb734b0c8589bcd847f1c277= %7C1%7C0%7C636531606648190055&sdata=3DmUjiKDza47GUhS0sTEp9knpVUQV6KgX1tYLT7k= NnGG4%3D&reserved=3D0> >>>>> for Wheezy I get error messages related to "untrusted source" and=20= >>>>> "cannot be authenticated".=20 >>>>> >=20 >>>>> > The problem seems to be located in=20 >>>>> >=20 >>>>> https://na01.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F%2Fd= ownload.mono-project.com%2Frepo%2Fdebian%2Fdists%2Fwheezy%2Fsnapshots%2F4.2.= 3%2Fmain%2Fbinary-amd64%2F&data=3D02%7C01%7Calkpli%40microsoft.com%7C0169e96= 78e7f4a8b799208d56a1fac9f%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C63653= 1606648190055&sdata=3D%2BU%2BdUMQyqWvUVdfdEqucRGhCrmw0ItB5nLeoQbbtmRs%3D&res= erved=3D0 >>>>> <https://na01.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F%2= Fdownload.mono-project.com%2Frepo%2Fdebian%2Fdists%2Fwheezy%2Fsnapshots%2F4.= 2.3%2Fmain%2Fbinary-amd64%2F&data=3D02%7C01%7Calkpli%40microsoft.com%7C0169e= 9678e7f4a8b799208d56a1fac9f%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636= 531606648190055&sdata=3D%2BU%2BdUMQyqWvUVdfdEqucRGhCrmw0ItB5nLeoQbbtmRs%3D&r= eserved=3D0> >>>>>=20 >>>>> > where:=20 >>>>> > - The file Release doesn't contain the hashes of Release=20 >>>>> itself, nor those of Packages and Packages.gz=20 >>>>> > - Release.gpg has not been generated=20 >>>>> >=20 >>>>> > Could you please check?=20 >>>>> >=20 >>>>> > Many thanks in advance!=20 >>>>> >=20 >>>>> > Guy=20 >>>>> > _______________________________________________=20 >>>>> > Mono-list maillist=EF=BF=BD - [email protected]=20 >>>>> <mailto:[email protected]>=20 >>>>> >=20 >>>>> https://na01.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F%2Fl= ists.dot.net%2Fmailman%2Flistinfo%2Fmono-list&data=3D02%7C01%7Calkpli%40micr= osoft.com%7C0169e9678e7f4a8b799208d56a1fac9f%7Cee3303d7fb734b0c8589bcd847f1c= 277%7C1%7C0%7C636531606648190055&sdata=3DK%2Fs%2FJAKW5xLT7zYLGXY9Gi8LSV5fO%2= BYpB8%2FY4HORylQ%3D&reserved=3D0 >>>>> <https://na01.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F%2= Flists.dot.net%2Fmailman%2Flistinfo%2Fmono-list&data=3D02%7C01%7Calkpli%40mi= crosoft.com%7C0169e9678e7f4a8b799208d56a1fac9f%7Cee3303d7fb734b0c8589bcd847f= 1c277%7C1%7C0%7C636531606648190055&sdata=3DK%2Fs%2FJAKW5xLT7zYLGXY9Gi8LSV5fO= %2BYpB8%2FY4HORylQ%3D&reserved=3D0> >>>>>=20 >>>>=20 >>>>=20 >>>> _______________________________________________=20 >>>> Mono-devel-list mailing list=20 >>>> [email protected] <mailto:[email protected]= >=20 >>>> http://lists.dot.net/mailman/listinfo/mono-devel-list=20 >>>> <http://lists.dot.net/mailman/listinfo/mono-devel-list>=20 >>>>=20 >>>>=20 >>>=20 >>> -------------- next part --------------=20 >>> An HTML attachment was scrubbed...=20 >>> URL: <http://lists.dot.net/pipermail/mono-devel-list/attachments/2018022= 3/3241bfe7/attachment.html> >>>=20 >>=20 >=20 --Apple-Mail-20521F17-84AA-4EAC-A639-C434B01D2BA2 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D= utf-8"></head><body dir=3D"auto">The warning is unfixable with the repositor= y management software we use on the server.<br><br><div id=3D"AppleMailSigna= ture">Sent from my iPhone</div><div><br>On 27 Feb 2018, at 07:46, Guy <<a= href=3D"mailto:[email protected]">[email protected]</a>> wrote:<br><br><= /div><blockquote type=3D"cite"><div> =20 <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8"= > =20 =20 <p>Many thanks for taking the time to answer! And sorry for not having read that part of the manual. Your suggestion in deed this solves the "untrusted source" problem.</p> <p>However, during apt-get update I now get this warning instead:<br> </p> W: Conflicting distribution: <a class=3D"moz-txt-link-freetext" href=3D"http://download.mono-project.= com/repo/debian">http://download.mono-project.com/repo/debian</a> wheezy/sna= pshots/4.2.3 InRelease (expected wheezy/snapshots/4.2.3 but got wheezy)<br> <br> The wrong deb line I used before can be found on different internet sites as a "remedy" for the conflicting distribution warning. That might explain how that wrong line way found its into the instructions I got.<br> <br> Am I right that the "conflicting distribution" warning would need to be fixed on the repo server? Though I can live with the warning message, a fix would be nice, if ever possible.<br> <br> Thanks<br> <br> Guy<br> <br> <br> <div class=3D"moz-cite-prefix">On 26/02/2018 20:34, Jo Shields wrote:<br= > </div> <blockquote type=3D"cite" cite=3D"mid:6a234368-a168-f169-ab9f-7015d5d590= [email protected]"> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-= 8"> <p>The instructions on <a class=3D"moz-txt-link-freetext" href=3D"http://www.mono-project.c= om/docs/getting-started/install/linux/#accessing-older-releases" moz-do-not-= send=3D"true">http://www.mono-project.com/docs/getting-started/install/linux= /#accessing-older-releases</a> say <span style=3D"color: rgb(34, 34, 34); font-family: "Helvetica Neue", Helvetica, Helvetica, Arial, sans-serif; font-size: 16px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">"If for some reason you want to pin an older version of Mono rather than updating to the latest, you can modify the Debian repository to =E2=80=9Cwheezy/snapshots/X.XX.X=E2= =80=9D instead of =E2=80=9Cwheezy=E2=80=9D. For example, =E2=80=9Cwheezy/= snapshots/3.10.0=E2=80=9D will lock you to that version."</span></p> <p>Hence:<br> </p> <p>deb <a class=3D"moz-txt-link-freetext" href=3D"http://download.mono= -project.com/repo/debian" moz-do-not-send=3D"true">http://download.mono-proj= ect.com/repo/debian</a> wheezy/snapshots/4.2.3 main</p> <p>Just like it says in the instructions. I'm not sure where you got your instructions from, but the formatting of spaces and slashes matters, and was wrong in your instructions.<br> </p> <br> <div class=3D"moz-cite-prefix">On 23/02/18 12:28, guy wrote:<br> </div> <blockquote type=3D"cite" cite=3D"mid:3779305b-ea9c-6f12-28b9-ad9f2a93= [email protected]">Thanks for the answer, Jimmy, I know that the repo you indicated works fine. <br> <br> However, I specifically need snapshot 4.2.3 for Wheezy. <br> <br> Anyone willing to try / to solve the problem on the repo server? <br> <br> Guy <br> <br> <br> On 23.02.2018 17:02, Jimmy Tang wrote: <br> <blockquote type=3D"cite">Hi Guy, <br> <br> You may try the instructions at <a class=3D"moz-txt-link-freetext"= href=3D"http://www.mono-project.com/download/stable/#download-lin-debian" m= oz-do-not-send=3D"true">http://www.mono-project.com/download/stable/#downloa= d-lin-debian</a> <br> <br> I just tested that the URL <a class=3D"moz-txt-link-rfc2396E" href= =3D"http://download.mono-project.com/repo/debianwheezymain" moz-do-not-send=3D= "true">"http://download.mono-project.com/repo/debian wheezy main"</a> works for me <br> <br> On Fri, Feb 23, 2018 at 8:48 AM, Guy <<a class=3D"moz-txt-link-= abbreviated" href=3D"mailto:[email protected]" moz-do-not-send=3D"true">deve= [email protected]</a> <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:[email protected]= t" moz-do-not-send=3D"true"><mailto:[email protected]></a>> wrote: <br> <br> Hm, no one likes to answer my answer below?? <b= r> <br> Then the same question asked differently: What i= s the correct line <br> for adding wheezy snapshot 4.2.3 to my /etc/apt/sources.list? <br> <br> I haven't found a way around the problem of the= missing repo files <br> yet. <br> <br> Guy <br> <br> <br> __________________________________________________________________= <br> <br> <br> <br> This thread originally had been started on the p= ackagers list, but <br> I was told to move to this place. <br> <br> Jo, the verification that you made probably ref= erred to a <br> different directory. I was told to <br> <br> sudo add-apt-repository "deb <a cla= ss=3D"moz-txt-link-freetext" href=3D"http://download.mono-project.com/repo/d= ebian" moz-do-not-send=3D"true">http://download.mono-project.com/repo/debian= </a> <br> <a class=3D"moz-txt-link-rfc2396E" href=3D"http= ://download.mono-project.com/repo/debian" moz-do-not-send=3D"true"><http:= //download.mono-project.com/repo/debian></a> wheezy/snapshots <br> 4.2.3/main" <br> <br> And yes, I also added the GPG key and called ap= t-get update. <br> <br> However, I get messages related to=EF=BF=BD "un= trusted source" and "cannot <br> be authenticated". <br> <br> As far as I observed, the add-apt-repository co= mmand from above <br> makes my system access <br> <a class=3D"moz-txt-link-freetext" href=3D"http://download.mono-pr= oject.com/repo/debian/dists/wheezy/snapshots/4.2.3/main/binary-amd64/" moz-d= o-not-send=3D"true">http://download.mono-project.com/repo/debian/dists/wheez= y/snapshots/4.2.3/main/binary-amd64/</a><br> <a class=3D"moz-txt-link-rfc2396E" href=3D"http://download.mono-pr= oject.com/repo/debian/dists/wheezy/snapshots/4.2.3/main/binary-amd64/" moz-d= o-not-send=3D"true"><http://download.mono-project.com/repo/debian/dists/w= heezy/snapshots/4.2.3/main/binary-amd64/></a><br> and there, some things are missing: <br> - The file Release doesn't contain the hashes o= f Release itself, <br> nor those of Packages and Packages.gz <br> - Release.gpg is missing <br> <br> Now, what's wrong? <br> - Does the add-apt-repository command point to t= he wrong location? <br> - Or is there a problem on the server? <br> <br> Thank you in advance! <br> <br> Guy <br> <br> <br> <br> On 02.02.2018 21:26, Jo Shields wrote: <br> <blockquote type=3D"cite"> Yeah. Or Gitter. <br>= <br> As for the issue at hand, I don't see a probl= em? <br> <br> directhex@origin-download:/srv/www/mono/repo/debian/dists$ gpg <br> --verify wheezy/snapshots/4.2.3/Release.gpg <= br> wheezy/snapshots/4.2.3/Release <br> gpg: Signature made Mon 13 Jun 2016 10:26:19 A= M UTC using RSA key <br> ID D3D831EF <br> directhex@origin-download:/srv/www/mono/repo/debian/dists$ grep <br> binary-amd64/Packages.gz wheezy/snapshots/4.2= .3/Release <br> 6208b41daa29eb86cad4b1b463457f49 56477 main/binary-amd64/Packages.gz <br> 3b150372db6f7726d5084f260123fdb949af0dae 5647= 7 <br> main/binary-amd64/Packages.gz <br> 4a96f46b972662fbb942306f6bbc15624456f3da2c4e44632628522f9292f83c= <br> 56477 main/binary-amd64/Packages.gz <br> directhex@origin-download:/srv/www/mono/repo/debian/dists$ md5sum <br> wheezy/snapshots/4.2.3/main/binary-amd64/Pack= ages.gz <br> 6208b41daa29eb86cad4b1b463457f49 <br> wheezy/snapshots/4.2.3/main/binary-amd64/Pack= ages.gz <br> directhex@origin-download:/srv/www/mono/repo/debian/dists$ <br> sha1sum wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz <br> 3b150372db6f7726d5084f260123fdb949af0dae <br>= wheezy/snapshots/4.2.3/main/binary-amd64/Pack= ages.gz <br> directhex@origin-download:/srv/www/mono/repo/debian/dists$ <br> sha256sum wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz <br> 4a96f46b972662fbb942306f6bbc15624456f3da2c4e44632628522f9292f83c= <br> wheezy/snapshots/4.2.3/main/binary-amd64/Pack= ages.gz <br> <br> Are you sure apt trusts the GPG key? Use: <br= > apt-key adv --keyserver hkp://keyserver.ubunt= u.com <br> <a class=3D"moz-txt-link-rfc2396E" href=3D"ht= tp://keyserver.ubuntu.com" moz-do-not-send=3D"true"><http://keyserver.ubu= ntu.com></a>:80--recv-keys <br> 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF <br>= <br> Sent from Outlook <a class=3D"moz-txt-link-rf= c2396E" href=3D"http://aka.ms/weboutlook" moz-do-not-send=3D"true"><http:= //aka.ms/weboutlook></a> <br> <br> ----------------------------------------------------------------= -------- <br> *From:* Alexander K=EF=BF=BDplinger <br> *Sent:* 02 February 2018 15:18 <br> *To:* Guy <br> *Cc:* Jo Shields; <a class=3D"moz-txt-link-ab= breviated" href=3D"mailto:[email protected]" moz-do-not-send=3D"true">= [email protected]</a> <br> <a class=3D"moz-txt-link-rfc2396E" href=3D"ma= ilto:[email protected]" moz-do-not-send=3D"true"><mailto:mono-list@= lists.dot.net></a> <br> *Subject:* Re: [Mono-list] Repository problem= <br> I added Jo in CC who is our Linux packaging e= xpert. <br> <br> @Jo: should we direct users to the mono-devel= list instead? <br> <br> - Alex <br> <br> > On 2 Feb 2018, at 10:30, Guy <a class=3D= "moz-txt-link-rfc2396E" href=3D"mailto:[email protected]" moz-do-not-send=3D= "true"><[email protected]></a> <br> <a class=3D"moz-txt-link-rfc2396E" href=3D"ma= ilto:[email protected]" moz-do-not-send=3D"true"><mailto:[email protected]= t></a> wrote: <br> > <br> > Hello list members, <br> > <br> > There's a problem with the repository fo= r Debian Wheezy. I <br> reported that problem on the mono-packagers-l= ist a few days ago <br> (see below) but I didn't get an answer. It lo= oks tome as if that <br> list is not followed by any packager any long= er. <br> > <br> > What would be the right place for report= ing the problem? <br> > <br> > Kind regards <br> > <br> > Guy <br> > <br> > <br> > ________________________________________= ___________ <br> > <br> > <br> > Hello everybody, <br> > <br> > I hope this is the right list for a prob= lem I have. When trying <br> to install Mono from repo <br> <a class=3D"moz-txt-link-freetext" href=3D"https://na01.safelink= s.protection.outlook.com/?url=3Dhttp%3A%2F%2Fdownload.mono-project.com%2Frep= o%2Fubuntu&data=3D02%7C01%7Calkpli%40microsoft.com%7C0169e9678e7f4a8b799= 208d56a1fac9f%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C63653160664819005= 5&sdata=3DmUjiKDza47GUhS0sTEp9knpVUQV6KgX1tYLT7kNnGG4%3D&reserved=3D= 0" moz-do-not-send=3D"true">https://na01.safelinks.protection.outlook.com/?u= rl=3Dhttp%3A%2F%2Fdownload.mono-project.com%2Frepo%2Fubuntu&data=3D02%7C= 01%7Calkpli%40microsoft.com%7C0169e9678e7f4a8b799208d56a1fac9f%7Cee3303d7fb7= 34b0c8589bcd847f1c277%7C1%7C0%7C636531606648190055&sdata=3DmUjiKDza47GUh= S0sTEp9knpVUQV6KgX1tYLT7kNnGG4%3D&reserved=3D0</a><br> <a class=3D"moz-txt-link-rfc2396E" href=3D"https://na01.safelink= s.protection.outlook.com/?url=3Dhttp%3A%2F%2Fdownload.mono-project.com%2Frep= o%2Fubuntu&data=3D02%7C01%7Calkpli%40microsoft.com%7C0169e9678e7f4a8b799= 208d56a1fac9f%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C63653160664819005= 5&sdata=3DmUjiKDza47GUhS0sTEp9knpVUQV6KgX1tYLT7kNnGG4%3D&reserved=3D= 0" moz-do-not-send=3D"true"><https://na01.safelinks.protection.outlook.co= m/?url=3Dhttp%3A%2F%2Fdownload.mono-project.com%2Frepo%2Fubuntu&data=3D0= 2%7C01%7Calkpli%40microsoft.com%7C0169e9678e7f4a8b799208d56a1fac9f%7Cee3303d= 7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531606648190055&sdata=3DmUjiKDza4= 7GUhS0sTEp9knpVUQV6KgX1tYLT7kNnGG4%3D&reserved=3D0></a><br> for Wheezy I get error messages related to "u= ntrusted source" and <br> "cannot be authenticated". <br> > <br> > The problem seems to be located in <br> > <br> <a class=3D"moz-txt-link-freetext" href=3D"https://na01.safelink= s.protection.outlook.com/?url=3Dhttp%3A%2F%2Fdownload.mono-project.com%2Frep= o%2Fdebian%2Fdists%2Fwheezy%2Fsnapshots%2F4.2.3%2Fmain%2Fbinary-amd64%2F&= ;data=3D02%7C01%7Calkpli%40microsoft.com%7C0169e9678e7f4a8b799208d56a1fac9f%= 7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531606648190055&sdata=3D= %2BU%2BdUMQyqWvUVdfdEqucRGhCrmw0ItB5nLeoQbbtmRs%3D&reserved=3D0" moz-do-= not-send=3D"true">https://na01.safelinks.protection.outlook.com/?url=3Dhttp%= 3A%2F%2Fdownload.mono-project.com%2Frepo%2Fdebian%2Fdists%2Fwheezy%2Fsnapsho= ts%2F4.2.3%2Fmain%2Fbinary-amd64%2F&data=3D02%7C01%7Calkpli%40microsoft.= com%7C0169e9678e7f4a8b799208d56a1fac9f%7Cee3303d7fb734b0c8589bcd847f1c277%7C= 1%7C0%7C636531606648190055&sdata=3D%2BU%2BdUMQyqWvUVdfdEqucRGhCrmw0ItB5n= LeoQbbtmRs%3D&reserved=3D0</a><br> <a class=3D"moz-txt-link-rfc2396E" href=3D"https://na01.safelink= s.protection.outlook.com/?url=3Dhttp%3A%2F%2Fdownload.mono-project.com%2Frep= o%2Fdebian%2Fdists%2Fwheezy%2Fsnapshots%2F4.2.3%2Fmain%2Fbinary-amd64%2F&= ;data=3D02%7C01%7Calkpli%40microsoft.com%7C0169e9678e7f4a8b799208d56a1fac9f%= 7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531606648190055&sdata=3D= %2BU%2BdUMQyqWvUVdfdEqucRGhCrmw0ItB5nLeoQbbtmRs%3D&reserved=3D0" moz-do-= not-send=3D"true"><https://na01.safelinks.protection.outlook.com/?url=3Dh= ttp%3A%2F%2Fdownload.mono-project.com%2Frepo%2Fdebian%2Fdists%2Fwheezy%2Fsna= pshots%2F4.2.3%2Fmain%2Fbinary-amd64%2F&data=3D02%7C01%7Calkpli%40micros= oft.com%7C0169e9678e7f4a8b799208d56a1fac9f%7Cee3303d7fb734b0c8589bcd847f1c27= 7%7C1%7C0%7C636531606648190055&sdata=3D%2BU%2BdUMQyqWvUVdfdEqucRGhCrmw0I= tB5nLeoQbbtmRs%3D&reserved=3D0></a><br> <br> > where: <br> > - The file Release doesn't contain the h= ashes of Release <br> itself, nor those of Packages and Packages.gz= <br> > - Release.gpg has not been generated <br= > > <br> > Could you please check? <br> > <br> > Many thanks in advance! <br> > <br> > Guy <br> > ________________________________________= _______ <br> > Mono-list maillist=EF=BF=BD - <a class=3D= "moz-txt-link-abbreviated" href=3D"mailto:[email protected]" moz-do-no= t-send=3D"true">[email protected]</a> <br> <a class=3D"moz-txt-link-rfc2396E" href=3D"ma= ilto:[email protected]" moz-do-not-send=3D"true"><mailto:Mono-list@= lists.dot.net></a> <br> > <br> <a class=3D"moz-txt-link-freetext" href=3D"https://na01.safelink= s.protection.outlook.com/?url=3Dhttp%3A%2F%2Flists.dot.net%2Fmailman%2Flisti= nfo%2Fmono-list&data=3D02%7C01%7Calkpli%40microsoft.com%7C0169e9678e7f4a= 8b799208d56a1fac9f%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531606648= 190055&sdata=3DK%2Fs%2FJAKW5xLT7zYLGXY9Gi8LSV5fO%2BYpB8%2FY4HORylQ%3D&am= p;reserved=3D0" moz-do-not-send=3D"true">https://na01.safelinks.protection.o= utlook.com/?url=3Dhttp%3A%2F%2Flists.dot.net%2Fmailman%2Flistinfo%2Fmono-lis= t&data=3D02%7C01%7Calkpli%40microsoft.com%7C0169e9678e7f4a8b799208d56a1f= ac9f%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531606648190055&sda= ta=3DK%2Fs%2FJAKW5xLT7zYLGXY9Gi8LSV5fO%2BYpB8%2FY4HORylQ%3D&reserved=3D0= </a><br> <a class=3D"moz-txt-link-rfc2396E" href=3D"https://na01.safelink= s.protection.outlook.com/?url=3Dhttp%3A%2F%2Flists.dot.net%2Fmailman%2Flisti= nfo%2Fmono-list&data=3D02%7C01%7Calkpli%40microsoft.com%7C0169e9678e7f4a= 8b799208d56a1fac9f%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531606648= 190055&sdata=3DK%2Fs%2FJAKW5xLT7zYLGXY9Gi8LSV5fO%2BYpB8%2FY4HORylQ%3D&am= p;reserved=3D0" moz-do-not-send=3D"true"><https://na01.safelinks.protecti= on.outlook.com/?url=3Dhttp%3A%2F%2Flists.dot.net%2Fmailman%2Flistinfo%2Fmono= -list&data=3D02%7C01%7Calkpli%40microsoft.com%7C0169e9678e7f4a8b799208d5= 6a1fac9f%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531606648190055&= ;sdata=3DK%2Fs%2FJAKW5xLT7zYLGXY9Gi8LSV5fO%2BYpB8%2FY4HORylQ%3D&reserved= =3D0></a><br> <br> </blockquote> <br> <br> _______________________________________________= <br> Mono-devel-list mailing list <br> <a class=3D"moz-txt-link-abbreviated" href=3D"m= ailto:[email protected]" moz-do-not-send=3D"true">Mono-devel-lis= [email protected]</a> <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:Mono-d= [email protected]" moz-do-not-send=3D"true"><mailto:Mono-devel-list= @lists.dot.net></a> <br> <a class=3D"moz-txt-link-freetext" href=3D"http= ://lists.dot.net/mailman/listinfo/mono-devel-list" moz-do-not-send=3D"true">= http://lists.dot.net/mailman/listinfo/mono-devel-list</a> <br> <a class=3D"moz-txt-link-rfc2396E" href=3D"http= ://lists.dot.net/mailman/listinfo/mono-devel-list" moz-do-not-send=3D"true">= <http://lists.dot.net/mailman/listinfo/mono-devel-list></a> <br> <br> <br> </blockquote> <br> -------------- next part -------------- <br> An HTML attachment was scrubbed... <br> URL: <a class=3D"moz-txt-link-rfc2396E" href=3D"http://lists.dot.net/pipe= rmail/mono-devel-list/attachments/20180223/3241bfe7/attachment.html" moz-do-= not-send=3D"true"><http://lists.dot.net/pipermail/mono-devel-list/attachm= ents/20180223/3241bfe7/attachment.html></a><br> <br> </blockquote> <br> </blockquote> <br> =20 </div></blockquote></body></html>= --Apple-Mail-20521F17-84AA-4EAC-A639-C434B01D2BA2-- --===============6363384903311260289== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTW9uby1kZXZl bC1saXN0IG1haWxpbmcgbGlzdApNb25vLWRldmVsLWxpc3RAbGlzdHMuZG90Lm5ldApodHRwOi8v bGlzdHMuZG90Lm5ldC9tYWlsbWFuL2xpc3RpbmZvL21vbm8tZGV2ZWwtbGlzdAo= --===============6363384903311260289==--