| 2011-04-28 18:21:02 |
WangLu |
bug |
|
|
added bug |
| 2011-04-28 18:21:27 |
WangLu |
description |
The title may be confusing, but let me make this clear:
Suppose I upload a source package P to PPA, which can be built for one architecture but fails for another. However in this case PPA would accept it for all the architectures.
One example I've found is https://launchpad.net/~matthaeus123/+archive/mrw-gimp-svn
Currently for the 'gimp' package, version 2.7.3-2011042102~nn is available for i386, but not for amd64 due to build failure.
'apt-cache showpkg' shows the installed version 2.7.3-2011031601~nn, and 'apt-cache showsrc' shows the latest source version 2.7.3-2011042102~nn. So there would be two problem
1. 'apt-get source' will download a source package that won't builld.
2. 'apt-build build' won't find a proper source package because of the versions mismatch.
(I guess it is the repository that should ensure the source packages are buildable, otherwise this would be a bug of apt-build) |
The title may be confusing, but let me make this clear:
Suppose I upload a source package P to PPA, which can be built for one architecture but fails for another. However in this case PPA would accept it for all the architectures.
One example I've found is https://launchpad.net/~matthaeus123/+archive/mrw-gimp-svn
Currently for the 'gimp' package, version 2.7.3-2011042102~nn is available for i386, but not for amd64 due to build failure.
'apt-cache showpkg' shows the installed version 2.7.3-2011031601~nn, and 'apt-cache showsrc' shows the latest source version 2.7.3-2011042102~nn. So there would be two problems
1. 'apt-get source' will download a source package that won't builld.
2. 'apt-build build' won't find a proper source package because of the versions mismatch.
(I guess it is the repository that should ensure the source packages are buildable, otherwise this would be a bug of apt-build) |
|
| 2011-04-28 18:21:45 |
WangLu |
description |
The title may be confusing, but let me make this clear:
Suppose I upload a source package P to PPA, which can be built for one architecture but fails for another. However in this case PPA would accept it for all the architectures.
One example I've found is https://launchpad.net/~matthaeus123/+archive/mrw-gimp-svn
Currently for the 'gimp' package, version 2.7.3-2011042102~nn is available for i386, but not for amd64 due to build failure.
'apt-cache showpkg' shows the installed version 2.7.3-2011031601~nn, and 'apt-cache showsrc' shows the latest source version 2.7.3-2011042102~nn. So there would be two problems
1. 'apt-get source' will download a source package that won't builld.
2. 'apt-build build' won't find a proper source package because of the versions mismatch.
(I guess it is the repository that should ensure the source packages are buildable, otherwise this would be a bug of apt-build) |
The title may be confusing, but let me make this clear:
Suppose I upload a source package P to PPA, which can be built for one architecture but fails for another. However in this case PPA would accept it for all the architectures.
One example I've found is https://launchpad.net/~matthaeus123/+archive/mrw-gimp-svn
Currently for the 'gimp' package, version 2.7.3-2011042102~nn is available for i386, but not for amd64 due to build failure.
'apt-cache showpkg' shows the installed version 2.7.3-2011031601~nn, and 'apt-cache showsrc' shows the latest source version 2.7.3-2011042102~nn. So there would be two problems
1. 'apt-get source' will download a source package that won't build.
2. 'apt-build build' won't find a proper source package because of the versions mismatch.
(I guess it is the repository that should ensure the source packages are buildable, otherwise this would be a bug of apt-build) |
|
| 2011-04-28 19:30:40 |
Curtis Hovey |
launchpad-buildd: status |
New |
Triaged |
|
| 2011-04-28 19:30:42 |
Curtis Hovey |
launchpad-buildd: importance |
Undecided |
Low |
|
| 2011-04-28 20:31:54 |
Julian Edwards |
affects |
launchpad-buildd |
launchpad |
|
