Bug #1929

2.0 packaging errors

Added by Bob Gobeille about 1 year ago. Updated 10 months ago.

Status:Closed Start date:05/09/2012
Priority:High Due date:
Assignee:Mary Laser % Done:

0%

Category:Package Install
Target version:2.1.0 Estimated time:24.00 hours
Rank:2 Tester:

Description

Hi all,
I seem to have fossy 2.0.0rc1.1 installed and running fine on my
Ubuntu 12.04 laptop, thanks!
But a couple of package oddities, as shown in the screen scrape below.
1) apt-get upgrade appears to work fine, but the 2nd upgrade try
should report back that it is already at the latest version.
2) the fossology-common package cannot be authenticated.
FYI.
Thanks again,
Pete

$ sudo apt-get upgrade fossology
[sudo] password for user:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
fossology-common
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/831 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]?
WARNING: The following packages cannot be authenticated!
fossology-common
Install these packages without verification [y/N]? y
(Reading database ... 368424 files and directories currently installed.)
Preparing to replace fossology-common 2.0.0rc1.1 (using
.../fossology-common_2.0.0rc1.1_amd64.deb) ...
Unpacking replacement fossology-common ...
Processing triggers for man-db ...
Setting up fossology-common (2.0.0rc1.1) ...
  • Running postinstall for common actions***
  • Creating user and group ***
    NOTE: group 'fossy' already exists, good.
    NOTE: user 'fossy' already exists, good.
  • Making sure needed dirs exist with right ownership/permissions ***
    NOTE: Repository already exists at /srv/fossology/repository
    FOSSology postinstall complete, but sure to complete the remaining
    steps in the INSTALL instructions.
    $ sudo apt-get upgrade fossology
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages will be upgraded:
    fossology-common
    1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    Need to get 0 B/831 kB of archives.
    After this operation, 0 B of additional disk space will be used.
    Do you want to continue [Y/n]?
    WARNING: The following packages cannot be authenticated!
    fossology-common
    Install these packages without verification [y/N]? y
    (Reading database ... 368424 files and directories currently installed.)
    Preparing to replace fossology-common 2.0.0rc1.1 (using
    .../fossology-common_2.0.0rc1.1_amd64.deb) ...
    Unpacking replacement fossology-common ...
    Processing triggers for man-db ...
    Setting up fossology-common (2.0.0rc1.1) ...
  • Running postinstall for common actions***
  • Creating user and group ***
    NOTE: group 'fossy' already exists, good.
    NOTE: user 'fossy' already exists, good.
  • Making sure needed dirs exist with right ownership/permissions ***
    NOTE: Repository already exists at /srv/fossology/repository
    FOSSology postinstall complete, but sure to complete the remaining
    steps in the INSTALL instructions.
    _______________________________________
    fossology mailing list

    http://lists.fossology.org/mailman/listinfo/fossology

History

Updated by Dong Ma about 1 year ago

  • Target version changed from 2.0.0 to 2.0.1

Have reply email to Pete, I consider this bug should move to 2.0.1.

1. Ubuntu 12.04 have not supported in this release, so we didn't do any tests on ubuntu 12.04
2. If you want to upgrade fossology, don't use 'sudo apt-get upgrade fossolology', just use 'sudo apt-get install fossology'
3. For now our packages is Unofficial packages, so we didn't add authentication into packages in this release.

Updated by Paul Holland about 1 year ago

  • IterNum set to 2

Updated by Dong Ma about 1 year ago

  • Estimated time set to 20.00

Updated by Paul Holland 12 months ago

  • Rank set to 2

Updated by Paul Holland 12 months ago

  • IterNum changed from 2 to 3

Updated by Dong Ma 12 months ago

  • Status changed from New to In Progress
  • Estimated time changed from 20.00 to 24.00

Need one more days to investigate how to sign debian pacakges and estimate 2~3 days to fix it.

Updated by Dong Ma 12 months ago

  • Estimate set to 3

Updated by Dong Ma 12 months ago

  • Status changed from In Progress to Resolved

As team discussed, we will not sign the packages.

Updated by Paul Holland 11 months ago

  • Assignee changed from Dong Ma to Mary Laser
  • IterNum changed from 3 to 6

Needs to be validated by Mary. She'll be back in iteration 6.

Updated by Mary Laser 11 months ago

  • Status changed from Resolved to Closed

no changes were made (per note #8). no need to verify.

Updated by Mary Laser 10 months ago

  • Target version changed from 2.0.1 to 2.1.0

Also available in: Atom PDF