Ticket #1548 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

Test that adding a repository actually works

Reported by: wendy_hung Owned by: tick
Priority: highest Milestone: Om2008.9
Component: Installer Version:
Severity: critical Keywords: must have
Cc: testing@…, marek@… Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: PatchReviewResult:
Reproducible:

Description

Kernel ： 20080705-asu.stable-uImage.bin
Root file system ：20080708-asu.stable-rootfs.jffs2

Steps:
1) launch assassin
2) select repo category
3) no repos to choose from

We want to test if installing community packages actually work.

Expected:
1) launch assassin
2) select repo category
3) select 'Community Repository'
4) press 'INSTALL'
5) Community categories/packages should now be in assassin list
6) select category
7) select a community package (tangoGPS)
8) install tangoGPS
9) tangoGPS should show in launcher
10) launch tangoGPS

Change History

comment:1 Changed 5 years ago by tick

  • Owner changed from tick@… to tick
  • Status changed from new to accepted

in progress

comment:2 Changed 5 years ago by will

  • Severity changed from critical to blocker

comment:3 follow-up: ↓ 8 Changed 5 years ago by tick

  • Status changed from accepted to closed
  • Resolution set to invalid

community-repository had been put into image

Therefore this test scenario will not happened.

You will see community-repository's stuff by default now.

comment:4 Changed 5 years ago by will

  • Status changed from closed to reopened
  • Resolution invalid deleted

comment:5 Changed 5 years ago by will

  • Keywords must have added
  • Status changed from reopened to in_testing

I don't know why it is invalid.
we would still like to test this :)
re-opening and forwarding to testing.

comment:6 Changed 5 years ago by will

just wondering.
what happens when user wants to add a third party repository, that includes packages contained in a DIFFERENT category then the ones we list by default? Will the new category be added to our list?

comment:7 Changed 5 years ago by tick

as long as you can see the comic-reader
that means you can see pkgs in community-repos
:)

comment:8 in reply to: ↑ 3 Changed 5 years ago by will

Replying to tick:

community-repository had been put into image
Therefore this test scenario will not happened.
You will see community-repository's stuff by default now.

Actually, what is supposed to be in the community repository?
I do not see any extra packages besides the comic-reader.
Is that the only one??

comment:10 Changed 5 years ago by will

  • Status changed from in_testing to assigned

Let's put this in testing when we have some repositories up and running for us to install as a package.
Can we set up something real quick to test this right away?

comment:11 Changed 5 years ago by regina_kim

  • Severity changed from blocker to critical

comment:12 Changed 5 years ago by tick

  • Status changed from assigned to in_testing
  1. remove community-repository from Installer
  2. check if comic-reader is still there. (NO)
  3. Install community-repository back
  4. check if comic-read comes back (Yes)
  5. Installer comic-reader

comment:13 Changed 5 years ago by wendy_hung

Tested with the image below:

kernel:20080807-asu.stable-uImage.bin
root file system:20080807-asu.stable-rootfs.jffs2

Still can't get into the repository, need the password to connect.
Will test that later.

comment:14 Changed 5 years ago by will

  • Milestone changed from Om2008.8 to Om2008.9

Let's take this serious.
We are offering people to create their own repository to add as a package to Metaverse.
We can:

[1] Test if this works ourselves and debug if necessary
[2] Wait until someone reports it

The difference is in the quality.
Can we set up a repository, create a package and test it?


comment:15 Changed 5 years ago by wendy_hung

  • Status changed from in_testing to closed
  • Resolution set to fixed

tested with the image below:
kernel: Om2008.8-gta02-20080903.uImage.bin
rootfs: Om2008.8-gta02-20080904.rootfs.jffs2

The repository package can be reinstall again now, after uninstall community repository package the small packages like comic-reader will also disappear. Go to Install categories-Repos you can install the Community Repository package back.

The only thing that I'm not sure is how we can recognize the packages were from community or default by openmoko.

But this ticket has been solved, thank you tick. :)

Note: See TracTickets for help on using tickets.