"Bernhard R. Link" writes:
> * Goswin von Brederlow [120311 19:51]:
>> git-dpm?
> http://git-dpm.alioth.debian.org/
> http://wiki.debian.org/PackagingWithGit/GitDpm
>
>> > That would still make git think that your upstream branch is based on
>> > your master branch and thus has the modification
* Goswin von Brederlow [120311 19:51]:
> git-dpm?
http://git-dpm.alioth.debian.org/
http://wiki.debian.org/PackagingWithGit/GitDpm
> > That would still make git think that your upstream branch is based on
> > your master branch and thus has the modification "remove debian/" in it
> > which git wi
Russ Allbery writes:
> Goswin von Brederlow writes:
>
>> But then you have to split your workflow again. You have to edit
>> upstream files in the master branch and debian files in the debian
>> branch. Switching between the branches becomes a pain and working in 2
>> workdirs is also a pain. To
Goswin von Brederlow writes:
> But then you have to split your workflow again. You have to edit
> upstream files in the master branch and debian files in the debian
> branch. Switching between the branches becomes a pain and working in 2
> workdirs is also a pain. To testbuild you then need to me
"Bernhard R. Link" writes:
> * Goswin von Brederlow [120311 08:10]:
>> I tried creating the upstream branch from the master branch and then
>> removing the debian dir. But then on the next merge git complains about a
>> merge conflict (modify/delete) when any file in debian/ was changed.
>
> git
Russ Allbery writes:
> Goswin von Brederlow writes:
>
>> I tried creating the upstream branch from the master branch and then
>> removing the debian dir. But then on the next merge git complains about a
>> merge conflict (modify/delete) when any file in debian/ was changed. I
>> googled a bit bu
* Goswin von Brederlow [120311 08:10]:
> I tried creating the upstream branch from the master branch and then
> removing the debian dir. But then on the next merge git complains about a
> merge conflict (modify/delete) when any file in debian/ was changed.
git is directed in that regard, if a chi
Goswin von Brederlow writes:
> I tried creating the upstream branch from the master branch and then
> removing the debian dir. But then on the next merge git complains about a
> merge conflict (modify/delete) when any file in debian/ was changed. I
> googled a bit but couldn't find any hint on ho
Russ Allbery writes:
> Goswin von Brederlow writes:
>> Russ Allbery writes:
>
>>> http://www.eyrie.org/~eagle/notes/debian/git.html
>
>> Where were you 2 years ago when I first asked about how to use git when
>> being both upstream and debian maintainer? :)
>
> Posting that site to Planet Debia
Goswin von Brederlow writes:
> Russ Allbery writes:
>> http://www.eyrie.org/~eagle/notes/debian/git.html
> Where were you 2 years ago when I first asked about how to use git when
> being both upstream and debian maintainer? :)
Posting that site to Planet Debian. :) In August of 2008 and then
Russ Allbery writes:
> Goswin von Brederlow writes:
>
>> Given the above idea how would you lay out the git then?
>
>> With a moments thought I would have 3 branches:
>> - master
>> - upstream
>> - pristine-tar
>
>> All developement would happen in the master branch. Then before the
>> Debian up
Goswin von Brederlow writes:
> Given the above idea how would you lay out the git then?
> With a moments thought I would have 3 branches:
> - master
> - upstream
> - pristine-tar
> All developement would happen in the master branch. Then before the
> Debian upload I would merge master -> upstre
Stéphane Glondu writes:
> Le 07/03/2012 09:14, Goswin von Brederlow a écrit :
>> With a moments thought I would have 3 branches:
>> - master
>> - upstream
>> - pristine-tar
>>
>> All developement would happen in the master branch. Then before the
>> Debian upload I would merge master -> upstream
Stéphane Glondu writes:
> Le 07/03/2012 09:52, Goswin von Brederlow a écrit :
>> That is what major, minor and subversions (x.y.z) are for. If I change
>> only something in Debian I would not increment x or y and I would not
>> create a new tarball for release on e.g. ocamlforge.
>
> I find this
Le 07/03/2012 09:52, Goswin von Brederlow a écrit :
> That is what major, minor and subversions (x.y.z) are for. If I change
> only something in Debian I would not increment x or y and I would not
> create a new tarball for release on e.g. ocamlforge.
I find this confusing. Debian has standardized
Le 07/03/2012 09:14, Goswin von Brederlow a écrit :
> I really don't get that argument. Nothing in having a debian directory
> in the source hinders any other distribution. And plenty of sources
> contain spec files for building rpms to no detriment to Debian. If any
> non rpm based distribution pi
Benoît Knecht writes:
> Goswin von Brederlow wrote:
>> Benoît Knecht writes:
>> > Goswin von Brederlow wrote:
>> >> [...]
>> >>
>> >> The package is native because I am both maintainer and upstream
>> >> author. Does a watch file make sense for a native package?
>> >
>> > That's not what nati
Stéphane Glondu writes:
> Le 06/03/2012 15:22, Benoît Knecht a écrit :
>> I think it important for any maintainer to clearly differentiate in
>> their mind upstream from Debian, even if they happen to be the same
>> person. Otherwise, you're artificially limiting your software to Debian,
>> wh
Le 06/03/2012 15:22, Benoît Knecht a écrit :
> I think it important for any maintainer to clearly differentiate in
> their mind upstream from Debian, even if they happen to be the same
> person. Otherwise, you're artificially limiting your software to Debian,
> which is at the opposite side of what
Goswin von Brederlow wrote:
> Benoît Knecht writes:
> > Goswin von Brederlow wrote:
> >> [...]
> >>
> >> The package is native because I am both maintainer and upstream
> >> author. Does a watch file make sense for a native package?
> >
> > That's not what native means. See the third point of [3]
Benoit Knecht writes:
> Hi Goswin,
>
> Goswin von Brederlow wrote:
>> Benoît Knecht writes:
>> > Goswin von Brederlow wrote:
>> >> I am looking for a sponsor for my package "libaio-ocaml"
>> >>
>> >> * Package name: libaio-ocaml
>> >>Version : 1.0~rc1
>> >>Upstream Author
tags 662632 - moreinfo
thanks
Stéphane Glondu writes:
> Le 05/03/2012 12:33, Goswin von Brederlow a écrit :
>> I am looking for a sponsor for my package "libaio-ocaml"
>
> I've looked at the git repository (037a448). It is written explicitly in
> [1]:
>
> "Do not close RFS bugs in debian/c
Hi Goswin,
Goswin von Brederlow wrote:
> Benoît Knecht writes:
> > Goswin von Brederlow wrote:
> >> I am looking for a sponsor for my package "libaio-ocaml"
> >>
> >> * Package name: libaio-ocaml
> >>Version : 1.0~rc1
> >>Upstream Author : Goswin von Brederlow
> >> * URL
Le 05/03/2012 12:33, Goswin von Brederlow a écrit :
> I am looking for a sponsor for my package "libaio-ocaml"
I've looked at the git repository (037a448). It is written explicitly in
[1]:
"Do not close RFS bugs in debian/changelog."
but the bug you refer to in debian/changelog is a RFS bug
Benoît Knecht writes:
> retitle 662632 RFS: libaio-ocaml/1.0~rc1 [ITP] -- OCaml bindings for libaio
> tags 662632 moreinfo
> thanks
>
> Hi Goswin,
>
> Goswin von Brederlow wrote:
>> I am looking for a sponsor for my package "libaio-ocaml"
>>
>> * Package name: libaio-ocaml
>>Version
Processing commands for cont...@bugs.debian.org:
> retitle 662632 RFS: libaio-ocaml/1.0~rc1 [ITP] -- OCaml bindings for libaio
Bug #662632 [sponsorship-requests] RFS: libaio-ocaml/1.0~rc1
Changed Bug title to 'RFS: libaio-ocaml/1.0~rc1 [ITP] -- OCaml bindings for
libaio' from 'RFS: libaio-ocaml/1
retitle 662632 RFS: libaio-ocaml/1.0~rc1 [ITP] -- OCaml bindings for libaio
tags 662632 moreinfo
thanks
Hi Goswin,
Goswin von Brederlow wrote:
> I am looking for a sponsor for my package "libaio-ocaml"
>
> * Package name: libaio-ocaml
>Version : 1.0~rc1
>Upstream Author : Go
Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]
Dear mentors,
I am looking for a sponsor for my package "libaio-ocaml"
* Package name: libaio-ocaml
Version : 1.0~rc1
Upstream Author : Goswin von Brederlow
* URL :
28 matches
Mail list logo
