[SOLVED]archiso and custom repo, failing to buld, pkg not found

qinohe · 2013-09-19 14:57:58

Hi all, having problems creating a custom repo, and adding it to archiso
The build is releng x86_64 only, it builds fine without the custom repo.
It runs in Virtualbox and bare metal, both running fine, no errors at all.

What have I done so far;
Used wiki for archiso pacman & pacman-tips(custom local repo) man repo-add etc.
Created a local repo for cower, first 'db', then 'files', and looks okay to me, like this;

repo-add custom.db.tar.xz cower-9-1-x86_64.pkg.tar.xz 
==> Adding package 'cower-9-1-x86_64.pkg.tar.xz'
  -> Computing checksums...
  -> Creating 'desc' db entry...
  -> Creating 'depends' db entry...
==> Creating updated database file 'custom.db.tar.xz'

repo-add -f custom.files.tar.xz cower-9-1-x86_64.pkg.tar.xz
==> Adding package 'cower-9-1-x86_64.pkg.tar.xz'
  -> Computing checksums...
  -> Creating 'desc' db entry...sed
  -> Creating 'depends' db entry...
  -> Creating 'files' db entry...
==> Creating updated database file 'custom.files.tar.xz'

Then I added 'custom' repo as first repo to releng/pacman.conf, like this;

[custom]
SigLevel = Optional TrustAll
Server = file:///home/mark/builds/custom

Added cower to releng/packages.x86_64 (at the top)

No errors about not finding the repo, it just can't find cower.

Mkarchiso gives this error, but whatever name I trow at it, cower or cower-9-1-x86_64 the output stays the same.
I still have the compleet output of build.sh, but I think this is the relevant part

[mkarchiso] INFO: Installing packages to 'work/x86_64/root-image/'...
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
error: target not found: cower-9-1-x86_64
warning: skipping target: ppp
error: target not found: cower-9-1-x86_64
error: target not found: cower-9-1-x86_64
warning: skipping target: ppp
error: target not found: cower-9-1-x86_64

Clearly, I'm overlooking something, in few posts, Allan and Xyne say the way to build a local repo, I followed their instructions, for clearness I add the url's
https://bbs.archlinux.org/viewtopic.php?id=164782
https://bbs.archlinux.org/viewtopic.php?id=150927

Thanks for talking time to read this.

edit;
Just to be sure I was not failing in the process, I added the custom repo to pacman on my main Arch OS/
No problems occur, this is the output;

  custom                   540.0   B   527K/s 00:00 [----------------------] 100%
 core is up to date
 extra is up to date
 community               2009.0 KiB   854K/s 00:02 [----------------------] 100%
 multilib is up to date
 repo-ck is up to date
:: Starting full system upgrade...
 there is nothing to do
No pacnew files to update.

and the second time

:: Synchronizing package databases...
 custom is up to date
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 repo-ck is up to date
:: Starting full system upgrade...
 there is nothing to do
No pacnew files to update.

Last edited by qinohe (2013-09-21 11:13:17)

qinohe · 2013-09-19 19:01:18

The story continuous. I found something that may well be worth adding.

After trying a few more times, I thought it be best to first try a really fresh build.
Created a new archlive dir. and cp'ed releng to it, and started to build right away.

Now I got an error saying the timestamp hook not being recognized.
After removing the timestamp hook from releng/mkinitcpio.conf the build finished and created an ISO, as the first time the image was successfully build but the ISO wasn't due to timestamp hook.

Haven't tried my own build yet, but I guess and hope this was the cause of it.
Does anyone know what happened to the timestamp hook, and how important is timesamp?

aesiris · 2013-09-19 19:02:07

qinohe wrote:

...
Mkarchiso gives this error, but whatever name I trow at it, cower or cower-9-1-x86_64 the output stays the same.
I still have the compleet output of build.sh, but I think this is the relevant part
[mkarchiso] INFO: Installing packages to 'work/x86_64/root-image/'...
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
error: target not found: cower-9-1-x86_64
...

I would expect a line for the custom repo:

 custom is up to date

are you sure that the syntax of releng/pacman.conf is correct? post the full file here

And in packages.x86_64 put just "cower" (as you would put after pacman -S ...)

qinohe wrote:

...Just to be sure I was not failing in the process, I added the custom repo to pacman on my main Arch OS/
No problems occur, this is the output;...

As an extra check, in on your main Arch try also

pacman -S cower

EDIT: About your post I didn't see:
This was in the output of pacman today when I updated systemd:

[2013-09-19 10:50] [ALPM-SCRIPTLET] ==> The "timestamp" hook for mkinitcpio no longer exists. If you used
[2013-09-19 10:50] [ALPM-SCRIPTLET]     this hook, you must remove it from /etc/mkinitcpio.conf. A "systemd"
[2013-09-19 10:50] [ALPM-SCRIPTLET]     hook has been added which provides this functionality, and more.
[2013-09-19 10:50] [PACMAN] upgraded systemd (204-3 -> 207-3)

Last edited by aesiris (2013-09-19 19:06:54)

karol · 2013-09-19 19:04:00

qinohe wrote:

Does anyone know what happened to the timestamp hook, and how important is timesamp?

https://mailman.archlinux.org/pipermail … 03855.html

qinohe · 2013-09-20 16:40:53

aesiris wrote:

I would expect a line for the custom repo:
 custom is up to date
are you sure that the syntax of releng/pacman.conf is correct? post the full file here
And in packages.x86_64 put just "cower" (as you would put after pacman -S ...)

