Your message dated Thu, 30 Aug 2018 15:28:25 -1000 with message-id <20180831012825.GA7410@persil.tilapin.org> and subject line Re: Bug#172892: best practices for CVS package handling has caused the Debian Bug report #172892, regarding maint-guide: best practices for CVS package handling to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 172892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=172892 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: maint-guide: best practices for CVS package handling
- From: era eriksson <era@iki.fi>
- Date: Fri, 13 Dec 2002 11:21:00 +0200
- Message-id: <E18Mm0C-000599-00@there.afraid.org>
Package: maint-guide Version: 1.0.2 Severity: wishlist As a lot of upstreams make their sources available over anon CVS, and a lot of Debian package maintainers seem to be using CVS to manage their packages, it would be useful to have a section or two about how to best combine CVS with the package management tool, perhaps also with some pointers to specialized packages for making this easy. There are some philosophical setup problems: - Should you set up your own "slave" CVS server which periodically downloads from the upstream repository, while keeping the integrity of your own local / packaging changes? How? - If not, should your local repository contain a copy of the upstream source, or just your own changes? How would you manage this? There are some simple day-to-day problems: - Surely there must already be many package maintainers who have set up cron jobs for monitoring upstream sources etc. Getting examples or even (gasp) pointers to polished packages which provide these sorts of facilities would be very useful. - How to keep version numbers and tag labels safe and consistent, in the case when you are using a slave CVS repository - Somebody posted about how CVS makes it simple to keep three versions of the sources on your computer, each corresponding respectively to stable, testing, and unstable. I don't think this sounds hard to do, but having a working example would be nice. These are things I've been wondering about myself, it's not like I am able to write up good answers on my own. Perhaps this should actually be the topic of a separate HOWTO or something. /* era */ -- Join the civilized world -- ban spam like we did! <http://www.euro.cauce.org/> tee -a $HOME/.signature <$HOME/.plan >http://www.iki.fi/era/index.html
--- End Message ---
--- Begin Message ---
- To: Tobias Frost <tobi@debian.org>, 172892-done@bugs.debian.org
- Subject: Re: Bug#172892: best practices for CVS package handling
- From: David Prévot <taffit@debian.org>
- Date: Thu, 30 Aug 2018 15:28:25 -1000
- Message-id: <20180831012825.GA7410@persil.tilapin.org>
- In-reply-to: <[🔎] 12ed89a96a54bc44144f6d1734f1189cc8c0d2b2.camel@debian.org>
- References: <CAPpVEmWmpc=NRK=tNzpVAKxrCLyvEVN9SWsex0nn9JOYT8MyzQ@mail.gmail.com> <E18Mm0C-000599-00@there.afraid.org> <[🔎] 12ed89a96a54bc44144f6d1734f1189cc8c0d2b2.camel@debian.org>
On Thu, Aug 30, 2018 at 11:58:08PM +0200, Tobias Frost wrote: > On Mon, 1 Jun 2015 15:59:30 +0900 Hideki Yamane <henrich@debian.or.jp> > > Probably it was useful when reported in 2002, but we're in 2015 and > > CVS was gone. so I'll tag wontfix for it. > > Should we just close the bug? Sure, done! I even heard rumors about www.d.o moving away from CVS ;). (kudos to everyone involve in that move!) Regards DavidAttachment: signature.asc
Description: PGP signature
--- End Message ---