Re: Renaming net/ceph to net/ceph12
On Tue, Jan 22, 2019 at 07:13:54PM +0100, Willem Jan Withagen wrote: > On 22-1-2019 16:45, Mathieu Arnold wrote: > > On Tue, Jan 22, 2019 at 03:35:51PM +0100, Willem Jan Withagen wrote: > > > On 22/01/2019 15:29, Mathieu Arnold wrote: > > > > On Tue, Jan 22, 2019 at 10:42:16AM +0100, Willem Jan Withagen wrote: > > > > > Hi, > > > > > > > > > > I there a ports committer that can do that for me if it is just a > > > > > mater of > > > > > `fix Makefile && svn rename` greatly appreciated. > > > > > > > > > > If it needs more work, can somebody explain to me what more is needed? > > > > > > > > > > After this is done, I'll submit a new ceph 12.2.11 version once it is > > > > > out. > > > > > And I'll upload the first version of ceph 13.2.x > > > > > > > > Well, there is nothing more needed, but, it would mean that until you > > > > submit tne 13.2.x update, there would be two identical versions of ceph. > > > > > > I would submit both under their own names: ceph12 or ceph13. > > > > Well, how they end up being named does not really matter. What matters > > is history. When ceph13 ends up being created, it will be by taking the > > ceph, or ceph12 directory, running svn copy so that subversion registers > > the ancestry, and by then updating that. > > Sorry for all the questions, but I do not often submit to FreeBSD. > And mostly upgrades go thru a shar in bugzilla. > > So I'd run > svn copy ceph ceph12 > svn copy ceph ceph13 > svn del ceph > > And fix both to the new versions... > Then submit the `svn diff net/ceph12` > > But then does that diff carry the ancestry? > Or need I submit thru arc? https://www.freebsd.org/doc/en/books/porters-handbook/port-upgrading.html Note: If some files have been added, copied, moved, or removed, add this information to the problem report so that the committer picking up the patch will know what svn(1) commands to run. -- Mathieu Arnold signature.asc Description: PGP signature
Re: Renaming net/ceph to net/ceph12
On 22-1-2019 16:45, Mathieu Arnold wrote: On Tue, Jan 22, 2019 at 03:35:51PM +0100, Willem Jan Withagen wrote: On 22/01/2019 15:29, Mathieu Arnold wrote: On Tue, Jan 22, 2019 at 10:42:16AM +0100, Willem Jan Withagen wrote: Hi, I there a ports committer that can do that for me if it is just a mater of `fix Makefile && svn rename` greatly appreciated. If it needs more work, can somebody explain to me what more is needed? After this is done, I'll submit a new ceph 12.2.11 version once it is out. And I'll upload the first version of ceph 13.2.x Well, there is nothing more needed, but, it would mean that until you submit tne 13.2.x update, there would be two identical versions of ceph. I would submit both under their own names: ceph12 or ceph13. Well, how they end up being named does not really matter. What matters is history. When ceph13 ends up being created, it will be by taking the ceph, or ceph12 directory, running svn copy so that subversion registers the ancestry, and by then updating that. Sorry for all the questions, but I do not often submit to FreeBSD. And mostly upgrades go thru a shar in bugzilla. So I'd run svn copy ceph ceph12 svn copy ceph ceph13 svn del ceph And fix both to the new versions... Then submit the `svn diff net/ceph12` But then does that diff carry the ancestry? Or need I submit thru arc? --WjW It would be preferrable to submit the 13.2.x update, asking the committer in the PR to also copy the current version to net/ceph12. Oke, So I'll first get ceph13 ready, submit and ask to move net/ceph to net/ceph12 Sort of like I did in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230432 ?? I'll be more persistent this time. --WjW ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Renaming net/ceph to net/ceph12
On Tue, Jan 22, 2019 at 03:35:51PM +0100, Willem Jan Withagen wrote: > On 22/01/2019 15:29, Mathieu Arnold wrote: > > On Tue, Jan 22, 2019 at 10:42:16AM +0100, Willem Jan Withagen wrote: > > > Hi, > > > > > > I there a ports committer that can do that for me if it is just a mater of > > > `fix Makefile && svn rename` greatly appreciated. > > > > > > If it needs more work, can somebody explain to me what more is needed? > > > > > > After this is done, I'll submit a new ceph 12.2.11 version once it is out. > > > And I'll upload the first version of ceph 13.2.x > > > > Well, there is nothing more needed, but, it would mean that until you > > submit tne 13.2.x update, there would be two identical versions of ceph. > > I would submit both under their own names: ceph12 or ceph13. Well, how they end up being named does not really matter. What matters is history. When ceph13 ends up being created, it will be by taking the ceph, or ceph12 directory, running svn copy so that subversion registers the ancestry, and by then updating that. > > It would be preferrable to submit the 13.2.x update, asking the > > committer in the PR to also copy the current version to net/ceph12. > > Oke, > > So I'll first get ceph13 ready, submit and ask to move net/ceph to > net/ceph12 > > Sort of like I did in > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230432 > ?? > I'll be more persistent this time. > > --WjW > > > > > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > -- Mathieu Arnold signature.asc Description: PGP signature
Re: Renaming net/ceph to net/ceph12
On 22/01/2019 15:29, Mathieu Arnold wrote: On Tue, Jan 22, 2019 at 10:42:16AM +0100, Willem Jan Withagen wrote: Hi, I there a ports committer that can do that for me if it is just a mater of `fix Makefile && svn rename` greatly appreciated. If it needs more work, can somebody explain to me what more is needed? After this is done, I'll submit a new ceph 12.2.11 version once it is out. And I'll upload the first version of ceph 13.2.x Well, there is nothing more needed, but, it would mean that until you submit tne 13.2.x update, there would be two identical versions of ceph. I would submit both under their own names: ceph12 or ceph13. It would be preferrable to submit the 13.2.x update, asking the committer in the PR to also copy the current version to net/ceph12. Oke, So I'll first get ceph13 ready, submit and ask to move net/ceph to net/ceph12 Sort of like I did in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230432 ?? I'll be more persistent this time. --WjW ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Renaming net/ceph to net/ceph12
On Tue, Jan 22, 2019 at 10:42:16AM +0100, Willem Jan Withagen wrote: > Hi, > > I there a ports committer that can do that for me if it is just a mater of > `fix Makefile && svn rename` greatly appreciated. > > If it needs more work, can somebody explain to me what more is needed? > > After this is done, I'll submit a new ceph 12.2.11 version once it is out. > And I'll upload the first version of ceph 13.2.x Well, there is nothing more needed, but, it would mean that until you submit tne 13.2.x update, there would be two identical versions of ceph. It would be preferrable to submit the 13.2.x update, asking the committer in the PR to also copy the current version to net/ceph12. -- Mathieu Arnold signature.asc Description: PGP signature
