Goswin von Brederlow writes:
> Russ Allbery writes:
>> So, y'all realize that pdebuild --buildresult .. by default breaks
>> the *_source.changes file that it generates because it regenerates a
>> source package as part of the regular build, right? How are you
>> actually using that *_source.ch
Russ Allbery writes:
> Ben Finney writes:
>> Russ Allbery writes:
>>> Cyril Brulebois writes:
>
You call it superfluous. It's particularly helpful for source-only
uploads.
>
>>> Well, yes, it's superfluous for Debian, which doesn't support
>>> source-only uploads.
>
>> But not for ha
On Fri, May 15, 2009 at 11:26:28AM -0700, Russ Allbery wrote:
> pdebuild uses dpkg-buildpackage -S to generate a source package
> which it then copies into the chroot to do the full build.
FWIW, via cowbuilder you get _source.changes by default. So, for
instance, I started seeing those files when
Russ Allbery writes:
> So, y'all realize that pdebuild --buildresult .. by default breaks the
> *_source.changes file that it generates because it regenerates a
> source package as part of the regular build, right?
I've no idea about what pdebuild does, I don't use it. I was addressing
only the
Russ Allbery (15/05/2009):
> So, y'all realize that pdebuild --buildresult .. by default breaks the
> *_source.changes file that it generates because it regenerates a
> source package as part of the regular build, right? How are you
> actually using that *_source.changes file? Always having pdeb
Ben Finney writes:
> Russ Allbery writes:
>> Cyril Brulebois writes:
>>> You call it superfluous. It's particularly helpful for source-only
>>> uploads.
>> Well, yes, it's superfluous for Debian, which doesn't support
>> source-only uploads.
> But not for hackers preparing packages for Debian
Russ Allbery writes:
> Cyril Brulebois writes:
> > You call it superfluous. It's particularly helpful for source-only
> > uploads.
>
> Well, yes, it's superfluous for Debian, which doesn't support
> source-only uploads.
But not for hackers preparing packages for Debian, who want to present
tho
On 2009-05-15, Russ Allbery wrote:
> Cyril Brulebois writes:
>> Russ Allbery (15/05/2009):
>>> Calling dpkg-buildpackage -S produces a superfluous _sources.changes
>>> file, so anything that uses that method to produce a source package
>>> for build would either need to remove it or would leave
Cyril Brulebois writes:
> Russ Allbery (15/05/2009):
>> Calling dpkg-buildpackage -S produces a superfluous _sources.changes
>> file, so anything that uses that method to produce a source package
>> for build would either need to remove it or would leave it lying
>> around. pdebuild uses dpkg-b
Russ Allbery (15/05/2009):
> Calling dpkg-buildpackage -S produces a superfluous _sources.changes
> file, so anything that uses that method to produce a source package
> for build would either need to remove it or would leave it lying
> around. pdebuild uses dpkg-buildpackage -S to generate a sou
Malte Forkel writes:
> Russ Allbery schrieb:
>> Malte Forkel writes:
>>> After some more checking and thinking, I guess I know what's causing
>>> my problems: Its me, probably! I assume the source.changes files are
>>> created while I setup everything for building a package, e.g. by
>>> dh_make
Russ Allbery schrieb:
> Malte Forkel writes:
>
>> After some more checking and thinking, I guess I know what's causing
>> my problems: Its me, probably! I assume the source.changes files are
>> created while I setup everything for building a package, e.g. by
>> dh_make calling dpkg-buildpackage -
On 2009-05-14, Russ Allbery wrote:
> Malte Forkel writes:
>> After some more checking and thinking, I guess I know what's causing
>> my problems: Its me, probably! I assume the source.changes files are
>> created while I setup everything for building a package, e.g. by
>> dh_make calling dpkg-bui
Malte Forkel writes:
> After some more checking and thinking, I guess I know what's causing
> my problems: Its me, probably! I assume the source.changes files are
> created while I setup everything for building a package, e.g. by
> dh_make calling dpkg-buildpackage -S or whatever. I then use eith
Philipp Kern schrieb:
> [Sorry about the terse reply.]
>
Not at all. Thanks for responding!
> On 2009-05-14, Malte Forkel wrote:
>> Well, just judging from a limited sample, all source.changes and
>> i386.changes files I checked contain both Source and Binary fields.
>
> He spoke about the File
[Sorry about the terse reply.]
On 2009-05-14, Malte Forkel wrote:
> Well, just judging from a limited sample, all source.changes and
> i386.changes files I checked contain both Source and Binary fields.
He spoke about the Files part.
> There is some correlation to the Architecture field, though
Luk Claes schrieb:
> Malte Forkel wrote:
>> Hi,
>>
>> I recently noticed that when I'm packaging software sometimes a
>> i386.changes file gets created, and sometimes a source.changes file gets
>> created.
>>
>> I couldn't find an explanation in the New Maintainer's Guide or in the
>> Policy Manual
Malte Forkel wrote:
> Hi,
>
> I recently noticed that when I'm packaging software sometimes a
> i386.changes file gets created, and sometimes a source.changes file gets
> created.
>
> I couldn't find an explanation in the New Maintainer's Guide or in the
> Policy Manual. I guess its something to
Hi,
I recently noticed that when I'm packaging software sometimes a
i386.changes file gets created, and sometimes a source.changes file gets
created.
I couldn't find an explanation in the New Maintainer's Guide or in the
Policy Manual. I guess its something to do with the setup or type of the
pac
19 matches
Mail list logo
