[SRU]: python-pam contains no binaries (edgy)

Bug #84732 reported by Laurent Bigonville
8
Affects Status Importance Assigned to Milestone
python-pam (Ubuntu)
Fix Released
Undecided
Unassigned
Edgy
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: python-pam

Currently the python-pam package contains no binaries at all. Rebuilding it does the trick

See original bug #69967

Revision history for this message
Laurent Bigonville (bigon) wrote :
Revision history for this message
Laurent Bigonville (bigon) wrote :
StefanPotyra (sistpoty)
description: updated
Revision history for this message
StefanPotyra (sistpoty) wrote :

Hi,

python-pam is in main:
* unsubscribing motu-sru
* subscribing ubuntu-sru instead.

(since I've been looking at the debdiff, here just a comment:
Version number should probably be 0.4.2-10.4build0.1~proposed1.)

Cheers,
    Stefan.

Revision history for this message
Martin Pitt (pitti) wrote :

Was already rebuilt in Feisty, closing Feisty task.

Changed in python-pam:
status: Unconfirmed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

I sponsored the package and fixed the version number to be 0.4.2-10.4build0.1~proposed1, since Feisty has -10.4build1.

Please go ahead with QA testing.

Changed in python-pam:
status: Unconfirmed → Fix Committed
Revision history for this message
Christian Holtje (docwhat) wrote :

I'm confused. Is this bug or is bug #69967 the bug for Edgy? The problem is that **edgy** has a totally useless python-pam package.

Ciao!

Revision history for this message
Laurent Bigonville (bigon) wrote :

This should be fixed now in edgy too. The package is in edgy-proposed now

Revision history for this message
Michael Vogt (mvo) wrote :

I verified this package with the following steps:

1. install python-pam from edgy
2. dpkg -L python-pam showed *no* python files

3. installed python-pam from edgy-proposed
4. dpkg -L python-pam shows python modules for both python2.4 and python2.5

HOWEVER:
python -c 'import PAMmodule'
gives me a error:
ImportError: dynamic module does not define init function (initPAMmodule)

Please clarify if this is expected behaviour. I will not mark this verification done until that is clarified.

Cheers,
 Michael

Revision history for this message
Christian Holtje (docwhat) wrote :

PAMmodule is the wrong bit to import. That's the binary parts.

This is a legit test case:
# python2.5 -c 'import PAM; print "found",len(dir(PAM))'
found 55

Ciao!

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks a lot!

This works now indeed, I will mark the bug as verification-done.

Revision history for this message
Martin Pitt (pitti) wrote :

I did a no-change upload to edgy-updates and accepted it.

Changed in python-pam:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.