Re: [Mono-dev] [Mono-list] Repository problem (Mono-devel-list Digest, Vol 154, Issue 25)

2018-02-27 Thread Guy 

Ok. All my questions have been answered. Many thanks!

Guy


On 2018-02-27 14:17, Jo Shields wrote:
The warning is unfixable with the repository management software we 
use on the server.


Sent from my iPhone

On 27 Feb 2018, at 07:46, Guy > wrote:


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.


However, during apt-get update I now get this warning instead:

W: Conflicting distribution: 
http://download.mono-project.com/repo/debian wheezy/snapshots/4.2.3 
InRelease (expected wheezy/snapshots/4.2.3 but got wheezy)


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.


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.


Thanks

Guy


On 26/02/2018 20:34, Jo Shields wrote:


The instructions on 
http://www.mono-project.com/docs/getting-started/install/linux/#accessing-older-releases 
say "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 “wheezy/snapshots/X.XX.X” instead of “wheezy”. For 
example, “wheezy/snapshots/3.10.0” will lock you to that version."


Hence:

deb http://download.mono-project.com/repo/debian 
wheezy/snapshots/4.2.3 main


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.



On 23/02/18 12:28, guy wrote:
Thanks for the answer, Jimmy, I know that the repo you indicated 
works fine.


However, I specifically need snapshot 4.2.3 for Wheezy.

Anyone willing to try / to solve the problem on the repo server?

Guy


On 23.02.2018 17:02, Jimmy Tang wrote:

Hi Guy,

You may try the instructions at 
http://www.mono-project.com/download/stable/#download-lin-debian


I just tested that the URL 
"http://download.mono-project.com/repo/debian wheezy main" works 
for me


On Fri, Feb 23, 2018 at 8:48 AM, Guy > wrote:


    Hm, no one likes to answer my answer below??

    Then the same question asked differently: What is the correct 
line

    for adding wheezy snapshot 4.2.3 to my /etc/apt/sources.list?

    I haven't found a way around the problem of the missing repo 
files

    yet.

    Guy


__



    This thread originally had been started on the packagers list, 
but

    I was told to move to this place.

    Jo, the verification that you made probably referred to a
    different directory. I was told to

    sudo  add-apt-repository  "deb 
http://download.mono-project.com/repo/debian

 wheezy/snapshots
    4.2.3/main"

    And yes, I also added the GPG key and called apt-get update.

    However, I get messages related to� "untrusted source" and 
"cannot

    be authenticated".

    As far as I observed, the add-apt-repository command from above
    makes my system access
http://download.mono-project.com/repo/debian/dists/wheezy/snapshots/4.2.3/main/binary-amd64/

    and there, some things are missing:
    - The file Release doesn't contain the hashes of Release itself,
    nor those of Packages and Packages.gz
    - Release.gpg is missing

    Now, what's wrong?
    - Does the add-apt-repository command point to the wrong 
location?

    - Or is there a problem on the server?

    Thank you in advance!

    Guy



    On 02.02.2018 21:26, Jo Shields wrote:

    Yeah. Or Gitter.

    As for the issue at hand, I don't see a problem?

directhex@origin-download:/srv/www/mono/repo/debian/dists$ gpg
    --verify wheezy/snapshots/4.2.3/Release.gpg
    wheezy/snapshots/4.2.3/Release
    gpg: Signature made Mon 13 Jun 2016 10:26:19 AM UTC using RSA 
key

    ID D3D831EF
directhex@origin-download:/srv/www/mono/repo/debian/dists$ grep
    binary-amd64/Packages.gz wheezy/snapshots/4.2.3/Release
    6208b41daa29eb86cad4b1b463457f49 56477 
main/binary-amd64/Packages.gz

    3b150372db6f7726d5084f260123fdb949af0dae 56477
    main/binary-amd64/Packages.gz
4a96f46b972662fbb942306f6bbc15624456f3da2c4e44632628522f9292f83c
    56477 main/binary-amd64/Packages.gz
directhex@origin-download:/srv/www/mono/repo/debian/dists$ md5sum
wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
    6208b41daa29eb86cad4b1b463457f49
wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
directhex@origin-download:/srv/www/mono/repo/debian/dists$
    sha1sum wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
   

Re: [Mono-dev] [Mono-list] Repository problem (Mono-devel-list Digest, Vol 154, Issue 25)

2018-02-27 Thread Jo Shields 
The warning is unfixable with the repository management software we use on the 
server.

Sent from my iPhone

> On 27 Feb 2018, at 07:46, Guy  wrote:
> 
> 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.
> 
> However, during apt-get update I now get this warning instead:
> W: Conflicting distribution: http://download.mono-project.com/repo/debian 
> wheezy/snapshots/4.2.3 InRelease (expected wheezy/snapshots/4.2.3 but got 
> wheezy)
> 
> 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.
> 
> 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.
> 
> Thanks
> 
> Guy
> 
> 
>> On 26/02/2018 20:34, Jo Shields wrote:
>> The instructions on 
>> http://www.mono-project.com/docs/getting-started/install/linux/#accessing-older-releases
>>  say "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 
>> “wheezy/snapshots/X.XX.X” instead of “wheezy”. For example, 
>> “wheezy/snapshots/3.10.0” will lock you to that version."
>> 
>> Hence:
>> deb http://download.mono-project.com/repo/debian wheezy/snapshots/4.2.3 main
>> 
>> 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.
>> 
>>> On 23/02/18 12:28, guy wrote:
>>> Thanks for the answer, Jimmy, I know that the repo you indicated works 
>>> fine. 
>>> 
>>> However, I specifically need snapshot 4.2.3 for Wheezy. 
>>> 
>>> Anyone willing to try / to solve the problem on the repo server? 
>>> 
>>> Guy 
>>> 
>>> 
 On 23.02.2018 17:02, Jimmy Tang wrote: 
 Hi Guy, 
 
 You may try the instructions at 
 http://www.mono-project.com/download/stable/#download-lin-debian 
 
 I just tested that the URL "http://download.mono-project.com/repo/debian 
 wheezy main" works for me 
 
 On Fri, Feb 23, 2018 at 8:48 AM, Guy > wrote: 
 
 Hm, no one likes to answer my answer below?? 
 
 Then the same question asked differently: What is the correct line 
 for adding wheezy snapshot 4.2.3 to my /etc/apt/sources.list? 
 
 I haven't found a way around the problem of the missing repo files 
 yet. 
 
 Guy 
 
 
 __ 
 
 
 
 This thread originally had been started on the packagers list, but 
 I was told to move to this place. 
 
 Jo, the verification that you made probably referred to a 
 different directory. I was told to 
 
 sudo  add-apt-repository  "deb 
 http://download.mono-project.com/repo/debian 
  wheezy/snapshots 
 4.2.3/main" 
 
 And yes, I also added the GPG key and called apt-get update. 
 
 However, I get messages related to� "untrusted source" and "cannot 
 be authenticated". 
 
 As far as I observed, the add-apt-repository command from above 
 makes my system access 
 
 http://download.mono-project.com/repo/debian/dists/wheezy/snapshots/4.2.3/main/binary-amd64/
 
 
 and there, some things are missing: 
 - The file Release doesn't contain the hashes of Release itself, 
 nor those of Packages and Packages.gz 
 - Release.gpg is missing 
 
 Now, what's wrong? 
 - Does the add-apt-repository command point to the wrong location? 
 - Or is there a problem on the server? 
 
 Thank you in advance! 
 
 Guy 
 
 
 
> On 02.02.2018 21:26, Jo Shields wrote: 
> Yeah. Or Gitter. 
> 
> As for the issue at hand, I don't see a problem? 
> 
> directhex@origin-download:/srv/www/mono/repo/debian/dists$ gpg 
> --verify wheezy/snapshots/4.2.3/Release.gpg 
> wheezy/snapshots/4.2.3/Release 
> gpg: Signature made Mon 13 Jun 2016 10:26:19 AM UTC using RSA key 
> ID D3D831EF 
> directhex@origin-download:/srv/www/mono/repo/debian/dists$ grep 
> binary-amd64/Packages.gz wheezy/snapshots/4.2.3/Release 
> 6208b41daa29eb86cad4b1b463457f49 56477 main/binary-amd64/Packages.gz 
> 3b150372db6f7726d5084f260123fdb949af0dae 56477 
>

