On 11/11/19 6:30 PM, Theodore Y. Ts'o wrote:
> Yes, and that's why I use debian/master instead of debian/buster or
> debian/bullseye. :-)
>
> When I do create debian/buster (once it became the stable branch), the
> first thing I did after I branched off debian/buster from
> debian/master was t
On 11/14/19 1:59 AM, Jeremy Bicha wrote:
> Let me try to be more specific. Many packages are maintained by people
> who use gbp. Many packages have pristine-tar branches but do not have
> "pristine-tar = True" set. When I work on one of these packages (and I
> work on many packages with many mainta
On Wed, 13 Nov 2019 at 19:59:07 -0500, Jeremy Bicha wrote:
> Let me try to be more specific. Many packages are maintained by people
> who use gbp. Many packages have pristine-tar branches but do not have
> "pristine-tar = True" set. When I work on one of these packages (and I
> work on many package
On Tue, Nov 12, 2019 at 5:23 AM Thomas Goirand wrote:
> On 11/11/19 12:50 PM, Jeremy Bicha wrote:
> > It is absolutely not possible to set the correct
> > pristine-tar=True/False in ~/.gbp.conf to work with your packages
> > (which avoid pristine-tar) and the vast majority of gbp packages in
> > D
On 11/13/19 1:53 PM, Andreas Tille wrote:
> Except for not agreeing with your opinion about pristine-tar I agree that
> debian/gbp.conf is frequently not very helpful and flooded with unneeded
> options sometimes. It really makes sense to use ~/.gbp.conf instead.
This was the single and only poin
Andreas Tille writes:
> From time to time I hear this statement. I can confirm that in all
> teams I'm working on pristine-tar belongs to the team policy and I never
> experienced in those > 2000 packages I've touched any problem with this.
> For me this makes some statistically relevant set whi
On Mon, Nov 11, 2019 at 11:37:06AM -0800, Russ Allbery wrote:
> "Theodore Y. Ts'o" writes:
>
> > Yes, and that's why I use debian/master instead of debian/buster or
> > debian/bullseye. :-)
>
> > When I do create debian/buster (once it became the stable branch), the
> > first thing I did after
On Tue, Nov 12, 2019 at 11:23:08AM +0100, Thomas Goirand wrote:
>
> If you're rebuilding a package which is already in the archive, you're
> supposed to take the .orig.tar.xz from the archive, and if not, you're
> supposed to generate it with git archive (or with the shortcut for that
> command: .
On 11/11/19 12:50 PM, Jeremy Bicha wrote:
> On Mon, Nov 11, 2019 at 2:59 AM Thomas Goirand wrote:
>> On 11/11/19 1:02 AM, Theodore Y. Ts'o wrote:
>>> On Sun, Nov 10, 2019 at 11:20:45PM +0100, Thomas Goirand wrote:
Please, *never* do that. It's generally a very bad idea to write
anyt
"Theodore Y. Ts'o" writes:
> Yes, and that's why I use debian/master instead of debian/buster or
> debian/bullseye. :-)
> When I do create debian/buster (once it became the stable branch), the
> first thing I did after I branched off debian/buster from debian/master
> was to edit debian/gbp.con
On Mon, Nov 11, 2019 at 08:58:42AM +0100, Thomas Goirand wrote:
> >> Please, *never* do that. It's generally a very bad idea to write
> >> anything to debian/gbp.conf. It's as if you were adding your text editor
> >> preferences in the package. Instead, please prefer writing in ~/.gbp.conf.
> >
>
On Mon, Nov 11, 2019 at 2:59 AM Thomas Goirand wrote:
> On 11/11/19 1:02 AM, Theodore Y. Ts'o wrote:
> > On Sun, Nov 10, 2019 at 11:20:45PM +0100, Thomas Goirand wrote:
> >>
> >> Please, *never* do that. It's generally a very bad idea to write
> >> anything to debian/gbp.conf. It's as if you were
On 11/11/19 1:02 AM, Theodore Y. Ts'o wrote:
> On Sun, Nov 10, 2019 at 11:20:45PM +0100, Thomas Goirand wrote:
>>
>> Please, *never* do that. It's generally a very bad idea to write
>> anything to debian/gbp.conf. It's as if you were adding your text editor
>> preferences in the package. Instead, p
On Sun, Nov 10, 2019 at 11:20:45PM +0100, Thomas Goirand wrote:
>
> Please, *never* do that. It's generally a very bad idea to write
> anything to debian/gbp.conf. It's as if you were adding your text editor
> preferences in the package. Instead, please prefer writing in ~/.gbp.conf.
I keep most
On 10/5/19 7:48 PM, Attila Szalay wrote:
> I added the "pbuilder-options = --source-only-changes" option to the
> [buildpackage] part of the debian/gbp.conf
Please, *never* do that. It's generally a very bad idea to write
anything to debian/gbp.conf. It's as if you were adding your text editor
pre
15 matches
Mail list logo
