dskvr / opkg

Automatically exported from code.google.com/p/opkg
0 stars 0 forks source link

opkg cannot create some sub-directories for itself #110

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Build opkg with parameters --with-opkglibdir and --with-opkgetcdir pointing 
to some dir you choose, e.g. ~/opkg-test.
2. mkdir ~/opkg-test. Don't create any subdirs.
3. Run opkg-cl with list-installed parameter, for example.

What is the expected output? What do you see instead?
Expected: (empty) list of installed packages.
What happens instead: an error message -

Collected errors:
 * opkg_conf_load: Could not create lock file /home/your_username/opkg-test/lib/opkg/lock: No such file or directory.

What version of the product are you using? On what operating system?
r739 at Linux Mint Debian Edition.

Please provide any additional information below.
I think that user should not be responsible for creating any subdirectories for 
software, but software should do that itself if they don't exist.

Original issue reported on code.google.com by paintitg...@gmail.com on 30 Oct 2013 at 11:39

GoogleCodeExporter commented 8 years ago
I agree this is a bug and we need to fix it. However, it is easy to work around 
(for example, OpenEmbedded already works around this). So I'm going to 
prioritise other bugs for the 0.3 release unless someone else wants to send a 
patch that fixes this.

Original comment by paul.betafive on 20 Dec 2013 at 5:47

GoogleCodeExporter commented 8 years ago
Sorry, you are right. Please could you close.

Original comment by Kros...@gmail.com on 20 Dec 2013 at 6:32

GoogleCodeExporter commented 8 years ago
I think that comment belongs on issue 114. I'll mark that as a duplicate.

Original comment by paul.betafive on 20 Dec 2013 at 6:33

GoogleCodeExporter commented 8 years ago
Issue 114 has been merged into this issue.

Original comment by paul.betafive on 20 Dec 2013 at 6:34

GoogleCodeExporter commented 8 years ago
This is almost fixed with the latest changes to master which place the lock 
file in '/var/run/opkg.lock' by default. For the rare cases where '/var/run' 
might not already exist, I'll add a call to file_mkdir_hier() before the access 
to the lock file.

Original comment by paul.betafive on 11 Jun 2014 at 10:23

GoogleCodeExporter commented 8 years ago
Fixed in master.

Original comment by paul.betafive on 19 Jul 2014 at 3:04