Re: Preparing the way for emacs22 with many individual package updates
[EMAIL PROTECTED] (Eric S. Raymond) writes: > Toby Smithe <[EMAIL PROTECTED]>: >> They are usually placed into /etc/apt/sources.list, or a >> file in /etc/apt/sources.list.d. After updating this file, you will need >> to update the cache, by running "apt-get update". > > Done. Is the incantation to follow with "apt upgrade emacs22"? It follows with `apt-get install emacs22`. The packages are available now, I'm using them currently myself with Gnus/CVS :). Please note, the packages are built for the `gutsy` distribution, which will become ubuntu 7.10. It is corrently not recommended to use that version for production use. I will update the packages in my PPA until it gets accepted into gutsy properly. Sorry for not being more clear in the first place. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
Moins, Am Donnerstag, den 05.07.2007, 17:10 -0400 schrieb Eric S. Raymond: > Reinhard Tartler <[EMAIL PROTECTED]>: > > If you have suggestion how to improve the documentation, let us > > know. Where would you have expected documentation about > > update-alternatives? > > This is not the kind of problem which can be solved with documentation. > Requiring users to RTFM in situations like this is a confession of UI > design failure. See my mini-rant in response to Michael Olson. > > Would a Mac user, for example, ever have to RTFM to install such an > update? When a MAC user is using the underlaying BSD system, and want to use the Ports system, he has to read the documentation. Just because you can use a mouse to do some all-day-long tasks is not a reason to not read a documentation. Reading documentation is a must, even for a coffee machine or a microwave. In this case, you should know about your tool of your choice. When you use Debian, you should know something about the debian way (ubuntu is debian based ;)). When you use SuSE, you should know something about yast, when you use RedHat, you should know about the RHAT config utilities. Learning by doing is a nice way to solve some problems, but it's timeconsuming. Knowing where to read about your problem before you start "doing and learn" is much better ;) > > > > More generally, I'm a fairly heavyweight Emacs expert (author of a > > > couple of the standard-library packages, among other things). > > > Please consider me available for package testing. > > > > Okay, I'm currently uploading Michaels emacs22 package to my personal > > package archive. They should appear soon there. You can use the > > following apt line for installing them (as soon as they get published > > and built on the build daemons): > > > > deb http://ppa.dogfood.launchpad.net/siretart/ubuntu/ gutsy main universe > > deb-src http://ppa.dogfood.launchpad.net/siretart/ubuntu/ gutsy main > > universe > > Um, this doesn't look like a command. Am I suppose to stuff it in a > config file somewhere? Sorry for my ignorance, I'm a recovering Fedora user. man apt-get sudo vi /etc/apt/sources.list add those lines, sudo apt-get update sudo apt-get install I wonder what fedora is using as a repository package manager (not rpm, this is equivalent to dpkg) but I thought they are using smart or yum as package manager, no? Regards, \sh -- Stephan Hermann eMail: [EMAIL PROTECTED] Blog: http://linux.blogweb.de/ JID: [EMAIL PROTECTED] OSS-Developer and Admin signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
Alexandre Vassalotti <[EMAIL PROTECTED]>: > However, please note this is a development mailing list and such > questions would better answered on the appropriate support mailing > list, Ubuntu-users, or in the #ubuntu IRC channel on FreeNode. I'll use the IRC channel in future. -- http://www.catb.org/~esr/";>Eric S. Raymond -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
Toby Smithe <[EMAIL PROTECTED]>: > They are usually placed into /etc/apt/sources.list, or a > file in /etc/apt/sources.list.d. After updating this file, you will need > to update the cache, by running "apt-get update". Done. Is the incantation to follow with "apt upgrade emacs22"? -- http://www.catb.org/~esr/";>Eric S. Raymond -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
On Thu, 2007-07-05 at 17:10 -0400, Eric S. Raymond wrote: > Reinhard Tartler <[EMAIL PROTECTED]>: > > deb http://ppa.dogfood.launchpad.net/siretart/ubuntu/ gutsy main universe > > deb-src http://ppa.dogfood.launchpad.net/siretart/ubuntu/ gutsy main > > universe > > Um, this doesn't look like a command. Am I suppose to stuff it in a > config file somewhere? Sorry for my ignorance, I'm a recovering Fedora user. They are "apt lines", which describe to apt where to download packages and the metadata from. The "deb" line describes the binary repository, whilst the "deb-src" line, as expected, describes the sources repository. They are usually placed into /etc/apt/sources.list, or a file in /etc/apt/sources.list.d. After updating this file, you will need to update the cache, by running "apt-get update". There is a GUI for this functionality at /usr/bin/software-properties-gtk, which can be found in the menus as System/Administration/'Software Sources'. Toby Smithe -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
Reinhard Tartler <[EMAIL PROTECTED]>: > If you have suggestion how to improve the documentation, let us > know. Where would you have expected documentation about > update-alternatives? This is not the kind of problem which can be solved with documentation. Requiring users to RTFM in situations like this is a confession of UI design failure. See my mini-rant in response to Michael Olson. Would a Mac user, for example, ever have to RTFM to install such an update? > > More generally, I'm a fairly heavyweight Emacs expert (author of a > > couple of the standard-library packages, among other things). > > Please consider me available for package testing. > > Okay, I'm currently uploading Michaels emacs22 package to my personal > package archive. They should appear soon there. You can use the > following apt line for installing them (as soon as they get published > and built on the build daemons): > > deb http://ppa.dogfood.launchpad.net/siretart/ubuntu/ gutsy main universe > deb-src http://ppa.dogfood.launchpad.net/siretart/ubuntu/ gutsy main universe Um, this doesn't look like a command. Am I suppose to stuff it in a config file somewhere? Sorry for my ignorance, I'm a recovering Fedora user. -- http://www.catb.org/~esr/";>Eric S. Raymond -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
On 7/4/07, Michael Olson <[EMAIL PROTECTED]> wrote: > I'm starting to go through each of the Emacs Lisp packages I use and > make certain that they would work with a theoretical emacs22 package. > I've also fixed lintian warnings and other errors along the way, and > submitted fixes back to the Debian package maintainers. I think currently the most annoying bug is the semantic-mode one: https://bugs.launchpad.net/ubuntu/+source/emacs-snapshot/+bug/93667 There is a fix described at: http://www.togaware.com/linux/survivor/Emacs_Using.html However, I think it would be better to just update the whole cadet package to the latest release (1.0pre4), which fixes this bug and a few others. I will try to contact the current maintainer of the debian package to see if he's working on it, otherwise I will package it myself. Keep the good work, -- Alexandre -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
Reinhard Tartler <[EMAIL PROTECTED]> writes: > Michael Olson <[EMAIL PROTECTED]> writes: >> And here are some packages of mine that have been updated recently in >> Debian unstable and need a sync to preserve the manual. >> >> - https://bugs.launchpad.net/ubuntu/+source/erc/+bug/123906 >> - https://bugs.launchpad.net/ubuntu/+source/muse-el/+bug/123907 > > If the manual has been stripped of in debian, we need another > orig.tar.gz. In that case we cannot sync from debian, since we are > using another source in fact. Do I miss something here? I haven't actually removed the manuals from the .orig.tar.gz in the Debian version -- I just did not install them into the package. So it should be safe to sync, since .orig.tar.gz is the same in Debian and Ubuntu. -- Michael Olson -- FSF Associate Member #652 | http://mwolson.org/ -- Jabber: mwolson_at_hcoop.net | /` |\ | | | Sysadmin -- Hobbies: Lisp, GP2X, HCoop| |_] | \| |_| Projects: Emacs, Muse, ERC, EMMS, ErBot, DVC, Planner | pgpn6kfiGmIoN.pgp Description: PGP signature -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
Michael Olson <[EMAIL PROTECTED]> writes: > And here are some packages of mine that have been updated recently in > Debian unstable and need a sync to preserve the manual. > > - https://bugs.launchpad.net/ubuntu/+source/erc/+bug/123906 > - https://bugs.launchpad.net/ubuntu/+source/muse-el/+bug/123907 If the manual has been stripped of in debian, we need another orig.tar.gz. In that case we cannot sync from debian, since we are using another source in fact. Do I miss something here? -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 pgp7ZQG8S2SXS.pgp Description: PGP signature -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
>> [EMAIL PROTECTED] (Eric S. Raymond) writes: >> > Note: I tried emacs-snapshot, and would be using it now except that >> > it doesn't seem to play nice with emacsclient. Consider this a >> > minor bug report. > Michael Olson <[EMAIL PROTECTED]>: >> Make sure that the /etc/alternatives/emacsclient points to >> /usr/bin/emacsclient.emacs-snapshot (and likewise for emacsclient.1.gz). >> This can also be achieved by running the following as root: >> >> update-alternatives --config emacsclient >> >> If it gives a message like "Nothing to configure" (which happens if you >> have only one variant of emacs on your system), then do the following >> to double-check the link: >> >> update-alternatives --auto emacsclient >> >> This updates both emacsclient and emacsclient.1.gz. [EMAIL PROTECTED] (Eric S. Raymond) writes: > Thanks for the tip; this may well resolve my problem. Is this procedure > documented anywhere? I'm still an Ubuntu- and Debian-world novice, where > would I learn when something like this is advisable? This is the debian alternatives system, which is a debian heritage. It is documented in the manpage update-alternatives(8). There was an article about it in 2005 at http://www.debian-administration.org/articles/91, which is perhaps a more lightweight lecture for this. > I'll file a bug report through the tracker previously suggested if > this doesn't work. If you have suggestion how to improve the documentation, let us know. Where would you have expected documentation about update-alternatives? > More generally, I'm a fairly heavyweight Emacs expert (author of a > couple of the standard-library packages, among other things). > Please consider me available for package testing. Okay, I'm currently uploading Michaels emacs22 package to my personal package archive. They should appear soon there. You can use the following apt line for installing them (as soon as they get published and built on the build daemons): deb http://ppa.dogfood.launchpad.net/siretart/ubuntu/ gutsy main universe deb-src http://ppa.dogfood.launchpad.net/siretart/ubuntu/ gutsy main universe -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 pgpdZM3AulGML.pgp Description: PGP signature -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
Michael Olson <[EMAIL PROTECTED]>: > [EMAIL PROTECTED] (Eric S. Raymond) writes: > > > Note: I tried emacs-snapshot, and would be using it now except that > > it doesn't seem to play nice with emacsclient. Consider this a > > minor bug report. > > Make sure that the /etc/alternatives/emacsclient points to > /usr/bin/emacsclient.emacs-snapshot (and likewise for emacsclient.1.gz). > This can also be achieved by running the following as root: > > update-alternatives --config emacsclient > > If it gives a message like "Nothing to configure" (which happens if you > have only one variant of emacs on your system), then do the following > to double-check the link: > > update-alternatives --auto emacsclient > > This updates both emacsclient and emacsclient.1.gz. Thanks for the tip; this may well resolve my problem. Is this procedure documented anywhere? I'm still an Ubuntu- and Debian-world novice, where would I learn when something like this is advisable? I'll file a bug report through the tracker previously suggested if this doesn't work. More generally, I'm a fairly heavyweight Emacs expert (author of a couple of the standard-library packages, among other things). Please consider me available for package testing. -- http://www.catb.org/~esr/";>Eric S. Raymond signature.asc Description: Digital signature -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
Toby Smithe <[EMAIL PROTECTED]>: > On Wed, 2007-07-04 at 17:08 -0400, Eric S. Raymond wrote: > > Note: I tried emacs-snapshot, and would be using it now except that > > it doesn't seem to play nice with emacsclient. Consider this a > > minor bug report. > > Well, I'm sure you know the rationale (mailing lists not good > bug-trackers, etc), so - if you haven't already - could you file a bug > report at https://launchpad.net/ubuntu/+source/emacs-snapshot/+filebug Thanks, that's the prompt I was looking for. Will do. -- http://www.catb.org/~esr/";>Eric S. Raymond -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
[EMAIL PROTECTED] (Eric S. Raymond) writes: > Note: I tried emacs-snapshot, and would be using it now except that > it doesn't seem to play nice with emacsclient. Consider this a > minor bug report. Make sure that the /etc/alternatives/emacsclient points to /usr/bin/emacsclient.emacs-snapshot (and likewise for emacsclient.1.gz). This can also be achieved by running the following as root: update-alternatives --config emacsclient If it gives a message like "Nothing to configure" (which happens if you have only one variant of emacs on your system), then do the following to double-check the link: update-alternatives --auto emacsclient This updates both emacsclient and emacsclient.1.gz. -- Michael Olson -- FSF Associate Member #652 | http://mwolson.org/ -- Jabber: mwolson_at_hcoop.net | /` |\ | | | Sysadmin -- Hobbies: Lisp, GP2X, HCoop| |_] | \| |_| Projects: Emacs, Muse, ERC, EMMS, ErBot, DVC, Planner | pgp3DdxCcHTHA.pgp Description: PGP signature -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
On Wed, 2007-07-04 at 17:08 -0400, Eric S. Raymond wrote: > Note: I tried emacs-snapshot, and would be using it now except that > it doesn't seem to play nice with emacsclient. Consider this a > minor bug report. Well, I'm sure you know the rationale (mailing lists not good bug-trackers, etc), so - if you haven't already - could you file a bug report at https://launchpad.net/ubuntu/+source/emacs-snapshot/+filebug Thanks, Toby Smithe -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
Romain Francoise <[EMAIL PROTECTED]>: > Thanks for including me in the discussion, I appreciate it. > > Reinhard Tartler <[EMAIL PROTECTED]> writes: > > > I'm not sure what Romain's plans are for emacs-snapshot, but this > > sounds reasonable. > > The plan for emacs-snapshot is to continue to follow the Emacs 22 > release branch until the 22.2 release, then switch back to the trunk > to benefit from the emacs-unicode and/or emacs-multi-tty merge(s). Note: I tried emacs-snapshot, and would be using it now except that it doesn't seem to play nice with emacsclient. Consider this a minor bug report. -- http://www.catb.org/~esr/";>Eric S. Raymond -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
Hey Reinhard, MOTUs, Thanks for including me in the discussion, I appreciate it. Reinhard Tartler <[EMAIL PROTECTED]> writes: > I'm not sure what Romain's plans are for emacs-snapshot, but this > sounds reasonable. The plan for emacs-snapshot is to continue to follow the Emacs 22 release branch until the 22.2 release, then switch back to the trunk to benefit from the emacs-unicode and/or emacs-multi-tty merge(s). The current version of emacs-snapshot (20070701) is much closer to Emacs 22.2 than 22.1 (the version Michael is working on) so if you sync it into Gutsy there will be little duplication, both packages will be useful. 22.2 includes the following new features: a CSS mode, a Vera mode, better horizontal and vertical scrolling of images, and new defaults for file and directory deletion in Dired. If it helps, I'll note that I reviewed Michael's emacs22 package and I think it's ready for inclusion (but I'm not familiar with Ubuntu's processes in this area). Cheers, -- ,''`. : :' :Romain Francoise <[EMAIL PROTECTED]> `. `' http://people.debian.org/~rfrancoise/ `- -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
[The previous message from me was put in moderation, so this might appear out of order on ubuntu-motu.] Reinhard Tartler <[EMAIL PROTECTED]> writes: > Michael Olson <[EMAIL PROTECTED]> writes: > >> >> I am working on my own emacs22 package, which is based heavily on >> Romain's emacs-snapshot package. >> > > Ah, cool! I noticed and already joined the lp group you created: > https://launchpad.net/~ubuntu-elisp > > Do you intend to host your packaging branch there? What is that group > for? I haven't decided what to do with that group yet. I wanted a point of presence for maintainers of Emacs Lisp packages, mainly. Suggestions for how to make good use of that group are welcome. :^) For now, I'm managing the emacs22 ./debian directory with git. If it would help group-maintenance efforts, I could create a bzr branch and host in on launchpad (I've never created a branch there before, so I'd have to look up how to do it). I have some bzr experience, so I could work with it. Current instructions for getting the ./debian directory are: git clone http://deleuze.hcoop.net/~mwolson/git/debian/emacs22.git > I've just had a very brief look at the source package, and tried to > compare it to Romains package. The differences seem to be considerable. Hmm. The changes were mostly s/emacs-snapshot/emacs22/ and s/Debian/Ubuntu/, with some snapshot-specific rules dropped or changed. If there are other changes that need to be made, let me know. > What is your plan about your emacs22 package? Do you intend to have it > in gutsy? With whom do you work together to bring that work in ubuntu? I want very much to get it into gutsy. I've emailed the last uploader of emacs21 about it on Monday, but haven't heard back yet. Any assistance on how to accomplish this would be welcome. >>> The problem I see with debian's package is that is strips of >>> documentation in another source package, something that we don't need >>> nor want in ubuntu (well, we could make our lives easy and just hard >>> depend on the documentation, but let's not go crazy here..) >> >> I completely agree. The very reason I am pushing for my emacs22 package >> (or, if some other Ubuntu core developer wants to maintain it instead, >> their package) rather than Debian's is because I do not want to see the >> documentation and GNU Manifesto stripped out into a separate "nondfsg" >> package. > > I'd be willing to help out with maintaining, however, my emacs-lisp > knowledge is very limited. I'm using emacs22 a lot, however. Excellent! I maintain several upstream emacs-lisp packages, so this might work out well. -- Michael Olson -- FSF Associate Member #652 | http://mwolson.org/ -- Jabber: mwolson_at_hcoop.net | /` |\ | | | Sysadmin -- Hobbies: Lisp, GP2X, HCoop| |_] | \| |_| Projects: Emacs, Muse, ERC, EMMS, ErBot, DVC, Planner | pgp81XDLGcXaA.pgp Description: PGP signature -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
Michael Olson <[EMAIL PROTECTED]> writes: > > I am working on my own emacs22 package, which is based heavily on > Romain's emacs-snapshot package. > Ah, cool! I noticed and already joined the lp group you created: https://launchpad.net/~ubuntu-elisp Do you intend to host your packaging branch there? What is that group for? I've just had a very brief look at the source package, and tried to compare it to Romains package. The differences seem to be considerable. What is your plan about your emacs22 package? Do you intend to have it in gutsy? With whom do you work together to bring that work in ubuntu? >> The problem I see with debian's package is that is strips of >> documentation in another source package, something that we don't need >> nor want in ubuntu (well, we could make our lives easy and just hard >> depend on the documentation, but let's not go crazy here..) > > I completely agree. The very reason I am pushing for my emacs22 package > (or, if some other Ubuntu core developer wants to maintain it instead, > their package) rather than Debian's is because I do not want to see the > documentation and GNU Manifesto stripped out into a separate "nondfsg" > package. I'd be willing to help out with maintaining, however, my emacs-lisp knowledge is very limited. I'm using emacs22 a lot, however. > >> For gutsy, I think we should decide if we want to ship with >> 'emacs-snapshot', go to experimental's emacs22 package, or work on a >> dedicated 'ubuntu emacs22' package. > > How about both my emacs22 package, and also an updated version of > Romain's emacs-snapshot (still packaged as emacs-snapshot)? I'm not sure what Romain's plans are for emacs-snapshot, but this sounds reasonable. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 pgptaDh9omVOq.pgp Description: PGP signature -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
Reinhard Tartler <[EMAIL PROTECTED]> writes: > CC'ing Romain, since I think this might be interesting for him. > > Michael Olson <[EMAIL PROTECTED]> writes: > >> I'm starting to go through each of the Emacs Lisp packages I use and >> make certain that they would work with a theoretical emacs22 package. >> I've also fixed lintian warnings and other errors along the way, and >> submitted fixes back to the Debian package maintainers. > > I'm currently using emacs22 from the emacs-snapshot package in > gutsy. In fact, it was me who requested the sync from Romain's private > archive. I'm not sure if you are aware of this fact. > > In fact, there is already an emacs22 package in debian/experimental. > What I wanted to ask you is: Are you working on that package, or on > Romain's emacs-snapshot package? Or are you working on your own > emacs22 package? In any case, why? I am working on my own emacs22 package, which is based heavily on Romain's emacs-snapshot package. My package may be retrieved by adding the following to your /etc/apt/sources.list. deb http://mwolson.org/ubuntu/emacs ./ deb-src http://mwolson.org/ubuntu/emacs ./ For now, I've modified those packages such that bug reports go to my own email address, since they aren't in gutsy yet. Upon making gutsy, this should be changed. My work on fixing packages to work with emacs22 is also there. > The problem I see with debian's package is that is strips of > documentation in another source package, something that we don't need > nor want in ubuntu (well, we could make our lives easy and just hard > depend on the documentation, but let's not go crazy here..) I completely agree. The very reason I am pushing for my emacs22 package (or, if some other Ubuntu core developer wants to maintain it instead, their package) rather than Debian's is because I do not want to see the documentation and GNU Manifesto stripped out into a separate "nondfsg" package. > For gutsy, I think we should decide if we want to ship with > 'emacs-snapshot', go to experimental's emacs22 package, or work on a > dedicated 'ubuntu emacs22' package. How about both my emacs22 package, and also an updated version of Romain's emacs-snapshot (still packaged as emacs-snapshot)? -- Michael Olson -- FSF Associate Member #652 | http://mwolson.org/ -- Jabber: mwolson_at_hcoop.net | /` |\ | | | Sysadmin -- Hobbies: Lisp, GP2X, HCoop| |_] | \| |_| Projects: Emacs, Muse, ERC, EMMS, ErBot, DVC, Planner | -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Preparing the way for emacs22 with many individual package updates
CC'ing Romain, since I think this might be interesting for him. Michael Olson <[EMAIL PROTECTED]> writes: > I'm starting to go through each of the Emacs Lisp packages I use and > make certain that they would work with a theoretical emacs22 package. > I've also fixed lintian warnings and other errors along the way, and > submitted fixes back to the Debian package maintainers. I'm currently using emacs22 from the emacs-snapshot package in gutsy. In fact, it was me who requested the sync from Romain's private archive. I'm not sure if you are aware of this fact. In fact, there is already an emacs22 package in debian/experimental. What I wanted to ask you is: Are you working on that package, or on Romain's emacs-snapshot package? Or are you working on your own emacs22 package? In any case, why? The problem I see with debian's package is that is strips of documentation in another source package, something that we don't need nor want in ubuntu (well, we could make our lives easy and just hard depend on the documentation, but let's not go crazy here..) For gutsy, I think we should decide if we want to ship with 'emacs-snapshot', go to experimental's emacs22 package, or work on a dedicated 'ubuntu emacs22' package. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 pgpawb2fcw7Mi.pgp Description: PGP signature -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