Re: [Mono-dev] [Mono-list] Repository problem (Mono-devel-list Digest, Vol 154, Issue 25)

2018-02-27 Thread Guy 
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.


However, during apt-get update I now get this warning instead:

W: Conflicting distribution: 
http://download.mono-project.com/repo/debian wheezy/snapshots/4.2.3 
InRelease (expected wheezy/snapshots/4.2.3 but got wheezy)


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.


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.


Thanks

Guy


On 26/02/2018 20:34, Jo Shields wrote:


The instructions on 
http://www.mono-project.com/docs/getting-started/install/linux/#accessing-older-releases 
say "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 “wheezy/snapshots/X.XX.X” instead of “wheezy”. For 
example, “wheezy/snapshots/3.10.0” will lock you to that version."


Hence:

deb http://download.mono-project.com/repo/debian 
wheezy/snapshots/4.2.3 main


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.



On 23/02/18 12:28, guy wrote:
Thanks for the answer, Jimmy, I know that the repo you indicated 
works fine.


However, I specifically need snapshot 4.2.3 for Wheezy.

Anyone willing to try / to solve the problem on the repo server?

Guy


On 23.02.2018 17:02, Jimmy Tang wrote:

Hi Guy,

You may try the instructions at 
http://www.mono-project.com/download/stable/#download-lin-debian


I just tested that the URL 
"http://download.mono-project.com/repo/debian wheezy main" works for me


On Fri, Feb 23, 2018 at 8:48 AM, Guy > wrote:


    Hm, no one likes to answer my answer below??

    Then the same question asked differently: What is the correct line
    for adding wheezy snapshot 4.2.3 to my /etc/apt/sources.list?

    I haven't found a way around the problem of the missing repo files
    yet.

    Guy


__



    This thread originally had been started on the packagers list, but
    I was told to move to this place.

    Jo, the verification that you made probably referred to a
    different directory. I was told to

    sudo  add-apt-repository  "deb 
http://download.mono-project.com/repo/debian

 wheezy/snapshots
    4.2.3/main"

    And yes, I also added the GPG key and called apt-get update.

    However, I get messages related to� "untrusted source" and "cannot
    be authenticated".

    As far as I observed, the add-apt-repository command from above
    makes my system access
http://download.mono-project.com/repo/debian/dists/wheezy/snapshots/4.2.3/main/binary-amd64/

    and there, some things are missing:
    - The file Release doesn't contain the hashes of Release itself,
    nor those of Packages and Packages.gz
    - Release.gpg is missing

    Now, what's wrong?
    - Does the add-apt-repository command point to the wrong location?
    - Or is there a problem on the server?

    Thank you in advance!

    Guy



    On 02.02.2018 21:26, Jo Shields wrote:

    Yeah. Or Gitter.

    As for the issue at hand, I don't see a problem?

directhex@origin-download:/srv/www/mono/repo/debian/dists$ gpg
    --verify wheezy/snapshots/4.2.3/Release.gpg
    wheezy/snapshots/4.2.3/Release
    gpg: Signature made Mon 13 Jun 2016 10:26:19 AM UTC using RSA key
    ID D3D831EF
directhex@origin-download:/srv/www/mono/repo/debian/dists$ grep
    binary-amd64/Packages.gz wheezy/snapshots/4.2.3/Release
    6208b41daa29eb86cad4b1b463457f49 56477 
main/binary-amd64/Packages.gz

    3b150372db6f7726d5084f260123fdb949af0dae 56477
    main/binary-amd64/Packages.gz
4a96f46b972662fbb942306f6bbc15624456f3da2c4e44632628522f9292f83c
    56477 main/binary-amd64/Packages.gz
directhex@origin-download:/srv/www/mono/repo/debian/dists$ md5sum
    wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
    6208b41daa29eb86cad4b1b463457f49
    wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
