Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating the list of repositories does not update the packages summary info #3

Closed
jacques opened this issue Jul 5, 2013 · 11 comments
Closed

Comments

@jacques
Copy link

jacques commented Jul 5, 2013

pkgin update after updating /opt/local/etc/pkgin/repositories.conf

[Wed, 03 Jul 2013 18:34:29 +0000] FATAL: Chef::Exceptions::Package: package[unzip] (sharecell::packages-archivers line 19) had an error: Chef::Exceptions::Package: Package unzip not found
[ Jul  3 18:34:29 Method "start" exited with status 1. ]

Manually force -f (sometimes a few times for it to actually update):

[root@wellington (ord) /var/chef]# pkgin -f up
pkg_summary.gz                                                                       100%  511KB 511.4KB/s 511.4KB/s   00:00   
cleaning database from http://pkgsrc.ams.example.com/sdc6/2012Q2/i386/All entries...
cleaning database from http://pkgsrc.ams.example.com/foo/2012Q2/i386/All entries...
cleaning database from http://pkgsrc.example.com/sdc6/2012Q2/i386/All entries...
cleaning database from http://pkgsrc.example.com/foo/2012Q2/i386/All entries...
processing remote summary (http://pkgsrc.example.com/sdc6/2012Q2/i386/All)...
updating database: 100%
pkg_summary.gz                                                                       100%   41KB  41.4KB/s  41.4KB/s   00:00   
processing remote summary (http://pkgsrc.example.com/foo/2012Q2/i386/All)...
updating database: 100%
@CRThaze
Copy link

CRThaze commented Aug 2, 2013

+1

in our case force update doesn't seem to do anything to the local database (as seen by opening it with a sqlite client), and it requires the deletion of the local db file for it to actually set up the correct data.

@pagodajosh
Copy link

Same issue. After scouring the code base the only hypothesis I have left is that the command to insert the packages into the database is failing silently. The message updating database: 100% indicates that pkgin thinks that it is inserting records (even though no records are added in pkgin.db).

@iMilnb
Copy link
Contributor

iMilnb commented Aug 3, 2013

Hi all, could you please provide pkgin version, repository address and OS used?

Thanks a lot for the feedbacks

@CRThaze
Copy link

CRThaze commented Aug 4, 2013

We're using: pkgin 0.6.3.1.1 for SunOS-5.11 x86_64 (using SQLite 3.7.15.2)
It's running on a SmartOS SmartMachine.

The repository however is a private repository running on our internal network.

@pagodajosh
Copy link

As a clarification, we saw this when switching to the private repo as well as switching from the private repo.

Testing was done on smartOS and Mac OS.

If we deleted the database or broke it so the pkgin db validation failed, pkgin would update. No matter what repo it was pointed at.

@jacques
Copy link
Author

jacques commented Sep 14, 2013

These hosts (100+ SmartOS non-global zones) are using the older version from pkgin from the pkgsrc 2012Q2 quarterly.

[root@wellington (ord) ~]# pkgin -v
pkgin 0.6.0 for SunOS-5.11 i386 (using SQLite 3.7.7.1)

Still working on a 2013Q2 upgrade solution since Joyent renumbered all the UID/GID's from installed packages.

@CRThaze
Copy link

CRThaze commented Sep 14, 2013

We have found that trashing the db file tends to do the trick of forcing an update if it doesn't work other wise.

rm -rf /var/db/pkgin

@jacques
Copy link
Author

jacques commented Oct 11, 2013

@iMilnb wgetting a pkgin.db file in the statethat works over the original pkgin.db works better than a clean one that does not update. Let me know what your ssh key is and skype id and we can chat and you can take a look at some boxes.

@iMilnb
Copy link
Contributor

iMilnb commented Apr 7, 2014

Hi everyone,

I changed the way packages are listed when multiple repositories are declared in repositories.conf, this could possibly fix the issues you are facing. Any of you could try the latest commit please?

@jacques
Copy link
Author

jacques commented Apr 7, 2014

Going to build and test.

@iMilnb
Copy link
Contributor

iMilnb commented Dec 27, 2014

No news from reporter for 6 months+, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants