Copying wrong pacman.conf file when creating isos #211

Closed
opened 2016-05-08 17:23:33 +00:00 by philm · 6 comments
philm commented 2016-05-08 17:23:33 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: Kirek

We copy a pacman.conf tailored for chroot builds, and we use that in the isos too. We need to copy the proper pacman.conf to the iso, or restore the default.

See this thread:
https://forum.manjaro.org/index.php?topic=33857.0

*Created by: Kirek* We copy a pacman.conf tailored for chroot builds, and we use that in the isos too. We need to copy the proper pacman.conf to the iso, or restore the default. See this thread: https://forum.manjaro.org/index.php?topic=33857.0
philm commented 2016-05-09 07:41:41 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: udeved

There should be no difference between pacman.conf from pacman package and our pacman.conf files for builds.
If there is a diff, we should just update the files, but, we don't have the stuff uncommented as the thread reports.
CacheDir is commented, and CheckSpace option is also present and commented in both conf files.

*Created by: udeved* There should be no difference between pacman.conf from pacman package and our pacman.conf files for builds. If there is a diff, we should just update the files, but, we don't have the stuff uncommented as the thread reports. CacheDir is commented, and CheckSpace option is also present and commented in both conf files.
philm commented 2016-05-09 17:12:53 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: udeved

Now, here is the golden washing machine question.
What edition was used to install? Was a custom pacman.conf used in the iso profile?

I am seriously thinking about removing support to add 3rd party repos to buildiso.

*Created by: udeved* Now, here is the golden washing machine question. What edition was used to install? Was a custom pacman.conf used in the iso profile? I am seriously thinking about removing support to add 3rd party repos to buildiso.
philm commented 2016-05-09 20:50:01 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: Kirek

This problem is present in the main editions, nothing to do with custom pacman.conf.
CacheDir should be commented, and CheckSpace should be uncommented.

We are overwriting the default pacman.conf https://github.com/manjaro/packages-core/blob/master/pacman/pacman.conf.x86_64 with the pacman.conf tailored for chroot builds https://github.com/manjaro/manjaro-tools/blob/master/data/pacman-multilib.conf, which is fine when creating the iso, but we don't restore the original file before squashing. So all isos end up with a wrong pacman.conf, without CheckSpace enabled.

*Created by: Kirek* This problem is present in the main editions, nothing to do with custom pacman.conf. CacheDir should be commented, and CheckSpace should be uncommented. We are overwriting the default pacman.conf https://github.com/manjaro/packages-core/blob/master/pacman/pacman.conf.x86_64 with the pacman.conf tailored for chroot builds https://github.com/manjaro/manjaro-tools/blob/master/data/pacman-multilib.conf, which is fine when creating the iso, but we don't restore the original file before squashing. So all isos end up with a wrong pacman.conf, without CheckSpace enabled.
philm commented 2016-05-09 21:26:58 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: udeved

Ok, so we won't copy pacman.conf in chroot-run and rely on the pacman.conf provided by pacman pkg.
This makes custom repos not possible, which is fine with me.

*Created by: udeved* Ok, so we won't copy pacman.conf in chroot-run and rely on the pacman.conf provided by pacman pkg. This makes custom repos not possible, which is fine with me.
philm commented 2016-05-09 22:11:52 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

Ok, makes sense. Then we should not copy the pacman.conf ...

*Created by: philmmanjaro* Ok, makes sense. Then we should not copy the **pacman.conf** ...
philm commented 2016-05-10 15:37:39 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: udeved

I confused the commit message and issue number.
github.com/manjaro/manjaro-tools@2825dfaae4

*Created by: udeved* I confused the commit message and issue number. https://github.com/manjaro/manjaro-tools/commit/2825dfaae4a7fd688fa4bd135655df67cf3ad9b6
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
tools/manjaro-tools#211
No description provided.