directhex@origin-download:/srv/www/mono/repo/debian/dists$
    sha1sum wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
    3b150372db6f7726d5084f260123fdb949af0dae
    wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
directhex@origin-download:/srv/www/mono/repo/debian/dists$
    sha256sum wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
4a96f46b972662fbb942306f6bbc15624456f3da2c4e44632628522f9292f83c
   

Re: [Mono-dev] [Mono-list] Repository problem (Mono-devel-list Digest, Vol 154, Issue 25)

2018-02-26 Thread Jo Shields 
The instructions on 
http://www.mono-project.com/docs/getting-started/install/linux/#accessing-older-releases 
say "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 
“wheezy/snapshots/X.XX.X” instead of “wheezy”. For example, 
“wheezy/snapshots/3.10.0” will lock you to that version."


Hence:

deb http://download.mono-project.com/repo/debian wheezy/snapshots/4.2.3 main

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.



On 23/02/18 12:28, guy wrote:
Thanks for the answer, Jimmy, I know that the repo you indicated works 
fine.


However, I specifically need snapshot 4.2.3 for Wheezy.

Anyone willing to try / to solve the problem on the repo server?

Guy


On 23.02.2018 17:02, Jimmy Tang wrote:

Hi Guy,

You may try the instructions at 
http://www.mono-project.com/download/stable/#download-lin-debian


I just tested that the URL 
"http://download.mono-project.com/repo/debian wheezy main" works for me


On Fri, Feb 23, 2018 at 8:48 AM, Guy > wrote:


    Hm, no one likes to answer my answer below??

    Then the same question asked differently: What is the correct line
    for adding wheezy snapshot 4.2.3 to my /etc/apt/sources.list?

    I haven't found a way around the problem of the missing repo files
    yet.

    Guy


__



    This thread originally had been started on the packagers list, but
    I was told to move to this place.

    Jo, the verification that you made probably referred to a
    different directory. I was told to

    sudo  add-apt-repository  "deb 
http://download.mono-project.com/repo/debian

     wheezy/snapshots
    4.2.3/main"

    And yes, I also added the GPG key and called apt-get update.

    However, I get messages related to� "untrusted source" and "cannot
    be authenticated".

    As far as I observed, the add-apt-repository command from above
    makes my system access
http://download.mono-project.com/repo/debian/dists/wheezy/snapshots/4.2.3/main/binary-amd64/

    and there, some things are missing:
    - The file Release doesn't contain the hashes of Release itself,
    nor those of Packages and Packages.gz
    - Release.gpg is missing

    Now, what's wrong?
    - Does the add-apt-repository command point to the wrong location?
    - Or is there a problem on the server?

    Thank you in advance!

    Guy



    On 02.02.2018 21:26, Jo Shields wrote:

    Yeah. Or Gitter.

    As for the issue at hand, I don't see a problem?

    directhex@origin-download:/srv/www/mono/repo/debian/dists$ gpg
    --verify wheezy/snapshots/4.2.3/Release.gpg
    wheezy/snapshots/4.2.3/Release
    gpg: Signature made Mon 13 Jun 2016 10:26:19 AM UTC using RSA key
    ID D3D831EF
    directhex@origin-download:/srv/www/mono/repo/debian/dists$ grep
    binary-amd64/Packages.gz wheezy/snapshots/4.2.3/Release
    6208b41daa29eb86cad4b1b463457f49 56477 
main/binary-amd64/Packages.gz

    3b150372db6f7726d5084f260123fdb949af0dae 56477
    main/binary-amd64/Packages.gz
4a96f46b972662fbb942306f6bbc15624456f3da2c4e44632628522f9292f83c
    56477 main/binary-amd64/Packages.gz
    directhex@origin-download:/srv/www/mono/repo/debian/dists$ md5sum
    wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
    6208b41daa29eb86cad4b1b463457f49
    wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
    directhex@origin-download:/srv/www/mono/repo/debian/dists$
    sha1sum wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
    3b150372db6f7726d5084f260123fdb949af0dae
    wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
    directhex@origin-download:/srv/www/mono/repo/debian/dists$
    sha256sum wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
