Summary: | bzr.eclass - bzr: ERROR: Not a branch: "/usr/portage_impala/distfiles/bzr-src/kicad/.bzr/branch/": location is a repository. (was: sci-electronics/kicad-20120119_p3256) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
Component: | Current packages | Assignee: | bazaar+obsolete |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | emacs |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
/etc/make.conf
/var/lib/layman/make.conf |
Description
Juergen Rose
2012-02-19 10:33:26 UTC
Now I hit the issue at the next system. It seems me, that the error description in the original posting is shown at the second and higher attempt to get
kicad-20120119_p3256. During the first attempt there is an other message:
>>> Emerging (1 of 16) sci-electronics/kicad-20120119_p3256
>>> Unpacking source...
* bzr branch start -->
* repository: lp:~kicad-testing-committers/kicad/testing => /usr/portage_moose/distfiles/bzr-src/kicad
You have not informed bzr of your Launchpad ID, and you must do this to
write to Launchpad or access private data. See "bzr help launchpad-login".
(In reply to comment #1) > You have not informed bzr of your Launchpad ID, and you must do this to > write to Launchpad or access private data. See "bzr help launchpad-login". This part is not an error, don't worry about it. About your real error, you are doing something funny with your portage setup. What makes me say that is that your DISTDIR is set to /usr/portage/distfiles which is the default and is OK, but you're somehow having portage store the bzr branch directory in /usr/portage_impala/distfiles. Can you please tell us more about what you're doing? Showing us your make.conf might help. Denis. Created attachment 302667 [details]
/etc/make.conf
Created attachment 302669 [details]
/var/lib/layman/make.conf
BTW. I have usually mounted a partition at /usr/portage_$(hostname) on my systems and /usr/portage is a link to /usr/portage_$(hostname), e.g.: root@impala:/root(50)# df | grep /usr/portage_impala$ /dev/mapper/vg0-portage 4142882 313537 3619630 8% /usr/portage_impala root@impala:/root(51)# ll /usr/portage lrwxrwxrwx 1 root root 14 Mar 12 2011 /usr/portage -> portage_impala/ So you are indeed doing something funny with your portage setup. And this is apparently causing an issue with bzr.eclass. I'm reassigning this to the maintainers of the eclass since kicad is just a consumer of it. Maybe they can help you. Denis. Hi Denis, what is funny with my portage setup? Juergen Fails with similar problem here, see appended traceback. Relevant make.conf entries: PORTAGE_TMPDIR=/usr/local/tmp DISTDIR=/usr/local/tmp/portage/distfiles PKGDIR=/usr/local/tmp/portage/packages /usr/local is a mount to other partition. I've been using this setup for a couple of years and never had problems, so I doubt the problem is related to this. >>> Verifying ebuild manifests >>> Emerging (1 of 1) sci-electronics/kicad-20120119_p3256 >>> Failed to emerge sci-electronics/kicad-20120119_p3256, Log file: >>> '/usr/local/tmp/portage/sci-electronics/kicad-20120119_p3256/temp/build.log' >>> Jobs: 0 of 1 complete, 1 failed Load avg: 0.46, 0.19, 0.16 * Package: sci-electronics/kicad-20120119_p3256 * Repository: gentoo * Maintainer: sci-electronics@gentoo.org * USE: amd64 elibc_glibc kernel_linux multilib userland_GNU * FEATURES: sandbox * bzr pull start --> * repository: lp:~kicad-testing-committers/kicad/testing bzr: ERROR: Not a branch: "/usr/local/tmp/portage/distfiles/bzr-src/kicad/.bzr/branch/": location is a repository. * ERROR: sci-electronics/kicad-20120119_p3256 failed (unpack phase): * bzr.eclass: can't pull from lp:~kicad-testing-committers/kicad/testing * * Call stack: * ebuild.sh, line 85: Called src_unpack * environment, line 3077: Called bzr_fetch * environment, line 718: Called bzr_update 'lp:~kicad-testing-committers/kicad/testing' '/usr/local/tmp/portage/distfiles/bzr-src/kicad' * environment, line 760: Called die * The specific snippet of code: * ${EBZR_UPDATE_CMD} ${EBZR_OPTIONS} "${repo_uri}" || die "${EBZR}: can't pull from ${repo_uri}"; * * If you need support, post the output of 'emerge --info =sci-electronics/kicad-20120119_p3256', * the complete build log and the output of 'emerge -pqv =sci-electronics/kicad-20120119_p3256'. * The complete build log is located at '/usr/local/tmp/portage/sci-electronics/kicad-20120119_p3256/temp/build.log'. * The ebuild environment file is located at '/usr/local/tmp/portage/sci-electronics/kicad-20120119_p3256/temp/environment'. * S: '/usr/local/tmp/portage/sci-electronics/kicad-20120119_p3256/work/kicad-20120119_p3256' I just deleted /usr/local/tmp/portage and tried to emerge kicad again, it worked. I know nothing about bzr but it looks like that if you interrupt an emerge while it is bzr fetching, when you rerun emerge again bzr will failed with the above mentioned error. I don't have any /usr/local/tmp directory. If I remove /var/tmp/portage/sci-electronics/kicad-20120119_p3256 and try to reemerge kicad, I get the old error. Reemerging bzr did not improve anything. Almost one month later, any news? (In reply to comment #12) > Almost one month later, any news? Sorry for the delay...little kids can keep you occupied. Get me a paid job working full time on Gentoo and I will fix bugs faster, promised. :) Let's start the standard procedure: Which Bazaar version? Is 2.5 also affected (I bumped it in between)? Does removing /usr/portage/distfiles/bzr_src/kicad* help? I have dev-vcs/bzr-2.5.0. root@moose:/root(10)# emerge -pvD bzr These are the packages that would be merged, in order: \Calculating dependencies... done! [ebuild R ] dev-vcs/bzr-2.5.0 USE="curl doc sftp -test" 0 kB I do not have any /usr/portage/distfiles/bzr_src/kicad* files. root@moose:/root(12)# ll /usr/portage/distfiles/bzr_src/kicad* /bin/ls: cannot access /usr/portage/distfiles/bzr_src/kicad*: No such file or directory I have only the following files: root@moose:/root(13)# ll /usr/portage/distfiles/kicad* -rw-rw-r-- 1 portage portage 44487272 Oct 1 2010 /usr/portage/distfiles/kicad-doc-20100505_p2356.tar.xz -rw-rw-r-- 1 portage portage 533260 Oct 1 2010 /usr/portage/distfiles/kicad-examples-20100505_p2356.tar.xz -rw-rw-r-- 1 portage portage 11803780 Oct 1 2010 /usr/portage/distfiles/kicad-library-20100505_p2356.tar.xz -rw-rw-r-- 1 portage portage 4359004 Oct 1 2010 /usr/portage/distfiles/kicad-sources-20100505_p2356.tar.xz I removed the /usr/portage/distfiles/kicad* files and tried once more to emerge kicad. It fails with the old error: root@moose:/root(15)# emerge -uvDN kicad These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] sci-electronics/kicad-20120119_p3256 [20100505_p2356] USE="doc examples python -debug -dev-doc -minimal" 0 kB Total: 1 package (1 upgrade), Size of downloads: 0 kB WARNING: One or more updates have been skipped due to a dependency conflict: net-misc/curl:0 (net-misc/curl-7.25.0-r1::gentoo, ebuild scheduled for merge) conflicts with net-misc/curl[ssl,nss,-gnutls] required by (net-libs/liboauth-0.9.6::gentoo, installed) >>> Verifying ebuild manifests >>> Emerging (1 of 1) sci-electronics/kicad-20120119_p3256 >>> Unpacking source... * bzr pull start --> * repository: lp:~kicad-testing-committers/kicad/testing bzr: ERROR: Not a branch: "/usr/portage_moose/distfiles/bzr-src/kicad/.bzr/branch/": location is a repository. * ERROR: sci-electronics/kicad-20120119_p3256 failed (unpack phase): * bzr.eclass: can't pull from lp:~kicad-testing-committers/kicad/testing I have /usr/portage_moose/distfiles/bzr-src/kicad directory: root@moose:/root(22)# ls -la /usr/portage/distfiles/bzr-src/kicad total 12 drwxr-sr-x 3 root portage 4096 Feb 20 11:18 . drwxr-sr-x 3 root portage 4096 Feb 20 11:18 .. drwxr-sr-x 4 root portage 4096 Feb 20 11:18 .bzr I removed this directory too: root@moose:/root(23)# rm -r /usr/portage/distfiles/bzr-src/kicad root@moose:/root(24)# emerge -uvDN kicad These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] sci-electronics/kicad-20120119_p3256 [20100505_p2356] USE="doc examples python -debug -dev-doc -minimal" 0 kB Total: 1 package (1 upgrade), Size of downloads: 0 kB ... >>> Verifying ebuild manifests >>> Emerging (1 of 1) sci-electronics/kicad-20120119_p3256 >>> Unpacking source... * bzr branch start --> * repository: lp:~kicad-testing-committers/kicad/testing => /usr/portage_moose/distfiles/bzr-src/kicad bzr: ERROR: Certificate error: hostname '10.101.10.254' doesn't match either of '*.launchpad.net', 'launchpad.net' * ERROR: sci-electronics/kicad-20120119_p3256 failed (unpack phase): * bzr.eclass: can't branch from lp:~kicad-testing-committers/kicad/testing * * Call stack: 10.101.10.254 is our proxy. I can check this evening, if I am at home, whether the removal of /usr/portage_moose/distfiles/bzr-src/kicad helps there to solve the problem. Regards During the test without firewall the installation worked on two systems and failed on one system with: root@condor:/root(17)# ll -la /usr/portage/distfiles/bzr-src/kicad total 12 drwxr-sr-x 3 root portage 4096 Apr 17 00:45 ./ drwxr-sr-x 5 root portage 4096 Apr 17 00:45 ../ drwxr-sr-x 5 root portage 4096 Apr 17 01:38 .bzr/ root@condor:/root(18)# rm -r /usr/portage/distfiles/bzr-src/kicad root@condor:/root(19)# ll -la /usr/portage/distfiles/bzr-src/kicad /bin/ls: cannot access /usr/portage/distfiles/bzr-src/kicad: No such file or directory root@condor:/root(20)# emerge -uvDN kicad These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] sci-electronics/kicad-20120119_p3256 [20100505_p2356] USE="doc examples python -debug -dev-doc -minimal" 0 kB Total: 1 package (1 upgrade), Size of downloads: 0 kB WARNING: One or more updates have been skipped due to a dependency conflict: net-misc/curl:0 (net-misc/curl-7.25.0-r1::gentoo, ebuild scheduled for merge) conflicts with net-misc/curl[ssl,nss,-gnutls] required by (net-libs/liboauth-0.9.6::gentoo, installed) >>> Verifying ebuild manifests >>> Emerging (1 of 1) sci-electronics/kicad-20120119_p3256 >>> Unpacking source... * bzr branch start --> * repository: lp:~kicad-testing-committers/kicad/testing => /usr/portage_condor/distfiles/bzr-src/kicad You have not informed bzr of your Launchpad ID, and you must do this to write to Launchpad or access private data. See "bzr help launchpad-login". Branched 3517 revisions. * exporting ... * revision 3256 is now in /var/tmp/portage/sci-electronics/kicad-20120119_p3256/work/kicad-20120119_p3256 * bzr pull start --> * repository: lp:~kicad-lib-committers/kicad/library You have not informed bzr of your Launchpad ID, and you must do this to write to Launchpad or access private data. See "bzr help launchpad-login". http://bazaar.launchpad.net/~kicad-lib-committers/kicad/library is permanently redirected to http://bazaar.launchpad.net/~kicad-lib-committers/kicad/library/changes You have not informed bzr of your Launchpad ID, and you must do this to write to Launchpad or access private data. See "bzr help launchpad-login". No revisions or tags to pull. * exporting ... * revision before:2012-01-19,23:59:59 is now in /var/tmp/portage/sci-electronics/kicad-20120119_p3256/work/kicad-20120119_p3256/kicad-library * bzr pull start --> * repository: lp:~kicad-developers/kicad/doc bzr: ERROR: Not a branch: "/usr/portage_condor/distfiles/bzr-src/kicad-doc/.bzr/branch/": location is a repository. * ERROR: sci-electronics/kicad-20120119_p3256 failed (unpack phase): * bzr.eclass: can't pull from lp:~kicad-developers/kicad/doc * * Call stack: * ebuild.sh, line 85: Called src_unpack * environment, line 3212: Called bzr_fetch * environment, line 825: Called bzr_update 'lp:~kicad-developers/kicad/doc' '/usr/portage_condor/distfiles/bzr-src/kicad-doc' * environment, line 867: Called die * The specific snippet of code: * ${EBZR_UPDATE_CMD} ${EBZR_OPTIONS} "${repo_uri}" || die "${EBZR}: can't pull from ${repo_uri}"; * * If you need support, post the output of 'emerge --info =sci-electronics/kicad-20120119_p3256', * the complete build log and the output of 'emerge -pqv =sci-electronics/kicad-20120119_p3256'. * The complete build log is located at '/var/tmp/portage/sci-electronics/kicad-20120119_p3256/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sci-electronics/kicad-20120119_p3256/temp/environment'. * S: '/var/tmp/portage/sci-electronics/kicad-20120119_p3256/work/kicad-20120119_p3256' >>> Failed to emerge sci-electronics/kicad-20120119_p3256, Log file: >>> '/var/tmp/portage/sci-electronics/kicad-20120119_p3256/temp/build.log' root@condor:/root(21)# qlist -Iv bzr dev-vcs/bzr-2.5.0 I repeat the attempt to install kicad-20120119_p3256 on condor some times. The fourth try of: 1004 ll -la /usr/portage/distfiles/bzr-src/kicad 1005 rm -r /usr/portage/distfiles/bzr-src/kicad 1006 ll -la /usr/portage/distfiles/bzr-src/kicad 1007 emerge -uvDN kicad seems to work. I see now: * repository: lp:~kicad-testing-committers/kicad/testing => /usr/portage_condor/distfiles/bzr-src/kicad You have not informed bzr of your Launchpad ID, and you must do this to write to Launchpad or access private data. See "bzr help launchpad-login". 61916kB 0kB/s \ Fetching revisions:Inserting stream:Estimate 80136/81855 What I still don't understand is, that the emerge time of kicad is multiplied by a factor between 6 and 60: root@impala:/usr/src(33)# genlop -t kicad * sci-electronics/kicad Mon Mar 28 18:08:41 2011 >>> sci-electronics/kicad-20100505_p2356 merge time: 3 minutes and 31 seconds. Tue Apr 17 03:45:49 2012 >>> sci-electronics/kicad-20120119_p3256 merge time: 3 hours and 36 seconds. root@caiman:/usr/src(41)# genlop -t kicad * sci-electronics/kicad Tue Jan 25 19:05:36 2011 >>> sci-electronics/kicad-20100505_p2356 merge time: 3 minutes and 14 seconds. Tue Apr 17 03:44:39 2012 >>> sci-electronics/kicad-20120119_p3256 merge time: 2 hours, 59 minutes and 28 seconds. root@lynx:/root(9)# genlop -t kicad * sci-electronics/kicad Sun Jun 20 16:49:29 2010 >>> sci-electronics/kicad-20100314_p2456 merge time: 17 minutes and 38 seconds. Sat Oct 2 17:57:55 2010 >>> sci-electronics/kicad-20100505_p2356 merge time: 19 minutes and 1 second. Tue Apr 17 10:45:53 2012 >>> sci-electronics/kicad-20120119_p3256 merge time: 2 hours, 11 minutes and 33 seconds. The largest part of this emerge time seems to be the time of transfering data, at lynx I needed two hours to transfer the data. There I saw the following: You have not informed bzr of your Launchpad ID, and you must do this to write to Launchpad or access private data. See "bzr help launchpad-login". 644208kB 13kB/s / Fetching revisions:Finishing stream Branched 328 revisions. It looks, whether 644 MB has been transferred, but I find only about 121 MB in the /usr/portage/distfiles/bzr-src/kicad directory: rose@lynx:/home/rose(8)$ du -s /usr/portage/distfiles/bzr-src/kicad/.bzr/* 4 /usr/portage/distfiles/bzr-src/kicad/.bzr/README 24 /usr/portage/distfiles/bzr-src/kicad/.bzr/branch 4 /usr/portage/distfiles/bzr-src/kicad/.bzr/branch-format 4 /usr/portage/distfiles/bzr-src/kicad/.bzr/branch-lock 121264 /usr/portage/distfiles/bzr-src/kicad/.bzr/repository Could anybody enlighten me? (In reply to comment #16) > I repeat the attempt to install kicad-20120119_p3256 on condor some times. > The fourth try of: > > 1004 ll -la /usr/portage/distfiles/bzr-src/kicad > 1005 rm -r /usr/portage/distfiles/bzr-src/kicad > 1006 ll -la /usr/portage/distfiles/bzr-src/kicad > 1007 emerge -uvDN kicad > > seems to work. I see now: > > * repository: lp:~kicad-testing-committers/kicad/testing => > /usr/portage_condor/distfiles/bzr-src/kicad > You have not informed bzr of your Launchpad ID, and you must do this to > write to Launchpad or access private data. See "bzr help launchpad-login". > 61916kB 0kB/s \ Fetching revisions:Inserting stream:Estimate 80136/81855 I was wrong with the hope that 'emerge kicad' works now. After one day 'emerge kicad' stands at the same point: 61916kB 0kB/s \ Fetching revisions:Inserting stream:Estimate 80136/81855 I encountered the same problem and error message. I could work it around successfully by removing /usr/portage/distfiles/bzr-src/kicad and re-emerging the package. I cannot reproduce the problem. Both initial branching and updating work fine for me. So, could to test if this is still an issue? Maybe after applying the recipe from comment 18. |