Re: upstream new version
Am 30.03.01 um 02:08:47 schrieb Timshel Knoll: On Thu, Mar 29, 2001 at 11:18:26AM +0100, Colin Watson wrote: - copy the debian/changelog file and add a new entry there. (is there a tool for doing this, or do i need to do it by hand like i currently do ?) debchange (in the devscripts package). Or debian-changelog-mode in emacs (from the dpkg-dev-el package) Or, of course, the debian-changelog mode for vim, which will be part of Vim 6.0 (it's already in the beta versions). Bye, Mike -- |=| Michael Piefel[EMAIL PROTECTED] |=| Humboldt-Universitt zu Berlin http://www.piefel.de |=| Tel. (+49 30) 2093 3831 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: upstream new version
Michael Piefel wrote: Or debian-changelog-mode in emacs (from the dpkg-dev-el package) Or, of course, the debian-changelog mode for vim, which will be part of Vim 6.0 (it's already in the beta versions). I smell a feature competition coming on... (just joking :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: upstream new version
Am 30.03.01 um 02:08:47 schrieb Timshel Knoll: On Thu, Mar 29, 2001 at 11:18:26AM +0100, Colin Watson wrote: - copy the debian/changelog file and add a new entry there. (is there a tool for doing this, or do i need to do it by hand like i currently do ?) debchange (in the devscripts package). Or debian-changelog-mode in emacs (from the dpkg-dev-el package) Or, of course, the debian-changelog mode for vim, which will be part of Vim 6.0 (it's already in the beta versions). Bye, Mike -- |=| Michael Piefel[EMAIL PROTECTED] |=| Humboldt-Universität zu Berlin http://www.piefel.de |=| Tel. (+49 30) 2093 3831
Re: upstream new version
Michael Piefel wrote: Or debian-changelog-mode in emacs (from the dpkg-dev-el package) Or, of course, the debian-changelog mode for vim, which will be part of Vim 6.0 (it's already in the beta versions). I smell a feature competition coming on... (just joking :-)
Re: upstream new version
On Thu, Mar 29, 2001 at 10:48:49AM +0200, Stefano Zacchiroli wrote: I've to build a new package against a new upstream version released by the upstream author of one of my packages. What I have to do to merge the new upstream version in the old one debianized source tree ? Have I to unpack the new orig file and copy in it the old debian/ dir ? What i use to do is either : 1) just apply the diff file to the new package, chmod +x debian/rules, and check that nothing broke. and once in a while i also do : 2) do a dh_make on the new upstream source, and one by one migrate the stuff done for the previous version to the new version. this needs : - applying all patches to the upstream source that are still needed. - modifying debian/rules os that it does the same things as the previous version - copy the debian/changelog file and add a new entry there. (is there a tool for doing this, or do i need to do it by hand like i currently do ?) - copy the rest of the stuff, checking it is still needed/don't need to be modified. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: upstream new version
Sven LUTHER [EMAIL PROTECTED] wrote: What i use to do is either : 1) just apply the diff file to the new package, chmod +x debian/rules, and check that nothing broke. and once in a while i also do : 2) do a dh_make on the new upstream source, and one by one migrate the stuff done for the previous version to the new version. this needs : - applying all patches to the upstream source that are still needed. - modifying debian/rules os that it does the same things as the previous version - copy the debian/changelog file and add a new entry there. (is there a tool for doing this, or do i need to do it by hand like i currently do ?) debchange (in the devscripts package). - copy the rest of the stuff, checking it is still needed/don't need to be modified. Sounds like a large amount of extra error-prone work to me, although I suppose running dh_make every so often is one way of keeping some bits of policy vaguely up to date. I just use uscan/uupdate to unpack the new source and try to apply the old diffs for me. -- Colin Watson [[EMAIL PROTECTED]] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: upstream new version
On Thu, Mar 29, 2001 at 11:18:26AM +0100, Colin Watson wrote: Sven LUTHER [EMAIL PROTECTED] wrote: - copy the debian/changelog file and add a new entry there. (is there a tool for doing this, or do i need to do it by hand like i currently do ?) debchange (in the devscripts package). Or debian-changelog-mode in emacs (from the dpkg-dev-el package) -- Timshel Knoll [EMAIL PROTECTED] for Debian email: [EMAIL PROTECTED] Geomatics/Computer Science double degree, RMIT Debian GNU/Linux developer, see http://people.debian.org/~timshel/ For GnuPG public key: finger [EMAIL PROTECTED] PGP signature
upstream new version
I've to build a new package against a new upstream version released by the upstream author of one of my packages. What I have to do to merge the new upstream version in the old one debianized source tree ? Have I to unpack the new orig file and copy in it the old debian/ dir ? TIA Bye -- - Zack - Stefano Zacchiroli [EMAIL PROTECTED] ICQ# 33538863 Home Page: http://www.students.cs.unibo.it/~zacchiro Undergraduate Student of Computer Science at University of Bologna, Italy SysAdm of verdicchio.students.cs.unibo.it (130.136.3.134) Information wants to be Open pgp4rn3hKbFA2.pgp Description: PGP signature
Re: upstream new version
Hi, On Thu, Mar 29, 2001 at 10:48:49AM +0200, Stefano Zacchiroli wrote: What I have to do to merge the new upstream version in the old one debianized source tree ? Have I to unpack the new orig file and copy in it the old debian/ dir ? No! See Debian New Maintainer's Guide chapter 6.4 Updating the package. Best wishes, Guenter -- Linux: Who needs GATES in a world without fences?
Re: upstream new version
On Thu, Mar 29, 2001 at 10:48:49AM +0200, Stefano Zacchiroli wrote: I've to build a new package against a new upstream version released by the upstream author of one of my packages. What I have to do to merge the new upstream version in the old one debianized source tree ? Have I to unpack the new orig file and copy in it the old debian/ dir ? What i use to do is either : 1) just apply the diff file to the new package, chmod +x debian/rules, and check that nothing broke. and once in a while i also do : 2) do a dh_make on the new upstream source, and one by one migrate the stuff done for the previous version to the new version. this needs : - applying all patches to the upstream source that are still needed. - modifying debian/rules os that it does the same things as the previous version - copy the debian/changelog file and add a new entry there. (is there a tool for doing this, or do i need to do it by hand like i currently do ?) - copy the rest of the stuff, checking it is still needed/don't need to be modified. Friendly, Sven Luther
Re: upstream new version
Sven LUTHER [EMAIL PROTECTED] wrote: What i use to do is either : 1) just apply the diff file to the new package, chmod +x debian/rules, and check that nothing broke. and once in a while i also do : 2) do a dh_make on the new upstream source, and one by one migrate the stuff done for the previous version to the new version. this needs : - applying all patches to the upstream source that are still needed. - modifying debian/rules os that it does the same things as the previous version - copy the debian/changelog file and add a new entry there. (is there a tool for doing this, or do i need to do it by hand like i currently do ?) debchange (in the devscripts package). - copy the rest of the stuff, checking it is still needed/don't need to be modified. Sounds like a large amount of extra error-prone work to me, although I suppose running dh_make every so often is one way of keeping some bits of policy vaguely up to date. I just use uscan/uupdate to unpack the new source and try to apply the old diffs for me. -- Colin Watson [EMAIL PROTECTED]
Re: upstream new version
On Thu, Mar 29, 2001 at 11:18:26AM +0100, Colin Watson wrote: Sven LUTHER [EMAIL PROTECTED] wrote: What i use to do is either : 1) just apply the diff file to the new package, chmod +x debian/rules, and check that nothing broke. and once in a while i also do : 2) do a dh_make on the new upstream source, and one by one migrate the stuff done for the previous version to the new version. this needs : - applying all patches to the upstream source that are still needed. - modifying debian/rules os that it does the same things as the previous version - copy the debian/changelog file and add a new entry there. (is there a tool for doing this, or do i need to do it by hand like i currently do ?) debchange (in the devscripts package). Thanks, didn't know about this. - copy the rest of the stuff, checking it is still needed/don't need to be modified. Sounds like a large amount of extra error-prone work to me, although I suppose running dh_make every so often is one way of keeping some bits Thought so also :))) Also will look at what dh_make will propose to me about about multi-binaries. of policy vaguely up to date. I just use uscan/uupdate to unpack the new source and try to apply the old diffs for me. Yes, but, ... Often the diffs are no more valid, or may apply, but will not work as expected. Also, since i send my patches also upstream, often the patches i have need no more to be applied, but will also not be detected to be already applied, since upstream may have changed them a bit. But then i guess it depends on the package, and as for me upstream provides good quality releases, and also accepts my patches, this is the easiest way for me. Friendly, Sven Luther
Re: upstream new version
On Thu, Mar 29, 2001 at 11:18:26AM +0100, Colin Watson wrote: Sven LUTHER [EMAIL PROTECTED] wrote: - copy the debian/changelog file and add a new entry there. (is there a tool for doing this, or do i need to do it by hand like i currently do ?) debchange (in the devscripts package). Or debian-changelog-mode in emacs (from the dpkg-dev-el package) -- Timshel Knoll [EMAIL PROTECTED] for Debian email: [EMAIL PROTECTED] Geomatics/Computer Science double degree, RMIT Debian GNU/Linux developer, see http://people.debian.org/~timshel/ For GnuPG public key: finger [EMAIL PROTECTED] pgpFyxaHVhPZo.pgp Description: PGP signature
