Hello,
On Tue, 11 Mar 2008, Alexander Schmehl wrote:
> Am 11.3.2008 schrieb "Charles Plessy"
> <[EMAIL PROTECTED]>:
>
> >I am wondering how to find the origin of a binary package: if it was
> >built on a buildd or the machine of a developper, and in this case, who
> >uploaded it.
>
> Well... If
Am 11.3.2008 schrieb "Charles Plessy"
<[EMAIL PROTECTED]>:
>I am wondering how to find the origin of a binary package: if it was
>built on a buildd or the machine of a developper, and in this case, who
>uploaded it.
Well... If it was build by an buildd, it is mentioned in the build log.
E.g. kli
On Tue, Mar 11, 2008 at 06:38:05PM +0900, Charles Plessy wrote:
>Nevertheless, trying to figure out what happens to the .arch.changes
>file made me curious. So if there is answer, I am still interested in.
You could see them briefly at http://incoming.debian.org/
I'm not aware if the ftpmaster te
Le Tue, Mar 11, 2008 at 08:27:22PM +1100, Aníbal Monsalve Salazar a écrit :
> I guess the arch is mips.
Hi Aníbal,
good guess :)
Actually, there have been also some mipsel uploads some weeks ago.
Thanks for the help! In the meantime I learnt how to use qemu, so I
should be able to deal with the
On Tue, Mar 11, 2008 at 05:40:15PM +0900, Charles Plessy wrote:
>I am wondering how to find the origin of a binary package:
You didn't mention the package name and the arch.
I guess the arch is mips.
>if it was built on a buildd or the machine of a developper, and
>in this case, who uploaded it.
Dear mentors,
I am wondering how to find the origin of a binary package: if it was
built on a buildd or the machine of a developper, and in this case, who
uploaded it. I did not manage to find this information in the
Developper's reference nor on the Debian website
(http://www.debian.org/devel/bui
6 matches
Mail list logo
