[opensuse-packaging] Update source breaks it all..
I just added a source for updates, mirrored locally and I've run createrepo on the dir. So, I added it in the config like this: url_suse="file:/iscsi/Archives/SuSE/inst_source/10.1" url_updates="file:/iscsi/Archives/SuSE/inst_source/10.1_up" add_sources="suse updates" So, then I tried to do a build, and this came out (hundreds of lines deleted).. root dir set to /store3/build.root.10.1-x86_64 running from system no ATTENTION: this is a one way ticket. Resetting this to true has not effect! initializing installation sources ... initializing target ... rebuilding RPM database ..................................................... ok reading RPM database ........................................................ ok Known sources: 0: [x] SUSE Linux 10.1 (file:/iscsi/Archives/SuSE/inst_source/10.1) 1: [x] file:/iscsi/Archives/SuSE/inst_source/10.1_up/ (file:/iscsi/Archives/SuSE/inst_source/10.1_up) [autorefresh] debug disabled 90 packages to install unresolvable dependencies: *** Conflicts *** Name: /bin/sh(*) Edition: EDITION-UNSPEC Referers: aaa_base-10.1-41 requires /bin/sh, Not-Available: any Name: /bin/bash(*) Edition: EDITION-UNSPEC Referers: aaa_base-10.1-41 requires /bin/bash, bind-utils-9.3.2-17 requires /bin/bash, groff-1.18.1.1-29 requires /bin/bash, less-394-12 requires /bin/bash, module-init-tools-3. 2.2-32.13 requires /bin/bash, perl-5.8.8-12 requires /bin/bash, pwdutils-3.0.7.1-17 requires /bin/bash, rpm-4.4.2-43.4 requires /bin/bash, util-linux-2.12r-35 requires /bin/bash Not-Available: any Ideas please.... -- Anders Norrbring Norrbring Consulting
Am Montag, 2. Oktober 2006 10:08 schrieb Anders Norrbring: [...] http://lists.opensuse.org/opensuse-packaging/2006-08/msg00021.html Detlef --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Detlef Reichelt skrev:
Am Montag, 2. Oktober 2006 10:08 schrieb Anders Norrbring: [...]
http://lists.opensuse.org/opensuse-packaging/2006-08/msg00021.html
So... Now it's all set.. I've mirrored fresh, I ran createrepo on it, and then create_package_descr as last step. Build environment starts to set up, but there are always one file (not the same one every time) that fails to install.. Like this: fetching bash (475.7 kB) .................................................... ok installing [ 0%] bash-3.1-24.3 (x86_64) .................................... *** failed: ERROR(InstTarget:E_RpmDB_subprocess_failed)[error: unpacking of archive failed on file /usr/share/doc/packages/bash/bash.html;452160a2: cpio: open failed - No such file or directory ] ERROR(InstSrc:E_cancel_media) Ideas? -- Anders Norrbring Norrbring Consulting
Anders Norrbring skrev:
Detlef Reichelt skrev:
Am Montag, 2. Oktober 2006 10:08 schrieb Anders Norrbring: [...]
http://lists.opensuse.org/opensuse-packaging/2006-08/msg00021.html
So... Now it's all set.. I've mirrored fresh, I ran createrepo on it, and then create_package_descr as last step.
Build environment starts to set up, but there are always one file (not the same one every time) that fails to install.. Like this:
fetching bash (475.7 kB) .................................................... ok installing [ 0%] bash-3.1-24.3 (x86_64) .................................... *** failed: ERROR(InstTarget:E_RpmDB_subprocess_failed)[error: unpacking of archive failed on file /usr/share/doc/packages/bash/bash.html;452160a2: cpio: open failed - No such file or directory ] ERROR(InstSrc:E_cancel_media)
Ideas?
Still nobody that can shed some light onto this? My y2pmbuild works just fine with the repo created from the DVD dist of 10.1, but as soon as I enter the repo created from my update mirror, it breaks at every attempt to build. -- Anders Norrbring Norrbring Consulting
Anders Norrbring wrote:
Anders Norrbring skrev:
Detlef Reichelt skrev:
Am Montag, 2. Oktober 2006 10:08 schrieb Anders Norrbring: [...]
http://lists.opensuse.org/opensuse-packaging/2006-08/msg00021.html
So... Now it's all set.. I've mirrored fresh, I ran createrepo on it, and then create_package_descr as last step.
Build environment starts to set up, but there are always one file (not the same one every time) that fails to install.. Like this:
fetching bash (475.7 kB) .................................................... ok installing [ 0%] bash-3.1-24.3 (x86_64) .................................... *** failed: ERROR(InstTarget:E_RpmDB_subprocess_failed)[error: unpacking of archive failed on file /usr/share/doc/packages/bash/bash.html;452160a2: cpio: open failed - No such file or directory ] ERROR(InstSrc:E_cancel_media)
Ideas?
Still nobody that can shed some light onto this? My y2pmbuild works just fine with the repo created from the DVD dist of 10.1, but as soon as I enter the repo created from my update mirror, it breaks at every attempt to build.
Check the yast log files. y2pmbuild stores them as .y2log and .y2logRPM in the build root. Alternatively switch to the new build script at http://software.opensuse.org/download/home:/lnussel/SLES_9/repodata/repoview... cu Ludwig -- (o_ Ludwig Nussel //\ SUSE LINUX Products GmbH, Development V_/_ http://www.suse.de/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Ludwig Nussel skrev:
Anders Norrbring wrote:
Anders Norrbring skrev:
Detlef Reichelt skrev:
Am Montag, 2. Oktober 2006 10:08 schrieb Anders Norrbring: [...]
http://lists.opensuse.org/opensuse-packaging/2006-08/msg00021.html So... Now it's all set.. I've mirrored fresh, I ran createrepo on it, and then create_package_descr as last step.
Build environment starts to set up, but there are always one file (not the same one every time) that fails to install.. Like this:
fetching bash (475.7 kB) .................................................... ok installing [ 0%] bash-3.1-24.3 (x86_64) .................................... *** failed: ERROR(InstTarget:E_RpmDB_subprocess_failed)[error: unpacking of archive failed on file /usr/share/doc/packages/bash/bash.html;452160a2: cpio: open failed - No such file or directory ] ERROR(InstSrc:E_cancel_media)
Ideas? Still nobody that can shed some light onto this? My y2pmbuild works just fine with the repo created from the DVD dist of 10.1, but as soon as I enter the repo created from my update mirror, it breaks at every attempt to build.
Check the yast log files. y2pmbuild stores them as .y2log and .y2logRPM in the build root.
Alternatively switch to the new build script at http://software.opensuse.org/download/home:/lnussel/SLES_9/repodata/repoview...
This is what I get in the y2logRPM: 2006-11-05 12:39:23 bash-3.1-24.3.x86_64.patch.rpm install failed rpm output: error: unpacking of archive failed on file /usr/share/doc/packages/bash/bash.html;454dcd6b: cpio: open failed - No such file or directory Not that I know how to get by it... When I look in the RPM (bash-3.1-24.3.x86_64.patch.rpm) the file /usr/share/doc/packages/bash/bash.html is in there. Should I just skip the "patch" RPMs? I'll take a look at the new script as well, is it as competent as the y2pmbuild, or is it "just" a new version of build? -- Anders Norrbring Norrbring Consulting
Anders Norrbring wrote:
This is what I get in the y2logRPM:
2006-11-05 12:39:23 bash-3.1-24.3.x86_64.patch.rpm install failed rpm output: error: unpacking of archive failed on file /usr/share/doc/packages/bash/bash.html;454dcd6b: cpio: open failed - No such file or directory
Not that I know how to get by it... When I look in the RPM (bash-3.1-24.3.x86_64.patch.rpm) the file /usr/share/doc/packages/bash/bash.html is in there.
Should I just skip the "patch" RPMs?
Yes, the old yast2 packagemanager used by y2pmsh can only deal with them as part of YOU.
I'll take a look at the new script as well, is it as competent as the y2pmbuild, or is it "just" a new version of build?
Both. It's supposed to replace y2pmbuild. cu Ludwig -- (o_ Ludwig Nussel //\ SUSE LINUX Products GmbH, Development V_/_ http://www.suse.de/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Ludwig Nussel skrev:
Anders Norrbring wrote:
This is what I get in the y2logRPM:
2006-11-05 12:39:23 bash-3.1-24.3.x86_64.patch.rpm install failed rpm output: error: unpacking of archive failed on file /usr/share/doc/packages/bash/bash.html;454dcd6b: cpio: open failed - No such file or directory
Not that I know how to get by it... When I look in the RPM (bash-3.1-24.3.x86_64.patch.rpm) the file /usr/share/doc/packages/bash/bash.html is in there.
Should I just skip the "patch" RPMs?
Yes, the old yast2 packagemanager used by y2pmsh can only deal with them as part of YOU.
Tried it, didn't help... installing [ 27%] bash-3.1-24.3 (x86_64) .................................... *** failed: ERROR(InstTarget:E_RpmDB_subprocess_failed)[error: unpacking of archive failed on file /usr/share/doc/packages/bash/bash.html;454dcd6b: cpio: open failed - No such file or directory ] ERROR(InstSrc:E_cancel_media) reading RPM database ........................................................ ok -33 packages installed
I'll take a look at the new script as well, is it as competent as the y2pmbuild, or is it "just" a new version of build?
Both. It's supposed to replace y2pmbuild.
I'll grab it and take a look at it. Thanks for the tip!
cu Ludwig
Possibly, some day.. :) -- Anders Norrbring Norrbring Consulting
Ludwig Nussel skrev:
Anders Norrbring wrote:
This is what I get in the y2logRPM:
2006-11-05 12:39:23 bash-3.1-24.3.x86_64.patch.rpm install failed rpm output: error: unpacking of archive failed on file /usr/share/doc/packages/bash/bash.html;454dcd6b: cpio: open failed - No such file or directory
Not that I know how to get by it... When I look in the RPM (bash-3.1-24.3.x86_64.patch.rpm) the file /usr/share/doc/packages/bash/bash.html is in there.
Should I just skip the "patch" RPMs?
Yes, the old yast2 packagemanager used by y2pmsh can only deal with them as part of YOU.
I'll take a look at the new script as well, is it as competent as the y2pmbuild, or is it "just" a new version of build?
Both. It's supposed to replace y2pmbuild.
Okay Ludwig, I've glanced over the package, but I can't quite figure out how to use it in a way that I use y2pmbuild. The /etc/build/dists_common is set up, but how do I initiate the build of packages the way I did with y2pmbuild-10.1? -- Anders Norrbring Norrbring Consulting
Am Sonntag, 5. November 2006 18:13 schrieb Anders Norrbring: [...]
The /etc/build/dists_common is set up, but how do I initiate the build of packages the way I did with y2pmbuild-10.1?
lbuild-10.1 Detlef --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Detlef Reichelt skrev:
Am Sonntag, 5. November 2006 18:13 schrieb Anders Norrbring: [...]
The /etc/build/dists_common is set up, but how do I initiate the build of packages the way I did with y2pmbuild-10.1?
lbuild-10.1
Thanks.. Should've seen that one :) I saw a problem though, I set "plain rpm-md" in the regen_repositary field and I got this in the end of the run: /usr/bin/lbuild: line 232: 18575 Segmentation fault genIS_PLAINcache -f -r "$repository" -- Anders Norrbring Norrbring Consulting
Anders Norrbring wrote:
Detlef Reichelt skrev:
Am Sonntag, 5. November 2006 18:13 schrieb Anders Norrbring: [...]
The /etc/build/dists_common is set up, but how do I initiate the build of packages the way I did with y2pmbuild-10.1?
lbuild-10.1
Thanks.. Should've seen that one :) I saw a problem though, I set "plain rpm-md" in the regen_repositary field and I got this in the end of the run:
/usr/bin/lbuild: line 232: 18575 Segmentation fault genIS_PLAINcache -f -r "$repository"
Someone either needs to debug and fix genIS_PLAINcache or even better write a replacement ... cu Ludwig -- (o_ Ludwig Nussel //\ SUSE LINUX Products GmbH, Development V_/_ http://www.suse.de/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Anders Norrbring skrev:
Detlef Reichelt skrev:
Am Sonntag, 5. November 2006 18:13 schrieb Anders Norrbring: [...]
The /etc/build/dists_common is set up, but how do I initiate the build of packages the way I did with y2pmbuild-10.1?
lbuild-10.1
Thanks.. Should've seen that one :) I saw a problem though, I set "plain rpm-md" in the regen_repositary field and I got this in the end of the run:
/usr/bin/lbuild: line 232: 18575 Segmentation fault genIS_PLAINcache -f -r "$repository"
Now I get it up and running, but without the "plain" repo setting, I guess it's not really needed since I only need the repositary for installations and updates... But, I came to think of another twist, now the directories are created as 10.1-i386, 10.1-x86_64, 10.0-i386, 10.0-x86_64 etc. Can I run 'createrepo' in that parent directory and mix the different versions in the same repositary, or do I have to place all the different versions in separate parents, one for 10.0, one for 10.1, one for SLES etc? Or will the respective version's installation/update routines "know" which directory to access if I place them all in one repositary? -- Anders Norrbring Norrbring Consulting
Am Montag, 6. November 2006 19:43 schrieb Anders Norrbring: [...]
But, I came to think of another twist, now the directories are created as 10.1-i386, 10.1-x86_64, 10.0-i386, 10.0-x86_64 etc. Can I run 'createrepo' in that parent directory and mix the different versions in the same repositary, or do I have to place all the different versions in separate parents, one for 10.0, one for 10.1, one for SLES etc? Or will the respective version's installation/update routines "know" which directory to access if I place them all in one repositary?
i delete the regen-repo in /etc/build/dists_common and set this in /etc/build/dists/$dist For example in /etc/build/dists/10.1: repository="/build/repo/10.1" regen_repository="yum" Then i have an repo for x86 and x86_64 in /build/repo/10.1, it works... ;) Detlef --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Detlef Reichelt skrev:
Am Montag, 6. November 2006 19:43 schrieb Anders Norrbring: [...]
But, I came to think of another twist, now the directories are created as 10.1-i386, 10.1-x86_64, 10.0-i386, 10.0-x86_64 etc. Can I run 'createrepo' in that parent directory and mix the different versions in the same repositary, or do I have to place all the different versions in separate parents, one for 10.0, one for 10.1, one for SLES etc? Or will the respective version's installation/update routines "know" which directory to access if I place them all in one repositary?
i delete the regen-repo in /etc/build/dists_common and set this in /etc/build/dists/$dist
For example in /etc/build/dists/10.1:
repository="/build/repo/10.1" regen_repository="yum"
Then i have an repo for x86 and x86_64 in /build/repo/10.1, it works... ;)
I was thinking the same way, but I'm curious about if it'll work to have one single repo, in a common directory, and will the different versions of SUSE find it's right packages? Not that I "need" that, but I'm curious.. ;) -- Anders Norrbring Norrbring Consulting
Am Dienstag, 7. November 2006 08:21 schrieb Anders Norrbring:
Detlef Reichelt skrev:
Am Montag, 6. November 2006 19:43 schrieb Anders Norrbring: [...]
But, I came to think of another twist, now the directories are created as 10.1-i386, 10.1-x86_64, 10.0-i386, 10.0-x86_64 etc. Can I run 'createrepo' in that parent directory and mix the different versions in the same repositary, or do I have to place all the different versions in separate parents, one for 10.0, one for 10.1, one for SLES etc? Or will the respective version's installation/update routines "know" which directory to access if I place them all in one repositary?
i delete the regen-repo in /etc/build/dists_common and set this in /etc/build/dists/$dist
For example in /etc/build/dists/10.1:
repository="/build/repo/10.1" regen_repository="yum"
Then i have an repo for x86 and x86_64 in /build/repo/10.1, it works... ;)
I was thinking the same way, but I'm curious about if it'll work to have one single repo, in a common directory, and will the different versions of SUSE find it's right packages?
yes, lbuild/smart/yast2 gets the right arch. Detlef --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 2006-11-07 17:15:57 +0100, Detlef Reichelt wrote:
yes, lbuild/smart/yast2 gets the right arch.
smart has known bugs with biarch repositories. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (4)
-
Anders Norrbring -
Detlef Reichelt -
Ludwig Nussel -
Marcus Rueckert