Opened 17 months ago

Closed 16 months ago

Last modified 10 months ago

#2248 closed enhancement (fixed)

Changes to debian download page

Reported by: anonymous maybe Owned by: slumlord
Priority: minor Milestone: undecided
Component: www/i2p Version: 0.9.34
Keywords: Cc:
Parent Tickets: Sensitive: no

Description (last modified by anonymous maybe)

This page looks horrible, and need to be tidy and upgraded/easy to explain

https://geti2p.net/en/download/debian#debian

the text should be at least:

Currently supported architectures include amd64, i386, armel, armhf (for Raspbian).

Note: copy/paste the commands and press Enter, it uses "sudo". if you dont use "sudo" then remove it from the command after login with "su". e.g: 

"su
apt install x package (copy/paste the command without sudo)" 


1- make sure that "apt-transport-https" and "curl" are installed: 

"sudo apt update
sudo apt install apt-transport-https curl"

2- add i2p repositories: (it will be added to /etc/apt/sources.list.d )

Note: to make sure which distro is stable and when its end of life please visit [https://wiki.debian.org/LTS/ Debian LTS]

For Stretch (Stable)

echo -e "deb https://deb.i2p2.de/ stretch main\\ndeb-src https://deb.i2p2.de/ stretch main" | sudo tee /etc/apt/sources.list.d/i2p.list > /dev/null

For Jessie (old-stable)

echo -e "deb https://deb.i2p2.de/ jessie main\\ndeb-src https://deb.i2p2.de/ jessie main" | sudo tee /etc/apt/sources.list.d/i2p.list > /dev/null

For Wheezy (obsolete)

echo -e "deb https://deb.i2p2.de/ wheezy main\\ndeb-src https://deb.i2p2.de/ wheezy main" | sudo tee /etc/apt/sources.list.d/i2p.list > /dev/null

Note: If by any chance you are running debian sid (testing), then you can install I2P directly from Debian main repos:

sudo apt install i2p

3- Download the key used to sign the repository and add it to apt: (this will download the key to home folder)

curl -o i2p-debian-repo.key.asc https://geti2p.net/_static/i2p-debian-repo.key.asc

4- Check fingerprints/owners without importing anything:

gpg -n --import --import-options import-show i2p-debian-repo.key.asc


5- If it looks good add it to APT's Keyring:

sudo apt-key add i2p-debian-repo.key.asc

6- Update Packages and Notify your package manager of the new repository

sudo apt update

7- You are now ready to install I2P! Installing the i2p-keyring package will ensure that you receive updates to the repository's GPG key:

sudo apt install i2p i2p-keyring

After the installation process completes you can move on to the next part of starting I2P and configuring it for your system.

These commands wont be exist without the referral to whonix-i2p

https://github.com/mutedstorm/Whonix-I2P

Subtickets

Change History (23)

comment:1 Changed 17 months ago by anonymous maybe

Description: modified (diff)

comment:2 Changed 17 months ago by slumlord

Would you care to explain your proposed changes?

comment:3 Changed 17 months ago by anonymous maybe

Its general question which i don't understand how to explain or which part you mean.But i will discuss the main differences:

1- i make it clear that our commands under sudo and if the user doesn't use them then that's fine as well and i have explained how to make that work. as in the current i2p debian download page is mixed between two commands e.g:

the command here mentioned without using sudo

Download the key used to sign the repository and add it to apt:
    apt-key add i2p-debian-repo.key.asc

the command mentioned here with sudo

 After the installation process completes you can move on to the next part of starting I2P and configuring it for your system.

Note: If the https address does not work, either:

    sudo apt-get install apt-transport-https

so that makes a confusion for the user and also one of the commands will not work directly as copy/paste without differentiate the commands which will work under su or sudo.

2- Debian by default doesn't install apt-transport-https , so making it in the last step is not really helping. because as the user will add i2p https repos in the beginning and then run "apt update" it will for sure not work for him as apt-transport-https not there in the first place. so instead i make at the top of the list

3- i added curl to the equation as it make the user just copy/paste the command and pressing Enter without to care on how to save the PGP from the link presented in the current i2p instructions? where to save it? avoiding the mistake of running "apt-key add i2p-debian-repo.key.asc" not in the same path of where he saved the PGP …etc and this all can happen by new users. so curl will solve this by downloading it by default on /home and he can run " apt-key add i2p-debian-repo.key.asc" after that without the need to check where did his browser saved the pgp or any mistake i addressed above …

4- i added "gpg -n —import —import-options import-show i2p-debian-repo.key.asc" command for security/convenient check up before trusting it.

5- Its very important not to encourage users to use an outdated distros + notifying them that their distro is obsolete and as well that i2p team aware its outdated (as the case with wheezy). so thats why i added Debian TLS link.

6- i made i2p repos to be added to apt with one command as this will avoid the user to have more time in doing that manually by multiple steps or even go reading another websites on how to added repos to apt and where to add to them and what path he should address them …etc. instead one command will do all of that for him and no need to make him go here and there to look for anything rather than reading the instructions and copy/paste the commands.

7- since i2p inside official debian sid repos , its very important to make that clear for users who are using debian sid or any debian derivatives who r built on top of debian sid.

i dunno if i have missed any change but thats what i remember.

also it is very important to consider that the new user/comer has very unbelievable basic knowledge on how to use things so instructions should be targeting him and on the same time targeting other skilled users. so automation commands make that happen smoothly.

Last edited 17 months ago by anonymous maybe (previous) (diff)

comment:4 Changed 17 months ago by anonymous maybe

Description: modified (diff)

comment:5 Changed 17 months ago by anonymous maybe

Description: modified (diff)

comment:6 Changed 17 months ago by zzz

Summary: upgrade debian download wikiChanges to debian download page

Changed summary, it's not a wiki

comment:7 Changed 17 months ago by anonymous maybe

Description: modified (diff)

comment:8 Changed 17 months ago by anonymous maybe

Description: modified (diff)

comment:9 Changed 17 months ago by anonymous maybe

Description: modified (diff)

comment:10 Changed 17 months ago by anonymous maybe

Description: modified (diff)

comment:11 in reply to:  6 Changed 17 months ago by anonymous maybe

Replying to zzz:

Changed summary, it's not a wiki

Thanks for addressing that , i changed the needful.

comment:12 Changed 17 months ago by slumlord

anonymous maybe:

I asked you to explain your changes as you saw a chunk of text on our website, gave a chunk of text of your own and neither pointed out what you were changing nor what your reasons for the changes were. Sure, I could sit down and spend some of my time comparing line-by-line your chunk of text vs. our chunk of text. This would be an error-prone process and even after I figure out what exactly your proposed changes are, I would still not have an explanation for them.

I understand and appreciate that you are trying to help but making tickets for things that were intended as discussions, making tickets where you have not provided adequate information and not only have to be prompted for the information which should have been provided from the start but also seem to need explanation as to why such information would be required to determine how to proceed is quite a drain. I strongly recommend and encourage that you make more use of zzz.i2p or i2pforum.i2p to draft/discuss the tickets which you are planning on submitting. I check these forums everyday and would be happy to carry out discussions there prior to adding tickets to our trac. As you mentioned in comment 3, you aren't sure if you recall all of the changes and reasons for the changes that you proposed - this further highlights the need for you to include as much of the relevant information as possible right from the start.


Request for someone who has better familiarity of Debian to comment on anonymous maybe's proposed changes.

comment:13 Changed 17 months ago by slumlord

Note: Also include any updates required for ARM - http://trac.i2p2.i2p/ticket/1999

comment:14 Changed 17 months ago by slumlord

Add a subticket #1999.

comment:15 in reply to:  12 Changed 17 months ago by anonymous maybe

Replying to slumlord:

anonymous maybe:

I asked you to explain your changes as you saw a chunk of text on our website, gave a chunk of text of your own and neither pointed out what you were changing nor what your reasons for the changes were. Sure, I could sit down and spend some of my time comparing line-by-line your chunk of text vs. our chunk of text. This would be an error-prone process and even after I figure out what exactly your proposed changes are, I would still not have an explanation for them.

so what do u think i did in comment number 3 ??? if didnt get what i have wrote in comment number 3 then i dont get what do u want. please ask straight forward questions rather than open/general questions.

I understand and appreciate that you are trying to help but making tickets for things that were intended as discussions, making tickets where you have not provided adequate information and not only have to be prompted for the information which should have been provided from the start but also seem to need explanation as to why such information would be required to determine how to proceed is quite a drain. I strongly recommend and encourage that you make more use of zzz.i2p or i2pforum.i2p to draft/discuss the tickets which you are planning on submitting. I check these forums everyday and would be happy to carry out discussions there prior to adding tickets to our trac.

i asked zzz on irc , and he told me to submit it here. please check first which proper place for website text fixations/upgrades then comment on the ticket. also i dont mind using these forums which i will doing that eventually.

As you mentioned in comment 3, you aren't sure if you recall all of the changes and reasons for the changes that you proposed - this further highlights the need for you to include as much of the relevant information as possible right from the start.

i said im not sure because im skeptical on any work that it may contain errors even if i claim thats the complete task. so this doesnt come from doubtness about the work rather than its a work from human which may contain errors even if the human claimed to be a perfect work.

Request for someone who has better familiarity of Debian to comment on anonymous maybe's proposed changes.

hope u give fixed time for this question , as i dont expect someone to read this and to be debian fan and comment on this question for the coming short time. and leaving debian not updated on the website for years is recommended against as this is not a progress way to fix any place inside the website.

comment:16 Changed 17 months ago by slumlord

so what do u think i did in comment number 3 ??? if didnt get what i have wrote in comment number 3 then i dont get what do u want. please ask straight forward questions rather than open/general questions.

I have helpfully attempted to explain the reasons why you should include all relevant information without being prompted for it when you are creating a ticket with proposed changes so that you can keep this in mind for any future tickets as this will help all of us. This is not just about this ticket but any of your future tickets as well.

Please try to always include the following when you are suggesting changes:

  • Line by line changes (with the diff utility if possible)
  • Summary of & reasoning for your changes

If you took the time and effort required to do this, there would be less back-and-forth required - tickets can be acted upon quicker and lead to updates/changes sooner. I am not going to repeat myself, you can take my humble suggestions or you can continue as you are.

I am again reiterating zzz's comment that your posts are difficult to read when you use convenient short-forms such as "u", "ur" etc. Please take the brief amount of time and effort required for the few extra keystrokes.

comment:17 Changed 17 months ago by anonymous maybe

this is a link from outside website describing the changes for faster come up of diffs:

https://www.diffchecker.com/TSDkAFxn

using Trac diff:

-Note: The steps below should be performed with root access (i.e., switching user to root with "su" or by prefixing each command with "sudo").
+Note: copy/paste the commands and press Enter, it uses "sudo". if you dont use "sudo" then remove it from the command after login with "su". e.g: 
+"su
+apt install x package (copy/paste the command without sudo)" 
-1.Add lines like the following to /etc/apt/sources.list.d/i2p.list.
-For Wheezy:
-deb https://deb.i2p2.de/ wheezy main
-deb-src https://deb.i2p2.de/ wheezy main
-For Jessie:
-deb https://deb.i2p2.de/ jessie main
-deb-src https://deb.i2p2.de/ jessie main
-For Stretch (stable):
-deb https://deb.i2p2.de/ stretch main
-deb-src https://deb.i2p2.de/ stretch main
+1.Make sure that "apt-transport-https" and "curl" are installed: 
+"sudo apt update
+sudo apt install apt-transport-https curl"
+2- add i2p repositories: (it will be added to /etc/apt/sources.list.d )
+Note: to make sure which distro is stable and when its end of life please visit [https://wiki.debian.org/LTS/ Debian LTS]
+For Stretch (Stable):
+echo -e "deb https://deb.i2p2.de/ stretch main\\ndeb-src https://deb.i2p2.de/ stretch main" | sudo tee /etc/apt/sources.list.d/i2p.list > /dev/null
+For Jessie (old-stable)
+echo -e "deb https://deb.i2p2.de/ jessie main\\ndeb-src https://deb.i2p2.de/ jessie main" | sudo tee /etc/apt/sources.list.d/i2p.list > /dev/null
+For Wheezy (obsolete)
+echo -e "deb https://deb.i2p2.de/ wheezy main\\ndeb-src https://deb.i2p2.de/ wheezy main" | sudo tee /etc/apt/sources.list.d/i2p.list > /dev/null
+Note: If by any chance you are running debian sid (testing), then you can install I2P directly from Debian main repos:
+sudo apt install i2p
-2.Download the key used to sign the repository and add it to apt:
-apt-key add i2p-debian-repo.key.asc
-Notify your package manager of the new repository by entering
-apt-get update
- This command will retrieve the latest list of software from every repository enabled on your system, including the I2P repository added in step 1.
+3- Download the key used to sign the repository and add it to apt: (this will download the key to home folder)
+curl -o i2p-debian-repo.key.asc https://geti2p.net/_static/i2p-debian-repo.key.asc
+4- Check fingerprints/owners without importing anything:
+gpg -n --import --import-options import-show i2p-debian-repo.key.asc
+5- If it looks good add it to APT's Keyring:
+sudo apt-key add i2p-debian-repo.key.asc
+6- Update Packages and Notify your package manager of the new repository
+sudo apt update
-Note: If the https address does not work, either:
-1.sudo apt-get install apt-transport-https
-2.Change the repository address to http://deb.i2p2.no/ 

please refer to comment number 3 for the reasons.

happy to hear more suggestions

comment:18 Changed 17 months ago by slumlord

Thank you.

I have not heard from anyone else so I will review the instructions myself in a Debian VM before accepting the changes.

I will update this ticket by 10th July 2018.

comment:19 Changed 16 months ago by slumlord

Sorry for the delay, I had hardware-related issues to sort out.

I had asked Sadie if she could test the changes and update this ticket but it seems like she was not able to do so.

I am upgrading a Debian VM currently. I will test the changes and update this ticket shortly.

comment:20 Changed 16 months ago by slumlord

I have merged in the changes - updates are in 8102f9427df9d17032fc6fe5ecf9652c6841646b with slight tweaks to formatting after.

—-

A few notes:

  • I have chosen to keep the simpler style of showing which lines are to be added instead of the more complicated echo ... | tee ... > /dev/null line which would be more difficult for users to understand. Users shouldn't be expected to run lines that they don't understand, especially not when working as root.
  • Fixed the inconsistencies with usage/non-usage of sudo

Thank you, anonymous maybe

comment:21 Changed 16 months ago by slumlord

Status: newtesting

comment:22 Changed 16 months ago by slumlord

Resolution: fixed
Status: testingclosed

Seeing no further comments, I am closing this ticket.

comment:23 Changed 10 months ago by slumlord

Remove a subticket #1999.

Note: See TracTickets for help on using tickets.