[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#773253: jenkins: please add script to detect dpkg trigger cycles



Hi josch,

On Mittwoch, 31. Dezember 2014, Johannes Schauer wrote:
> I made a number of modifications to jenkins but I fail to run
> bin/chroot-run.sh locally by itself. So I gave up.

I guess I should try myself and fix/document this...
 
> Instead, I created a Jessie chroot, copied Jenkins inside it and ran
> bin/find_dpkg_trigger_cycles.sh to test.

ok. (i dont understand what you mean with "copied jenkins inside it"..)

> The attached patch installs apt-file and dose-extra as the two additional
> dependencies I had to install for the find_dpkg_trigger_cycles script.

please re-do the patch without that hunk... it belongs in the part where the 
jessie chroot is created... (the script should be able to run as user, not as 
root and also should not need to use "sudo apt-get install"....)

> Since this is running in Jessie, I also removed the python-arpy hack and
> rely on dpkg instead.

OTOH, as this is the only change, I guess I can cherry-pick half the patch 
from here....

> Since I could not test this locally, I didn't touch job-cfg/dpkg.yaml, so
> this still has to be done.

ok, will do...

> One remaining problem could be that there might be no /dev/stdin inside the
> chroot.  If this is the case, then we still have to use python-arpy or
> somehow mount /dev and /proc (or only /proc and read from /proc/self/fd/0
> instead). This is until bug #616614 is fixed.

ack.

> Thanks!

likewise and apologies for the slow progress... I expected this script to be 
easier :)


cheers,
	Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: