Incorrect "port echo maintainer:vinc17" output

[vinc17@…]

"port echo maintainer:vinc17" gives libgtkhtml in the list, even though I've done a portindex after dropping the maintainership (note: I no longer have this port installed).

"port info libgtkhtml" says

Maintainers:          nomaintainer@macports.org

as expected.

[jmroot (Joshua Root)]

Can't reproduce.

% port echo maintainer:vinc17
dvi2bitmap                      
gmp-ecm                         
latexmk                         
liferea                         
lzip                            
mairix                          
mpfr                            
optipng                         
p5-appconfig-std                
p5-compress-raw-bzip2           
p5-math-mpfr                    
p5-moosex-multiinitarg          
p5-net-dict                     
p5-net-oauth                    
p5-net-twitter                  
p5-news-nntpclient              
p5-ogg-vorbis-header-pureperl   
p5-term-gnuplot                 
pari                            
stardict-xmlittre               
tetex-frogg                     
texinfo                         
tin-recent                      
urlview                         
vttest

[ryandesign (Ryan Carsten Schmidt)]

When something like this happens to me, I usually find that at some point I had made a copy of the port directory, and that got indexed instead. Even if you later delete that directory, it's still in the port index. Try deleting both PortIndex files and letting MacPorts recreate it from scratch.

[jmroot (Joshua Root)]

Touching the Portfile is a lot quicker.

[ryandesign (Ryan Carsten Schmidt)]

Vincent, does that resolve the issue for you?

[vinc17@…]

The problem was due to /opt/local/var/macports/sources/rsync.macports.org/release/ports/PortIndex, which wasn't updated by "sudo port selfupdate" apparently. Is this normal?

[ryandesign (Ryan Carsten Schmidt)]

PortIndex is updated by MacPorts, either by retrieving it from the rsync server if you're syncing using rsync, or by generating it locally if you're syncing using svn.

[vinc17@…]

In my sources, I have both a rsync source (IIRC, mainly for base) and a svn source. As I've said in Comment 5, the problem was due to the rsync one (FYI, I had run portindex in the svn source). But a "sudo port selfupdate" (which does a rsync, doesn't it?) didn't solve the problem. Now, perhaps the Portindex hadn't been updated yet by the rsync server.

[jmroot (Joshua Root)]

If you have the rsync source listed first, and the rsync server hadn't yet picked up the update, that's normal.