Package name incorrect

Bug #92494 reported by monkeyhelper
6
Affects Status Importance Assigned to Milestone
php-imap (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

On backporting the fiesty version to dapper, the resulting built package is titled :

php5-imap_5.1.2-1_i386.deb

I believe it should be titled :

php5-imap_5.1.2-1ubuntu1_i386.deb

This has caused confusion within my local repository as you recently changed the package name from using build1 to ubuntu1, resulting in an identically titled package filename for two different versions of the package.

Revision history for this message
Lionel Porcheron (lionel.porcheron) wrote :

Could you explain a bit more your problem.

Where does the source come from ? Who built the backport ?

Changed in php-imap:
status: Unconfirmed → Needs Info
Revision history for this message
monkeyhelper (robl) wrote :

/etc/apt/sources.list :

deb-src http://gb.archive.ubuntu.com/ubuntu feisty main restricted
deb-src http://security.ubuntu.com/ubuntu feisty-security universe

debian-builder php5-imap

produces :

php5-imap_5.1.2-1_i386.deb

This was building on Dapper (however I suspect the same problem exists when building on Feisty).

You've changed the package name from :

php5-imap (5.1.2-1build1)

to

php5-imap (5.1.2-1ubuntu1)

However both these 'versions' build to :

php5-imap_5.1.2-1_i386.deb

This seems incorrect to me.

Revision history for this message
Lionel Le Folgoc (mrpouit) wrote :

> /etc/apt/sources.list :
>
> deb-src http://gb.archive.ubuntu.com/ubuntu feisty main restricted
> deb-src http://security.ubuntu.com/ubuntu feisty-security universe

debian-builder behavior is normal: php5-imap is in feisty universe, and didn't get any security issue fixed in feisty-security. So it doesn't exist in "feisty-security universe", and can't be found in feisty (because you only added "main" and "restricted"), therefore debian-builder used your dapper deb-src line.
This is not a bug then, closing the report.

Changed in php-imap:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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