On 12-01-04 at 12:26pm, Barak A. Pearlmutter wrote:
> > How can the Debian project rest assured that that the binary indeed
> > is (only!) unpacking itself when executed?
>
> > Also, that it is the case for _every_ new upstream release, not only
> > once when you cared to investigate closely.
>
> How can the Debian project rest assured that that the binary indeed
> is (only!) unpacking itself when executed?
> Also, that it is the case for _every_ new upstream release, not only
> once when you cared to investigate closely.
Although that is a serious issue, *exactly* the same issue is pre
On Wed, Jan 4, 2012 at 12:52 PM, Jonas Smedegaard wrote:
> On 12-01-04 at 12:42pm, Daniel Svensson wrote:
>> On Wed, Jan 4, 2012 at 12:34 PM, Jonas Smedegaard wrote:
>> > I believe you did not answer my question: I did not ask how the
>> > Debian project can verify later on, but how it can rest a
On 12-01-04 at 12:42pm, Daniel Svensson wrote:
> On Wed, Jan 4, 2012 at 12:34 PM, Jonas Smedegaard wrote:
> > I believe you did not answer my question: I did not ask how the
> > Debian project can verify later on, but how it can rest assured that
> > this verification have already been done for
On Wed, Jan 4, 2012 at 12:34 PM, Jonas Smedegaard wrote:
> I believe you did not answer my question: I did not ask how the Debian
> project can verify later on, but how it can rest assured that this
> verification have already been done for packages using waf.
Which is why I mentioned it's 1.6.7
On 12-01-04 at 12:22pm, Daniel Svensson wrote:
> On Wed, Jan 4, 2012 at 12:18 PM, Jonas Smedegaard wrote:
> >> As I mentioned, this is a question of a compressed file, so sure
> >> it's binary encoded, but when you execute ./waf, it will decompress
> >> into the ".waf-1.6.7-b271784c448ab906d5606
On Wed, Jan 4, 2012 at 12:18 PM, Jonas Smedegaard wrote:
>> As I mentioned, this is a question of a compressed file, so sure it's
>> binary encoded, but when you execute ./waf, it will decompress into
>> the ".waf-1.6.7-b271784c448ab906d5606267fb7f92c0" directory in the top
>> level directory.
>
>
On 12-01-04 at 10:37am, Daniel Svensson wrote:
> On Tue, Jan 3, 2012 at 11:03 PM, Debian Bug Tracking System
> wrote:
> > Bug #654512 [xmms2] postler: doesn't contain source for waf binary code
> > Changed Bug title to 'Doesn't contain source for waf binary code' from
> > 'postler: doesn't contai
On Wed, Jan 4, 2012 at 10:37 AM, Daniel Svensson wrote:
> On Tue, Jan 3, 2012 at 11:03 PM, Debian Bug Tracking System
> wrote:
>> Bug #654512 [xmms2] postler: doesn't contain source for waf binary code
>> Changed Bug title to 'Doesn't contain source for waf binary code' from
>> 'postler: doesn't
On Tue, Jan 3, 2012 at 11:03 PM, Debian Bug Tracking System
wrote:
> Bug #654512 [xmms2] postler: doesn't contain source for waf binary code
> Changed Bug title to 'Doesn't contain source for waf binary code' from
> 'postler: doesn't contain source for waf binary code'
This is just a compressed
Processing commands for cont...@bugs.debian.org:
> retitle 654462 Doesn't contain source for waf binary code
Bug #654462 [a2jmidid] postler: doesn't contain source for waf binary code
Changed Bug title to 'Doesn't contain source for waf binary code' from
'postler: doesn't contain source for waf b
11 matches
Mail list logo
