[opensuse-factory] source services
Hi, is there some kind of statement if source services should or should/must not be used for openSUSE:Factory packages? I cannot remember to have read anything about that before. Or does it matter at all? Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Freitag, 14. Januar 2011 schrieb Wolfgang Rosenauer:
Hi,
is there some kind of statement if source services should or should/must not be used for openSUSE:Factory packages? I cannot remember to have read anything about that before. Or does it matter at all?
The idea behind source services is that you have the server to download the tar from the original upstream, so there is some more confidence that the packager didn't make up the tar ball and inject funny things. The same could of course be implemented differently, but source service are the answer of the build service team (adrian mainly). But using source services is quite fragile - it's implementation in the build service is far from HA, so not using it surely brings advantages if all you want is to build a package. And many tools are not prepared to work with incomplete source checkouts - e.g. quilt setup or rpmbuild won't work on your osc checkout. So no, there is absolutely no requirement to use services for openSUSE:Factory, but you're free to experiment with it and also submit your experiments if you're happy with them and want to maintain them this way. What won't work at the moment are services that generate spec files out of nothing, e.g. the cpanspec service generates the spec file from the cpan tar and many tools (including the build service itself) expect a spec file. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hello Bernhard First thanks for the qa test harness that checks iso installs of factory. I am writing so see if this is is possible with the qa system. Thanks for advice on this. The qa system would prove good value for testing the following. Cheers Glenn The request involves testing a built kernel {Im in the process of building the kernel}. The steps would be something like this sequence of steps. The check would run say 2 times a day. - Check the Kernel built ok [1] by searching for the string in the log "build: extracting built packages..." - If search {"build: extracting built packages..."} found continue,else stop. - copy the built kernel from obs project to qa test area. - Boot the built kernel - Check booted ok - Next open a terminal session - Check terminal session opened ok and run a sequence of commands at a prompt # modprobe -v reiser4 see output[2] # echo next allocate some unused disk to reiser4 partition # mkfs.reiser4 -o create=ccreg40,compress=lzo1 /dev/sdb -fy # echo check the super block see output[3] # fsck.reiser4 --fix /dev/sdb -y # echo mount reiser4 partition on /media/disk # mkdir /media # mkdir /media/disk # mount -t reiser4 /dev/sdb /media/disk # cd /media/disk # echo untar a sample kernel # time tar -jxvf /tmp/linux-2.6.36.3.tar.bz2 # echo remove unpacked files # time rm -rf linux-2.6.36.3 # echo unmount reiser4 partition # cd / # unmount /media/disk # echo "*finished*" # exit [1] Example of build kernel location it will change at a future date. https://build.opensuse.org/package/live_build_log?arch=x86_64&package=kernel-vanilla&project=home%3Adoiggl&repository=openSUSE_Factory [2] insmod /lib/modules/2.6.36.2-56-vanilla/kernel/lib/zlib_deflate/zlib_deflate.ko insmod /lib/modules/2.6.36.2-56-vanilla/kernel/lib/lzo/lzo_compress.ko insmod /lib/modules/2.6.36.2-56-vanilla/kernel/fs/reiser4/reiser4.ko [3] ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. ******************************************************************* Fscking the /dev/sdb block device. Will fix minor corruptions of the Reiser4 SuperBlock. Will fix minor corruptions of the Reiser4 FileSystem. ***** fsck.reiser4 started at Mon Dec 27 16:04:57 2010 Reiser4 fs was detected on /dev/sdb. Master super block (16): magic: ReIsEr4 blksize: 4096 format: 0x0 (format40) uuid: 5602fc26-41a7-4361-b3a7-39a673679f80 label: <none> Format super block (17): plugin: format40 description: Disk-format plugin. version: 0 magic: ReIsEr40FoRmAt mkfs id: 0x62e55157 flushes: 0 blocks: 244190640 free blocks: 244183135 root block: 23 tail policy: 0x2 (smart) next oid: 0x10000 file count: 1 tree height: 2 key policy: LARGE CHECKING THE STORAGE TREE Read nodes 2 Nodes left in the tree 2 Leaves of them 1, Twigs of them 1 Time interval: Mon Dec 27 16:05:52 2010 - Mon Dec 27 16:05:52 2010 CHECKING EXTENT REGIONS. Read twigs 1 Time interval: Mon Dec 27 16:05:52 2010 - Mon Dec 27 16:05:53 2010 CHECKING THE SEMANTIC TREE Found 1 objects (some could be encountered more then once). Time interval: Mon Dec 27 16:05:53 2010 - Mon Dec 27 16:05:53 2010 ***** fsck.reiser4 finished at Mon Dec 27 16:05:53 2010 Closing fs...done FS is consistent. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi Glenn, this is a nice testing proposal and I think, that can be run regularly on http://openQA.opensuse.org. Since creating & maintaining such a test can be quite some work, I would appreciate it, if you could provide a few simple scripts (bash/perl/ruby), that would do the building/running/checking and report failure or success either as a simple text message or via return code. I did one such test-script at http://www.zq1.de/qatests/qa_ntp.pl This design has the advantage that tests can also easily be run standalone on any installation. I can then add just the glue for openQA testing, which looks like this: http://openqa.opensuse.org/opensuse/perl/autoinst/consoletest.d/170_sntp.pm Ciao Bernhard M. P.S. you should not use the reply button when you want to start a completely different topic, because your mail-client will include a "References" header so that other mail clients will include your message in the wrong thread. Am 19.01.2011 14:21, schrieb doiggl@velocitynet.com.au:
Hello Bernhard First thanks for the qa test harness that checks iso installs of factory.
I am writing so see if this is is possible with the qa system. Thanks for advice on this. The qa system would prove good value for testing the following. Cheers Glenn
The request involves testing a built kernel {Im in the process of building the kernel}. The steps would be something like this sequence of steps. The check would run say 2 times a day. - Check the Kernel built ok [1] by searching for the string in the log "build: extracting built packages..." - If search {"build: extracting built packages..."} found continue,else stop. - copy the built kernel from obs project to qa test area. - Boot the built kernel - Check booted ok
- Next open a terminal session - Check terminal session opened ok and run a sequence of commands at a prompt # modprobe -v reiser4 see output[2] # echo next allocate some unused disk to reiser4 partition # mkfs.reiser4 -o create=ccreg40,compress=lzo1 /dev/sdb -fy # echo check the super block see output[3] # fsck.reiser4 --fix /dev/sdb -y # echo mount reiser4 partition on /media/disk # mkdir /media # mkdir /media/disk # mount -t reiser4 /dev/sdb /media/disk # cd /media/disk # echo untar a sample kernel # time tar -jxvf /tmp/linux-2.6.36.3.tar.bz2 # echo remove unpacked files # time rm -rf linux-2.6.36.3 # echo unmount reiser4 partition # cd / # unmount /media/disk # echo "*finished*" # exit
[1] Example of build kernel location it will change at a future date. https://build.opensuse.org/package/live_build_log?arch=x86_64&package=kernel-vanilla&project=home%3Adoiggl&repository=openSUSE_Factory
[2] insmod /lib/modules/2.6.36.2-56-vanilla/kernel/lib/zlib_deflate/zlib_deflate.ko insmod /lib/modules/2.6.36.2-56-vanilla/kernel/lib/lzo/lzo_compress.ko insmod /lib/modules/2.6.36.2-56-vanilla/kernel/fs/reiser4/reiser4.ko
[3] ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. *******************************************************************
Fscking the /dev/sdb block device.
Will fix minor corruptions of the Reiser4 SuperBlock.
Will fix minor corruptions of the Reiser4 FileSystem.
***** fsck.reiser4 started at Mon Dec 27 16:04:57 2010 Reiser4 fs was detected on /dev/sdb.
Master super block (16): magic: ReIsEr4 blksize: 4096 format: 0x0 (format40) uuid: 5602fc26-41a7-4361-b3a7-39a673679f80 label: <none>
Format super block (17): plugin: format40 description: Disk-format plugin. version: 0 magic: ReIsEr40FoRmAt mkfs id: 0x62e55157 flushes: 0 blocks: 244190640 free blocks: 244183135 root block: 23 tail policy: 0x2 (smart) next oid: 0x10000 file count: 1 tree height: 2 key policy: LARGE
CHECKING THE STORAGE TREE
Read nodes 2
Nodes left in the tree 2 Leaves of them 1, Twigs of them 1 Time interval: Mon Dec 27 16:05:52 2010 - Mon Dec 27 16:05:52 2010
CHECKING EXTENT REGIONS.
Read twigs 1
Time interval: Mon Dec 27 16:05:52 2010 - Mon Dec 27 16:05:53 2010
CHECKING THE SEMANTIC TREE
Found 1 objects (some could be encountered more then once).
Time interval: Mon Dec 27 16:05:53 2010 - Mon Dec 27 16:05:53 2010
***** fsck.reiser4 finished at Mon Dec 27 16:05:53 2010 Closing fs...done
FS is consistent.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hello Bernhard
Some progress made.
Here is a script [1] which does the following
-Checks the obs build log for a rpm package
-Retrieves rpm to the /tmp/ directory.
The next bit I am unsure how to script with using the openqa
-boot to a termial
- run command to install following rpms sourced from [2] use rpm -ivhU
....
reiser4progs-1.0.7-1.21.x86_64.rpm
kernel-reiser4-2.6.37-15.1.x86_64.rpm
- after that reboot to new kernel
- start terminal
- run command to mount disk and format it using following commands
# mkfs.reiser4 -o create=ccreg40,compress=lzo1 /dev/sdX -fy
# fsck.reiser4 --fix /dev/sdX -y
# mkdir /reiser4
# mount -t reiser4 /dev/sdX /reiser4
# manually added reiser4 filesystem to /etc/fstab
/dev/sdX /reiser4 reiser4 defaults 0 0
- Reboot and select new kernel
- open terminal and copy some files to new filesystem
Thanks for the assistance
Glenn
[1]
# cat ./retrive.sh
buildlog="/tmp/buildlog.txt"
filelist="/tmp/filelist.txt"
id="doiggl"
packagename="kernel-reiser4"
distribution="openSUSE_11.3"
platform="x86_64"
cd /tmp
# example how to list log
# osc rbl home:doiggl kernel-vanilla openSUSE_11.3 x86_64 > $buildlog
echo "## please wait while extracting build log from obs and finding
built .rpm (if any) from build log"
echo "## running process osc rbl home:$id $packagename $distribution
$platform - results in $buildlog "
osc rbl home:$id $packagename $distribution $platform >$buildlog
RETVAL=$?
echo "$RETVAL"
if [ "$RETVAL" -eq "0" ]
then
echo "## found log now searching for any built .rpms"
tail -4 $buildlog | head -1 > $filelist
fileremote="
ftp5.gwdg.de/pub/opensuse/repositories/home:/$id/$distribution/$platform/`cat
$filelist`"
/usr/bin/wget -c $fileremote
RETVAL=$?
if [ "$RETVAL" -eq "0" ]
then
echo "wget ok on $fileremote"
echo "file is: /tmp/`cat $filelist`"
echo "return code: $RETVAL "
else
echo "## wget failed on $fileremote"
echo $RETVAL
exit $RETVAL
fi
else
echo "## no buildlog found"
exit 2
fi
echo "## process finished..."
[2]
http://download.opensuse.org/repositories/home:/lmich/openSUSE_Factory/x86_6...
https://build.opensuse.org/package/binaries?package=kernel-reiser4&project=home%3Adoiggl&repository=openSUSE_11.3
On Wed, 19 Jan 2011 15:01:49 +0100, "Bernhard M. Wiedemann"
Hi Glenn,
this is a nice testing proposal and I think, that can be run regularly on http://openQA.opensuse.org. Since creating & maintaining such a test can be quite some work, I would appreciate it, if you could provide a few simple scripts (bash/perl/ruby), that would do the building/running/checking and report failure or success either as a simple text message or via return code.
I did one such test-script at http://www.zq1.de/qatests/qa_ntp.pl
This design has the advantage that tests can also easily be run standalone on any installation. I can then add just the glue for openQA testing, which looks like this:
http://openqa.opensuse.org/opensuse/perl/autoinst/consoletest.d/170_sntp.pm
Ciao Bernhard M.
P.S. you should not use the reply button when you want to start a completely different topic, because your mail-client will include a "References" header so that other mail clients will include your message in the wrong thread.
Am 19.01.2011 14:21, schrieb doiggl@velocitynet.com.au:
Hello Bernhard First thanks for the qa test harness that checks iso installs of
factory.
I am writing so see if this is is possible with the qa system. Thanks for advice on this. The qa system would prove good value for testing the following. Cheers Glenn
The request involves testing a built kernel {Im in the process of building the kernel}. The steps would be something like this sequence of steps. The check would run say 2 times a day. - Check the Kernel built ok [1] by searching for the string in the log "build: extracting built packages..." - If search {"build: extracting built packages..."} found continue,else stop. - copy the built kernel from obs project to qa test area. - Boot the built kernel - Check booted ok
- Next open a terminal session - Check terminal session opened ok and
run
a sequence of commands at a prompt # modprobe -v reiser4 see output[2] # echo next allocate some unused disk to reiser4 partition # mkfs.reiser4 -o create=ccreg40,compress=lzo1 /dev/sdb -fy # echo check the super block see output[3] # fsck.reiser4 --fix /dev/sdb -y # echo mount reiser4 partition on /media/disk # mkdir /media # mkdir /media/disk # mount -t reiser4 /dev/sdb /media/disk # cd /media/disk # echo untar a sample kernel # time tar -jxvf /tmp/linux-2.6.36.3.tar.bz2 # echo remove unpacked files # time rm -rf linux-2.6.36.3 # echo unmount reiser4 partition # cd / # unmount /media/disk # echo "*finished*" # exit
[1] Example of build kernel location it will change at a future date.
[2] insmod
/lib/modules/2.6.36.2-56-vanilla/kernel/lib/zlib_deflate/zlib_deflate.ko
insmod /lib/modules/2.6.36.2-56-vanilla/kernel/lib/lzo/lzo_compress.ko insmod /lib/modules/2.6.36.2-56-vanilla/kernel/fs/reiser4/reiser4.ko
[3] ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. *******************************************************************
Fscking the /dev/sdb block device.
Will fix minor corruptions of the Reiser4 SuperBlock.
Will fix minor corruptions of the Reiser4 FileSystem.
***** fsck.reiser4 started at Mon Dec 27 16:04:57 2010 Reiser4 fs was detected on /dev/sdb.
Master super block (16): magic: ReIsEr4 blksize: 4096 format: 0x0 (format40) uuid: 5602fc26-41a7-4361-b3a7-39a673679f80 label: <none>
Format super block (17): plugin: format40 description: Disk-format plugin. version: 0 magic: ReIsEr40FoRmAt mkfs id: 0x62e55157 flushes: 0 blocks: 244190640 free blocks: 244183135 root block: 23 tail policy: 0x2 (smart) next oid: 0x10000 file count: 1 tree height: 2 key policy: LARGE
CHECKING THE STORAGE TREE
Read nodes 2
Nodes left in the tree 2 Leaves of them 1, Twigs of them 1 Time interval: Mon Dec 27 16:05:52 2010 - Mon Dec 27 16:05:52 2010
CHECKING EXTENT REGIONS.
Read twigs 1
Time interval: Mon Dec 27 16:05:52 2010 - Mon Dec 27 16:05:53 2010
CHECKING THE SEMANTIC TREE
Found 1 objects (some could be encountered more then once).
Time interval: Mon Dec 27 16:05:53 2010 - Mon Dec 27 16:05:53 2010
***** fsck.reiser4 finished at Mon Dec 27 16:05:53 2010 Closing fs...done
FS is consistent.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 29.01.2011 05:17, schrieb doiggl@velocitynet.com.au:
Hello Bernhard Some progress made. Here is a script [1] which does the following -Checks the obs build log for a rpm package -Retrieves rpm to the /tmp/ directory.
The next bit I am unsure how to script with using the openqa -boot to a termial
I would run the script in a console right away, since there should be nothing needing graphics. I made this from your input: http://openqa.opensuse.org/opensuse/qatests/qa_obs_retrieve.sh however, for obs API access, it wants access credentials, which should not be public. so we better use zypper addrepo \ http://download.opensuse.org/repositories/home:/doiggl/openSUSE_Factory/ reisertest and zypper -n install ... even testing the same software several times can give interesting results, because it interacts with other parts of the distribution, which do change (say, a DB using the FS). Ciao Bernhard M. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk1EPo0ACgkQSTYLOx37oWSMKQCdGK8+L2UQsAL60+MeVsrEq5jT Ns8AoNVi+av1xUctjAJ4EzQJ4Dj3Wa8V =wpg8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sat, 29 Jan 2011 17:21:33 +0100, "Bernhard M. Wiedemann"
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 29.01.2011 05:17, schrieb doiggl@velocitynet.com.au:
Hello Bernhard Some progress made. Here is a script [1] which does the following -Checks the obs build log for a rpm package -Retrieves rpm to the /tmp/ directory.
The next bit I am unsure how to script with using the openqa -boot to a termial
I would run the script in a console right away, since there should be nothing needing graphics.
I made this from your input: http://openqa.opensuse.org/opensuse/qatests/qa_obs_retrieve.sh
however, for obs API access, it wants access credentials, which should not be public.
so we better use zypper addrepo \ http://download.opensuse.org/repositories/home:/doiggl/openSUSE_Factory/ reisertest and zypper -n install ...
even testing the same software several times can give interesting results, because it interacts with other parts of the distribution, which do change (say, a DB using the FS).
Ciao Bernhard M. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAk1EPo0ACgkQSTYLOx37oWSMKQCdGK8+L2UQsAL60+MeVsrEq5jT Ns8AoNVi+av1xUctjAJ4EzQJ4Dj3Wa8V =wpg8 -----END PGP SIGNATURE-----
Hello Bernhard, Which scripts do you use to generate the output for the NET* of isos. Please include script in reply or a link to the script. Thanks Glenn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (4)
-
Bernhard M. Wiedemann -
doiggl＠velocitynet.com.au -
Stephan Kulow -
Wolfgang Rosenauer