4a96f46b972662fbb942306f6bbc15624456f3da2c4e44632628522f9292f83c
    wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz

    Are you sure apt trusts the GPG key? Use:
    apt-key adv --keyserver hkp://keyserver.ubuntu.com
    :80--recv-keys
    3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF

    Sent from Outlook 

 


    *From:* Alexander K�plinger
    *Sent:* 02 February 2018 15:18
    *To:* Guy
    *Cc:* Jo Shields; mono-l...@lists.dot.net
    
    *Subject:* Re: [Mono-list] Repository problem
    I added Jo in CC who is our Linux packaging expert.

    @Jo: should we direct users to the mono-devel list instead?

    - Alex

    > On 2 Feb 2018, at 10:30, Guy 
     wrote:
    >
    > Hello list

Re: [Mono-dev] [Mono-list] Repository problem

2018-02-23 Thread Jimmy Tang 
Hi Guy,

You may try  the instructions at
http://www.mono-project.com/download/stable/#download-lin-debian

I just tested that the URL "http://download.mono-project.com/repo/debian
wheezy main" works for me

On Fri, Feb 23, 2018 at 8:48 AM, Guy  wrote:

> Hm, no one likes to answer my answer below??
>
> Then the same question asked differently: What is the correct line for
> adding wheezy snapshot 4.2.3 to my /etc/apt/sources.list?
>
> I haven't found a way around the problem of the missing repo files yet.
>
> Guy
>
>
> __
>
>
>
> This thread originally had been started on the packagers list, but I was
> told to move to this place.
>
> Jo, the verification that you made probably referred to a different
> directory. I was told to
>
> sudo add-apt-repository "deb http://download.mono-project.com/repo/debian 
> wheezy/snapshots 4.2.3/main"
>
> And yes, I also added the GPG key and called apt-get update.
>
> However, I get messages related to  "untrusted source" and "cannot be
> authenticated".
>
> As far as I observed, the add-apt-repository command from above makes my
> system access
> http://download.mono-project.com/repo/debian/dists/wheezy/
> snapshots/4.2.3/main/binary-amd64/
> and there, some things are missing:
> - The file Release doesn't contain the hashes of Release itself, nor those
> of Packages and Packages.gz
> - Release.gpg is missing
>
> Now, what's wrong?
> - Does the add-apt-repository command point to the wrong location?
> - Or is there a problem on the server?
>
> Thank you in advance!
>
> Guy
>
>
>
> On 02.02.2018 21:26, Jo Shields wrote:
>
> Yeah. Or Gitter.
>
> As for the issue at hand, I don't see a problem?
>
> directhex@origin-download:/srv/www/mono/repo/debian/dists$ gpg --verify
> wheezy/snapshots/4.2.3/Release.gpg wheezy/snapshots/4.2.3/Release
> gpg: Signature made Mon 13 Jun 2016 10:26:19 AM UTC using RSA key ID
> D3D831EF
> directhex@origin-download:/srv/www/mono/repo/debian/dists$ grep
> binary-amd64/Packages.gz wheezy/snapshots/4.2.3/Release
>  6208b41daa29eb86cad4b1b463457f49 56477 main/binary-amd64/Packages.gz
>  3b150372db6f7726d5084f260123fdb949af0dae 56477
> main/binary-amd64/Packages.gz
>  4a96f46b972662fbb942306f6bbc15624456f3da2c4e44632628522f9292f83c 56477
> main/binary-amd64/Packages.gz
> directhex@origin-download:/srv/www/mono/repo/debian/dists$ md5sum
> wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
> 6208b41daa29eb86cad4b1b463457f49  wheezy/snapshots/4.2.3/main/
> binary-amd64/Packages.gz
> directhex@origin-download:/srv/www/mono/repo/debian/dists$ sha1sum
> wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
> 3b150372db6f7726d5084f260123fdb949af0dae  wheezy/snapshots/4.2.3/main/
> binary-amd64/Packages.gz
> directhex@origin-download:/srv/www/mono/repo/debian/dists$ sha256sum
> wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
> 4a96f46b972662fbb942306f6bbc15624456f3da2c4e44632628522f9292f83c
> wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
>
> Are you sure apt trusts the GPG key? Use:
> apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3
> FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
>
> Sent from Outlook 
> --
> *From:* Alexander Köplinger
> *Sent:* 02 February 2018 15:18
> *To:* Guy
> *Cc:* Jo Shields; mono-l...@lists.dot.net
> *Subject:* Re: [Mono-list] Repository problem
>
> I added Jo in CC who is our Linux packaging expert.
>
> @Jo: should we direct users to the mono-devel list instead?
>
> - Alex
>
> > On 2 Feb 2018, at 10:30, Guy  
> wrote:
> >
> > Hello list members,
> >
> > There's a problem with the repository for Debian Wheezy. I reported that
> problem on the mono-packagers-list a few days ago (see below) but I didn't
> get an answer. It looks tome as if that list is not followed by any
> packager any longer.
> >
> > What would be the right place for reporting the problem?
> >
> > Kind regards
> >
> > Guy
> >
> >
> > ___
> >
> >
> > Hello everybody,
> >
> > I hope this is the right list for a problem I have. When trying to
> install Mono from repo https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fdownload.mono-project.com%2Frepo%2Fubuntu&
> data=02%7C01%7Calkpli%40microsoft.com%7C0169e9678e7f4a8b799208d56a1fac9f%
> 7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531606648190055=
> mUjiKDza47GUhS0sTEp9knpVUQV6KgX1tYLT7kNnGG4%3D=0 for Wheezy I
> get error messages related to "untrusted source" and "cannot be
> authenticated".
> >
> > The problem seems to be located in
> > https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fdownload.mono-project.com%2Frepo%2Fdebian%
> 2Fdists%2Fwheezy%2Fsnapshots%2F4.2.3%2Fmain%2Fbinary-amd64%
> 2F=02%7C01%7Calkpli%40microsoft.com%7C0169e9678e7f4a8b799208d56a1f
> ac9f%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%
>

Re: [Mono-dev] [Mono-list] Repository problem

2018-02-23 Thread Guy 

Hm, no one likes to answer my answer below??

Then the same question asked differently: What is the correct line for 
adding wheezy snapshot 4.2.3 to my /etc/apt/sources.list?


I haven't found a way around the problem of the missing repo files yet.

Guy


__



This thread originally had been started on the packagers list, but I was 
told to move to this place.


Jo, the verification that you made probably referred to a different 
directory. I was told to


sudo  add-apt-repository  "deb http://download.mono-project.com/repo/debian wheezy/snapshots 
4.2.3/main"


And yes, I also added the GPG key and called apt-get update.

However, I get messages related to  "untrusted source" and "cannot be 
authenticated".


As far as I observed, the add-apt-repository command from above makes my 
system access

http://download.mono-project.com/repo/debian/dists/wheezy/snapshots/4.2.3/main/binary-amd64/
and there, some things are missing:
- The file Release doesn't contain the hashes of Release itself, nor 
those of Packages and Packages.gz

- Release.gpg is missing

Now, what's wrong?
- Does the add-apt-repository command point to the wrong location?
- Or is there a problem on the server?

Thank you in advance!

Guy



On 02.02.2018 21:26, Jo Shields wrote:

Yeah. Or Gitter.

As for the issue at hand, I don't see a problem?

directhex@origin-download:/srv/www/mono/repo/debian/dists$ gpg 
--verify wheezy/snapshots/4.2.3/Release.gpg wheezy/snapshots/4.2.3/Release
gpg: Signature made Mon 13 Jun 2016 10:26:19 AM UTC using RSA key ID 
D3D831EF
directhex@origin-download:/srv/www/mono/repo/debian/dists$ grep 
binary-amd64/Packages.gz wheezy/snapshots/4.2.3/Release

 6208b41daa29eb86cad4b1b463457f49 56477 main/binary-amd64/Packages.gz
 3b150372db6f7726d5084f260123fdb949af0dae 56477 
main/binary-amd64/Packages.gz
 4a96f46b972662fbb942306f6bbc15624456f3da2c4e44632628522f9292f83c 
56477 main/binary-amd64/Packages.gz
directhex@origin-download:/srv/www/mono/repo/debian/dists$ md5sum 
wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
6208b41daa29eb86cad4b1b463457f49 
wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
directhex@origin-download:/srv/www/mono/repo/debian/dists$ sha1sum 
wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
3b150372db6f7726d5084f260123fdb949af0dae 
wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
directhex@origin-download:/srv/www/mono/repo/debian/dists$ sha256sum 
wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
4a96f46b972662fbb942306f6bbc15624456f3da2c4e44632628522f9292f83c 
wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz


Are you sure apt trusts the GPG key? Use:
apt-key adv --keyserver hkp://keyserver.ubuntu.com:80--recv-keys 
3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF


Sent from Outlook 


*From:* Alexander Köplinger
*Sent:* 02 February 2018 15:18
*To:* Guy
*Cc:* Jo Shields; mono-l...@lists.dot.net
*Subject:* Re: [Mono-list] Repository problem
I added Jo in CC who is our Linux packaging expert.

@Jo: should we direct users to the mono-devel list instead?

- Alex

> On 2 Feb 2018, at 10:30, Guy  wrote:
>
> Hello list members,
>
> There's a problem with the repository for Debian Wheezy. I reported 
that problem on the mono-packagers-list a few days ago (see below) but 
I didn't get an answer. It looks tome as if that list is not followed 
by any packager any longer.

>
> What would be the right place for reporting the problem?
>
> Kind regards
>
> Guy
>
>
> ___
>
>
> Hello everybody,
>
> I hope this is the right list for a problem I have. When trying to 
install Mono from repo 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdownload.mono-project.com%2Frepo%2Fubuntu=02%7C01%7Calkpli%40microsoft.com%7C0169e9678e7f4a8b799208d56a1fac9f%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531606648190055=mUjiKDza47GUhS0sTEp9knpVUQV6KgX1tYLT7kNnGG4%3D=0 
for Wheezy I get error messages related to "untrusted source" and 
"cannot be authenticated".

>
> The problem seems to be located in
> 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdownload.mono-project.com%2Frepo%2Fdebian%2Fdists%2Fwheezy%2Fsnapshots%2F4.2.3%2Fmain%2Fbinary-amd64%2F=02%7C01%7Calkpli%40microsoft.com%7C0169e9678e7f4a8b799208d56a1fac9f%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531606648190055=%2BU%2BdUMQyqWvUVdfdEqucRGhCrmw0ItB5nLeoQbbtmRs%3D=0 


> where:
> - The file Release doesn't contain the hashes of Release itself, nor 
those of Packages and Packages.gz

> - Release.gpg has not been generated
>
> Could you please check?
>
> Many thanks in advance!
>
> Guy
> ___
> Mono-list maillist  - mono-l...@lists.dot.net
>

Re: [Mono-dev] [Mono-list] Repository problem

2018-02-21 Thread Guy 
This thread originally had been started on the packagers list, but I was 
told to move to this place.


Jo, the verification that you made probably referred to a different 
directory. I was told to


sudo  add-apt-repository  "deb http://download.mono-project.com/repo/debian wheezy/snapshots 
4.2.3/main"


And yes, I also added the GPG key and called apt-get update.

However, I get messages related to  "untrusted source" and "cannot be 
authenticated".


As far as I observed, the add-apt-repository command from above makes my 
system access

http://download.mono-project.com/repo/debian/dists/wheezy/snapshots/4.2.3/main/binary-amd64/
and there, some things are missing:
- The file Release doesn't contain the hashes of Release itself, nor 
those of Packages and Packages.gz

- Release.gpg is missing

Now, what's wrong?
- Does the add-apt-repository command point to the wrong location?
- Or is there a problem on the server?

Thank you in advance!

Guy



On 02.02.2018 21:26, Jo Shields wrote:

Yeah. Or Gitter.

As for the issue at hand, I don't see a problem?