Thanks for your answer aesiris, In fact, I do get the line 'custum is up to date', that is okay now.
Also I did put cower on top in my packages list, which I do for other repo's like multilib too. Multilib works fine.

As an extra check, in on your main Arch try also

pacman -S cower

EDIT: About your post I didn't see:
This was in the output of pacman today when I updated systemd:

[2013-09-19 10:50] [ALPM-SCRIPTLET] ==> The "timestamp" hook for mkinitcpio no longer exists. If you used
[2013-09-19 10:50] [ALPM-SCRIPTLET]     this hook, you must remove it from /etc/mkinitcpio.conf. A "systemd"
[2013-09-19 10:50] [ALPM-SCRIPTLET]     hook has been added which provides this functionality, and more.
[2013-09-19 10:50] [PACMAN] upgraded systemd (204-3 -> 207-3)

Completely missed that scriptlet.
Also added the repo to my main machine, cower is installing just fine, and I expected that.

@karol , thanks karol, where would we all be without you.
I must really subscribe to the mailinglist, I have done without so far.
But it seems I can't do without any longer.

The ISO, It's an on my own project, with i3WM on it I have build dozens of times, In fact, it is/was almost ready for github, but I'm back to basics, have build the ISO with a new fresh releng, and changed nothing.
Everything seems to be working as it should, all is build, the ISO also.

Ready to test it in Vbox, and it ends with the well known 30 second timeout, right after syslinux

losetup: /run/archiso/bootmnt/arch/x86_64/root-image.fs.sfs: failed to set up loop device: No such file or directory
Waiting 30 seconds for device...
ERROR: '' device did not show up after 30 seconds...

Maybe this is obvious to someone else, but I haven't got a clue what path I should use...
Or even where to put it.
Are any other builders seeing this issue?
Thanks

BTW, the ISO build with archiso --git, comes down with a kernel crash, all the above is about 'archiso'

karol · 2013-09-20 16:57:44

Two guesses:
1. If you're using VB, you're unlikely to use UNetbootin for the iso, but just FYI - UNetbootin breaks things https://bbs.archlinux.org/viewtopic.php?id=156066
2. Compare

ERROR : ‘/dev/disk/by-label/‘ device did not show up after 30 seconds...

from the thread I linked to in point one to

ERROR: '' device did not show up after 30 seconds...

you're getting.

BTW, I'm using [testing] and I got the message about dropping 'timespamp' hook so long ago, that I completely forgot about it:

[2013-07-23 20:43] [ALPM-SCRIPTLET] ==> The "timestamp" hook for mkinitcpio no longer exists. If you used

;P

qinohe · 2013-09-20 17:43:19

karol wrote:

Two guesses:
1. If you're using VB, you're unlikely to use UNetbootin for the iso, but just FYI - UNetbootin breaks things https://bbs.archlinux.org/viewtopic.php?id=156066
2. Compare
ERROR : ‘/dev/disk/by-label/‘ device did not show up after 30 seconds...
from the thread I linked to in point one to
ERROR: '' device did not show up after 30 seconds...
you're getting.

BTW, I'm using [testing] and I got the message about dropping 'timespamp' hook so long ago, that I completely forgot about it:
[2013-07-23 20:43] [ALPM-SCRIPTLET] ==> The "timestamp" hook for mkinitcpio no longer exists. If you used
;P

Thanks, I don't use tools like UNetbootin, USB I build manual, the ISO is straight from mkarchiso to vbox, and I think that should work.
here is some output;

[mkarchiso] INFO: Done! | 533M out/archlinux-2013.09.20-dual.iso
[root@nymph releng]# mv out/archlinux-2013.09.20-dual.iso /run/media/mark/media-vps/isoos/ 
[root@nymph releng]# chown mark:users /run/media/mark/media-vps/isoos/archlinux-2013.09.20-dual.iso 
[root@nymph releng]#

Oh and my last working build is still starting/running without problems.

I see your point about the error, I think that is how archiso handling this?
It's strange that it's happening to a fresh build.
Maybe, very maybe there is a bug

Haha, this my main machine, I don't dare to ptu testing on it yet;)
.
Maybe, if my interest in Arch keeps growing like it does now, I will probably run testing some day

qinohe · 2013-09-21 11:12:50

Thanks devs for systemd 207-5, all issues are solved at once;)

I directly tried my own build and everything is working, also my custom repo with with cower in it.Running fine in Vbox, solved.

Arch Linux

#1 2013-09-19 14:57:58

[SOLVED]archiso and custom repo, failing to buld, pkg not found

#2 2013-09-19 19:01:18

Re: [SOLVED]archiso and custom repo, failing to buld, pkg not found

#3 2013-09-19 19:02:07

Re: [SOLVED]archiso and custom repo, failing to buld, pkg not found

#4 2013-09-19 19:04:00

Re: [SOLVED]archiso and custom repo, failing to buld, pkg not found

#5 2013-09-20 16:40:53

Re: [SOLVED]archiso and custom repo, failing to buld, pkg not found

#6 2013-09-20 16:57:44

Re: [SOLVED]archiso and custom repo, failing to buld, pkg not found

#7 2013-09-20 17:43:19

Re: [SOLVED]archiso and custom repo, failing to buld, pkg not found

#8 2013-09-21 11:12:50

Re: [SOLVED]archiso and custom repo, failing to buld, pkg not found

Board footer