Bug 557862

Summary:	app-portage/gentoolkit-dev - imlate --maintainer no longer works
Product:	Portage Development	Reporter:	Michael Palimaka (kensington) <kensington>
Component:	Tools	Assignee:	Portage Tools Team <tools-portage>
Status:	RESOLVED INVALID
Severity:	normal	CC:	fatzer2, itumaykin+gentoo
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Michael Palimaka (kensington) gentoo-dev

2015-08-15 16:59:57 UTC

Ever since the git migration, imlate no longer works:

$ imlate -H kde
Generated on: Sat Aug 15 16:59:10 UTC 2015
============================================================
0 Stable and 0 Keyword(~) candidates for 'gentoo' on 'amd64'
============================================================

category/package[:SLOT]                 our version         best version
------------------------------------------------------------------------
$

Comment 1 Michael Palimaka (kensington) gentoo-dev

2017-03-04 01:05:47 UTC

This is still an issue:

$ imlate -M kensington@gentoo.org
Generated on: Sat Mar 04 01:05:00 UTC 2017
============================================================
0 Stable and 0 Keyword(~) candidates for 'gentoo' on 'amd64'
============================================================

category/package[:SLOT]                 our version         best version
------------------------------------------------------------------------

Comment 2 Michael Palimaka (kensington) gentoo-dev

2017-03-04 01:38:16 UTC

Actually, I suspect this may be caused by recent tree-wide commits causing mtime to be updated. In that case, it's unfortunate but I don't think there's anything that can be done.

Comment 3 Fat-Zer 2017-03-28 04:13:12 UTC

May this be related (duplicate?) to #610944?

Comment 4 Coacher 2017-03-28 06:22:37 UTC

(In reply to Fat-Zer from comment #3)
> May this be related (duplicate?) to #610944?
No, imlate doesn't crash. It just gives no stabilization candidates.

Comment 5 Michael Palimaka (kensington) gentoo-dev

2017-06-11 05:44:58 UTC

This is definitely caused by tree-wide commits.