Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 478242 - dev-python/django-ldapdb - PV=0.2 is wrong?
Summary: dev-python/django-ldapdb - PV=0.2 is wrong?
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: All All
: Normal normal (vote)
Assignee: Ian Delaney (RETIRED)
URL: https://github.com/jlaine/django-ldap...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-26 15:18 UTC by Dmitri Bogomolov
Modified: 2013-07-30 13:27 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitri Bogomolov 2013-07-26 15:18:21 UTC 
`version=0.1.0` in setup.py on github.com (http://opensource.bolloretelecom.eu/projects/django-ldapdb/ redirects to https://github.com/jlaine/django-ldapdb)

Reproducible: Always
Comment 1 Ian Delaney (RETIRED) gentoo-dev 2013-07-30 13:14:52 UTC 
I am in doubt as to what the problem is.

testuser@archtester ~/cvsPortage/gentoo-x86/dev-python/django-ldapdb $ ls
ChangeLog  django-ldapdb-0.1.0_p20120424.ebuild     django-ldapdb-0.1.0_p20130712.ebuild  metadata.xml
CVS        django-ldapdb-0.1.0_p20120424-r1.ebuild  Manifest

(In reply to Dmitri Bogomolov from comment #0)
> `version=0.1.0` in setup.py on github.com
> (http://opensource.bolloretelecom.eu/projects/django-ldapdb/ redirects to
> https://github.com/jlaine/django-ldapdb)
> 
> Reproducible: Always

For a day or so 0.1.0_p20130712.ebuild was 0.2.0_p20130712.ebuild.  Is it that your portage tree is updated at that point leading you to cite PV=0.2?  An emerge --sync will fix that up.

http://opensource.bolloretelecom.eu/projects/django-ldapdb indeed does redirect to https://github.com/jlaine/django-ldapdb but I for the life o' me I can't see what that has to do with version=0.1.0` in setup.py on github.com.  These must be to consecutive and unrelated statements.  

This package is an oddity because it's present only by virtue of the 2 snapshots made at the dates 20120424 & 20130712 which I detest because they read backwards. It has no releases and its version is set at 0.1.0 in setup.py.
Both your initial Summary: PV=0.2 is wrong for dev-python/django-ldapd
and the edited one are absent of the version which is basically making the bug un-understandable.
Comment 2 Dmitri Bogomolov 2013-07-30 13:27:24 UTC 
(In reply to Ian Delaney from comment #1)
> I am in doubt as to what the problem is.
> 
> testuser@archtester ~/cvsPortage/gentoo-x86/dev-python/django-ldapdb $ ls
> ChangeLog  django-ldapdb-0.1.0_p20120424.ebuild    
> django-ldapdb-0.1.0_p20130712.ebuild  metadata.xml
> CVS        django-ldapdb-0.1.0_p20120424-r1.ebuild  Manifest
> 
> (In reply to Dmitri Bogomolov from comment #0)
> > `version=0.1.0` in setup.py on github.com
> > (http://opensource.bolloretelecom.eu/projects/django-ldapdb/ redirects to
> > https://github.com/jlaine/django-ldapdb)
> > 
> > Reproducible: Always
> 
> For a day or so 0.1.0_p20130712.ebuild was 0.2.0_p20130712.ebuild.  Is it
> that your portage tree is updated at that point leading you to cite PV=0.2? 
> An emerge --sync will fix that up.

You right. It was fixed 10 days before reported (strange, I usually watch http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86 before report)

> http://opensource.bolloretelecom.eu/projects/django-ldapdb indeed does
> redirect to https://github.com/jlaine/django-ldapdb but I for the life o' me
> I can't see what that has to do with version=0.1.0` in setup.py on
> github.com.  These must be to consecutive and unrelated statements.  

Trere is an URL in this issue. I have mentioned redirect to prove that I look for the version in the right place: at HOMEPAGE.