Clean chroot now with every build? #157

Closed
opened 2015-12-07 07:03:34 +00:00 by philm · 8 comments
philm commented 2015-12-07 07:03:34 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

I noticed now that we clean-up the chroot on every build. Is this now default and wanted?

*Created by: philmmanjaro* I noticed now that we clean-up the chroot on every build. Is this now default and wanted?
philm commented 2015-12-07 15:53:19 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: udeved

Not that I am aware of.
But, we changed the git version in the scripts to have a git id rather than version number.
This causes check_chroot to recreate the chroot, because the version check detects new chroot version.
Perhaps its not ideal for our git package to have a git version variable.

*Created by: udeved* Not that I am aware of. But, we changed the git version in the scripts to have a git id rather than version number. This causes check_chroot to recreate the chroot, because the version check detects new chroot version. Perhaps its not ideal for our git package to have a git version variable.
philm commented 2015-12-07 20:31:43 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

No, I'm talking about the regular build. Maybe it doesn't like to have 0.9.15-rc1 as version. Simply install the current non-git-version and try to build a package. It will recreate the chroot every time. That's why I was wondering ...

*Created by: philmmanjaro* No, I'm talking about the regular build. Maybe it doesn't like to have **0.9.15-rc1** as version. Simply install the current non-git-version and try to build a package. It will recreate the chroot every time. That's why I was wondering ...
philm commented 2015-12-07 20:35:47 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: udeved

Hmm, it works for me with git version, updating chroot works on my end.

Please review github.com/manjaro/packages-extra@a70c0855b9

*Created by: udeved* Hmm, it works for me with git version, updating chroot works on my end. Please review https://github.com/manjaro/packages-extra/commit/a70c0855b95b5628ad91d1eef7f3f2070d504f47
philm commented 2015-12-07 20:37:37 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

Will check that later ...

*Created by: philmmanjaro* Will check that later ...
philm commented 2015-12-09 08:24:19 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

Hmm, the latest changes gave me now this:

==> ERROR: chroot '/var/lib/manjaro-tools/buildpkg/stable/x86_64/phil' is not at version r1784.d895624. Please rebuild.

Will check what will happen next if I build another package in the same chroot. The funny thing is, I'm doing unstable here. Some is wrong with the check.

*Created by: philmmanjaro* Hmm, the latest changes gave me now this: ``` ==> ERROR: chroot '/var/lib/manjaro-tools/buildpkg/stable/x86_64/phil' is not at version r1784.d895624. Please rebuild. ``` Will check what will happen next if I build another package in the same chroot. The funny thing is, I'm doing **unstable** here. Some is wrong with the check.
philm commented 2015-12-09 08:26:28 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

Ah, forget the stable cmd. manjaro-tools.conf changed it's location. I forgot about that.

*Created by: philmmanjaro* Ah, forget the stable cmd. manjaro-tools.conf changed it's location. I forgot about that.
philm commented 2015-12-09 08:29:37 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

Ok, I can confirm: removing the check doesn't do anything. It still deletes the chroot on each build of a package. So we have to fix this issue on systemd systems.

*Created by: philmmanjaro* Ok, I can confirm: removing the check doesn't do anything. It still deletes the chroot on each build of a package. So we have to fix this issue on **systemd** systems.
philm commented 2015-12-09 08:32:46 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

I'm stupied. Did again a -c build ... Tilt.

*Created by: philmmanjaro* I'm stupied. Did again a **-c** build ... Tilt.
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#157
No description provided.