| Summary: | net-misc/dropbox is a persistent rebuild target for python-updater | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Chicago <chicago> |
| Component: | [OLD] Unspecified | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | chicago |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | 'emerge --info' output | ||
Do you have similar output to https://bugs.gentoo.org/show_bug.cgi?id=347861#c0 if you run `python-updater -p -v -v -v' (static linking part)? python-updater is not used for years |
Created attachment 436910 [details] 'emerge --info' output Hello, My system Python version is configured to prefer v2.7, which you can see in the following output from 'eselect python list'. Available Python interpreters, in order of preference: [1] python2.7 [2] python3.4 [3] jython2.7 (fallback) This bug report is about the behavior from python-updater. Repeatedly, python-updater wants to rebuild net-misc/dropbox. Initially, I was running with the stable version, net-misc/dropbox-2.10.2 and python-updater wanted to rebuild dropbox so I rebuilt it. Then, I invoked python-updater a second time to see if it was "satisfied" and was curious to note it wanted to rebuild net-misc/dropbox-2.10.2 once more. I figured, meh, let's keyword the package and install net-misc/dropbox-5.3.18 and see what happens. So, after upgrading to the latest ~amd64 version of net-misc/dropbox, I ran python-updater and it wanted to rebuild net-misc/dropbox yet again and I figured "okay" go for it. Once python-updater was done I thought, there you have had your chance to rebuild it for whatever reason, now I wanted to be able to invoke python-updater again and not see net-misc/dropbox on the list of packages (or any packages for that matter) requesting to be rebuilt. It is worth mentioning, the *only* package here which is being marked for rebuild is net-misc/dropbox. My emerge --info output is attached for your reference. Please help determine what may be wrong with either my configuration or the package's ebuild leading to this behavior and try to reproduce it on your end. Kind Regards, -Chicago