directhex@origin-download:/srv/www/mono/repo/debian/dists$ gpg 
--verify wheezy/snapshots/4.2.3/Release.gpg wheezy/snapshots/4.2.3/Release
gpg: Signature made Mon 13 Jun 2016 10:26:19 AM UTC using RSA key ID 
D3D831EF
directhex@origin-download:/srv/www/mono/repo/debian/dists$ grep 
binary-amd64/Packages.gz wheezy/snapshots/4.2.3/Release

 6208b41daa29eb86cad4b1b463457f49 56477 main/binary-amd64/Packages.gz
 3b150372db6f7726d5084f260123fdb949af0dae 56477 
main/binary-amd64/Packages.gz
 4a96f46b972662fbb942306f6bbc15624456f3da2c4e44632628522f9292f83c 
56477 main/binary-amd64/Packages.gz
directhex@origin-download:/srv/www/mono/repo/debian/dists$ md5sum 
wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
6208b41daa29eb86cad4b1b463457f49 
wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
directhex@origin-download:/srv/www/mono/repo/debian/dists$ sha1sum 
wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
3b150372db6f7726d5084f260123fdb949af0dae 
wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
directhex@origin-download:/srv/www/mono/repo/debian/dists$ sha256sum 
wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz
4a96f46b972662fbb942306f6bbc15624456f3da2c4e44632628522f9292f83c 
wheezy/snapshots/4.2.3/main/binary-amd64/Packages.gz


Are you sure apt trusts the GPG key? Use:
apt-key adv --keyserver hkp://keyserver.ubuntu.com:80--recv-keys 
3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF


Sent from Outlook 


*From:* Alexander Köplinger
*Sent:* 02 February 2018 15:18
*To:* Guy
*Cc:* Jo Shields; mono-l...@lists.dot.net
*Subject:* Re: [Mono-list] Repository problem
I added Jo in CC who is our Linux packaging expert.

@Jo: should we direct users to the mono-devel list instead?

- Alex

> On 2 Feb 2018, at 10:30, Guy  wrote:
>
> Hello list members,
>
> There's a problem with the repository for Debian Wheezy. I reported 
that problem on the mono-packagers-list a few days ago (see below) but 
I didn't get an answer. It looks tome as if that list is not followed 
by any packager any longer.

>
> What would be the right place for reporting the problem?
>
> Kind regards
>
> Guy
>
>
> ___
>
>
> Hello everybody,
>
> I hope this is the right list for a problem I have. When trying to 
install Mono from repo 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdownload.mono-project.com%2Frepo%2Fubuntu=02%7C01%7Calkpli%40microsoft.com%7C0169e9678e7f4a8b799208d56a1fac9f%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531606648190055=mUjiKDza47GUhS0sTEp9knpVUQV6KgX1tYLT7kNnGG4%3D=0 
for Wheezy I get error messages related to "untrusted source" and 
"cannot be authenticated".

>
> The problem seems to be located in
> 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdownload.mono-project.com%2Frepo%2Fdebian%2Fdists%2Fwheezy%2Fsnapshots%2F4.2.3%2Fmain%2Fbinary-amd64%2F=02%7C01%7Calkpli%40microsoft.com%7C0169e9678e7f4a8b799208d56a1fac9f%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531606648190055=%2BU%2BdUMQyqWvUVdfdEqucRGhCrmw0ItB5nLeoQbbtmRs%3D=0 


> where:
> - The file Release doesn't contain the hashes of Release itself, nor 
those of Packages and Packages.gz

> - Release.gpg has not been generated
>
> Could you please check?
>
> Many thanks in advance!
>
> Guy
> ___
> Mono-list maillist  - mono-l...@lists.dot.net
> 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.dot.net%2Fmailman%2Flistinfo%2Fmono-list=02%7C01%7Calkpli%40microsoft.com%7C0169e9678e7f4a8b799208d56a1fac9f%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531606648190055=K%2Fs%2FJAKW5xLT7zYLGXY9Gi8LSV5fO%2BYpB8%2FY4HORylQ%3D=0




___
Mono-devel-list mailing list
Mono-devel-list@lists.dot.net