Re: RFC: Better formatting for long descriptions

On Wed, 8 Apr 2009, Guillem Jover wrote: There's been a wiki page trying to track this, including packages which formatting was proving problematic: Great. The most important information from this page for myself is that ther

Re: Improvements to ‘debian/watch’ for fetching from VCS

On Tue, Apr 07 2009, Ben Finney wrote: > (Why was Manoj's message also sent individually to me?) > > On 07-Apr-2009, Manoj Srivastava wrote: >> If the current version is what we are interested, why not >> get it from the canonical site, the Debian archive? > > The Debian archive is

Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby

Sebastien Delafond dijo [Tue, Apr 07, 2009 at 02:17:09PM -0700]: > On Apr/07, Mike Hommey wrote: > > But why a need for two versions at a time ? AFAICS, jruby 1.2 supports > > both ruby 1.8 *and* 1.9, as jruby 1.1 does, so why would jruby 1.1 > > still be needed ? > > As I said in my other mail, f

Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby

Sebastien Delafond dijo [Tue, Apr 07, 2009 at 01:59:00PM -0700]: > On Apr/07, Mike Hommey wrote: > > While I see why it can be needed for python, I fail to see how it is > > important for jruby... > > to have 2 versions of jruby available ? I guess so you can at least, for > instance, try the new

Re: "Team uploads"

Matthew Johnson dijo [Mon, Apr 06, 2009 at 08:24:44AM +0100]: > > It is a useful concept, but I would like to consider them as "special > > case NMUs" rather than "special case MUs". > > Quite apart from the issue of deciding whether or not something is 'team > maintained' in all cases, if you are

Re: RFC: Better formatting for long descriptions

Hi! On Mon, 2009-03-23 at 16:23:12 -0700, Daniel Burrows wrote: > I don't have the energy to push this any more, but I should probably > at least refer to my previous attempt to standardize bulleted lists: > > http://lists.debian.org/debian-devel/2005/12/msg00531.html > > You might find it u

Re: autoconf method in ifupdown

Hi! On Sun, 2009-03-29 at 18:00:14 +0100, Thomas Preud'homme wrote: > I was looking a method to just have ipv6 with autoconf network and > found this patch > http://mlblog.osdir.com/linux.debian.devel.ipv6/2005-05/msg00012.shtml This link didn't seem to work, got this instead:

Re: Writing symbols files for C++ libraries.

Daniel Kobras schrieb: > On Tue, Apr 07, 2009 at 12:15:19PM +0200, Josselin Mouette wrote: >> Le mardi 07 avril 2009 à 11:57 +0200, Mike Hommey a écrit : >>> I found nothing better than using a version script. I'm lucky that the >>> library in question (WebKit) only really exports C symbols, and C+

Re: Writing symbols files for C++ libraries.

On Tue, Apr 07, 2009 at 12:15:19PM +0200, Josselin Mouette wrote: > Le mardi 07 avril 2009 à 11:57 +0200, Mike Hommey a écrit : > > I found nothing better than using a version script. I'm lucky that the > > library in question (WebKit) only really exports C symbols, and C++ is only > > internal det

Re: Improvements to ‘debian /watch’ for fetching from VCS

On Wed, Apr 08, 2009 at 09:04:21AM +1000, Ben Finney wrote: > (Why was Manoj's message also sent individually to me?) > > On 07-Apr-2009, Manoj Srivastava wrote: > > If the current version is what we are interested, why not > > get it from the canonical site, the Debian archive? > >

Re: Improvements to ‘debian/watch’ for fetching from VCS

(Why was Manoj's message also sent individually to me?) On 07-Apr-2009, Manoj Srivastava wrote: > If the current version is what we are interested, why not > get it from the canonical site, the Debian archive? The Debian archive is *not* the canonical location for the upstream's o

Re: lilo about to be dropped?

I demand that William Pitcock may or may not have written... [snip] > So at this point, our only option seems to be taking over upstream lilo > maintainance ourselves (which could be a good thing in some ways, I am > not denying that), I say go for it... > or find a way to transition these use-c

Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby

On Tue, Apr 07, 2009 at 02:17:09PM -0700, Sebastien Delafond wrote: > On Apr/07, Mike Hommey wrote: > > But why a need for two versions at a time ? AFAICS, jruby 1.2 supports > > both ruby 1.8 *and* 1.9, as jruby 1.1 does, so why would jruby 1.1 > > still be needed ? > > As I said in my other mail

Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby

On Apr/07, Mike Hommey wrote: > But why a need for two versions at a time ? AFAICS, jruby 1.2 supports > both ruby 1.8 *and* 1.9, as jruby 1.1 does, so why would jruby 1.1 > still be needed ? As I said in my other mail, for transition reasons; backward-compatibility is something many people like t

Re: lilo about to be dropped?

On Mon, 06 Apr 2009 10:24:54 -0500 William Pitcock wrote: > On Mon, 2009-04-06 at 16:17 +0200, Harald Braumann wrote: > > Yes, I do and it works without problems. There are some > > inconveniences, though, with grub2, which might make some stick > > with LILO: > > The LVM support in LILO is hide

Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby

On Apr/07, Mike Hommey wrote: > While I see why it can be needed for python, I fail to see how it is > important for jruby... to have 2 versions of jruby available ? I guess so you can at least, for instance, try the new one on your existing jruby code without removing the old one, for instance ?

Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby

On Tue, Apr 07, 2009 at 01:40:54PM -0700, Sebastien Delafond wrote: > On Apr/07, Adeodato Simó wrote: > > The question was, rather: why would a user want to install jruby1.0 or > > jruby1.1 instead of jruby1.2? What purpose does it serve having three > > different versions in the archive instead of

Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby

On Apr/07, Adeodato Simó wrote: > The question was, rather: why would a user want to install jruby1.0 or > jruby1.1 instead of jruby1.2? What purpose does it serve having three > different versions in the archive instead of one, or two at most? jruby1.0 will indeed be removed shortly from the arch

Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby

On Tue, Apr 07, 2009 at 01:08:17PM -0700, Sebastien Delafond wrote: > On Apr/07, Mike Hommey wrote: > > Why do we need jruby1.0, jruby1.1 and now jruby1.2 ? > > so multiple versions of jruby can be simultaneously installed on a > system, like with python2.x, ruby1.x, etc ? While I see why it can

Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby

+ Sebastien Delafond (Tue, 07 Apr 2009 13:08:17 -0700): > On Apr/07, Mike Hommey wrote: > > Why do we need jruby1.0, jruby1.1 and now jruby1.2 ? > so multiple versions of jruby can be simultaneously installed on a > system, like with python2.x, ruby1.x, etc ? The question was, rather: why would

Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby

On Apr/07, Mike Hommey wrote: > Why do we need jruby1.0, jruby1.1 and now jruby1.2 ? so multiple versions of jruby can be simultaneously installed on a system, like with python2.x, ruby1.x, etc ? Cheers, --Seb -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of

Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby

On Tue, Apr 07, 2009 at 12:09:56PM -0700, Sebastien Delafond wrote: > Package: wnpp > Severity: wishlist > Owner: Sebastien Delafond > > > > * Package name: jruby1.2 > Version : 1.2.0 > Upstream Author : The JRuby Team > * URL : http://jruby.codehaus.org/ > * License

Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby

Package: wnpp Severity: wishlist Owner: Sebastien Delafond * Package name: jruby1.2 Version : 1.2.0 Upstream Author : The JRuby Team * URL : http://jruby.codehaus.org/ * License : tri-license CPL/GPL/LGPL Programming Lang: Java Description : 100% pure

Re: lilo about to be dropped?

William Pitcock (07/04/2009): > Alternatively, we can just leave it and let it become another XMMS. I > don't like this solution very much. Beware, gtk3 is coming, so you'd better update lilo to no longer depend on gtk2! Mraw, KiBi. signature.asc Description: Digital signature

Re: lilo about to be dropped?

On Tue, 2009-04-07 at 13:06 -0300, Otavio Salvador wrote: > On Mon, Apr 6, 2009 at 9:21 PM, William Pitcock > wrote: > > Lilo upstream is dead (no release in quite a while), but the lilo > > maintainer has also been seen as saying in various mailing lists etc, > > that since Debian patches lilo th

Re: Why do we have to support tmpfs for /var/run (policy changes in 3.8.1)

Giacomo A. Catenazzi dijo [Tue, Apr 07, 2009 at 11:05:35AM +0200]: > In Debian policy: > : The init.d scripts must ensure that they will behave sensibly > : (i.e., returning success and not starting multiple copies of a > : service) if invoked with start when the service is already running, > : or

Bug#522984: ITP: magics++ -- Meteorological plotting software

Package: wnpp Severity: wishlist Owner: Alastair McKinstry * Package name: magics++ Version : 2.6.4 Upstream Author : ECMWF * URL : http://www.ecmwf.int/products/data/software/magics++.html * License : Apache license, version 2. Programming Lang: C, Fortran

Re: lilo about to be dropped?

On Tue, Apr 07, 2009 at 07:36:40AM +0200, Mike Hommey wrote: > On Mon, Apr 06, 2009 at 11:10:25PM +0200, Iustin Pop wrote: > > On Mon, Apr 06, 2009 at 11:42:42AM -0500, William Pitcock wrote: > > > On Mon, 2009-04-06 at 18:19 +0200, Vincent Zweije wrote: > > > > On Mon, Apr 06, 2009 at 06:06:38PM +

Re: lilo about to be dropped?

On Tue, 2009-04-07 at 10:52 +0200, Giacomo A. Catenazzi wrote: > Stephen Gran wrote: > > This one time, at band camp, William Pitcock said: > >> The only way it is feasible to do so is to drop all of the Debian > >> patches. Without this, upstream is not cooperative with us. > > > > Why is this? >

Re: RFA: acpi-support -- glue layer for translating laptop buttons, plus legacy suspend support

On Tue, Apr 07, 2009 at 01:26:18PM +0200, Petter Reinholdtsen wrote: > [Michael Biebl] > > As (co-)maintainer of pm-utils and hal, I'd prefer if we could work > > towards standardizing on one power management stack in Debian (and > > not install 3 by default [1]), i.e. I'd support in phasing out >

Re: tdiff (DEP-4: The TDeb specification.)

On Tue, 07 Apr 2009 09:57:30 -0400 Filipus Klutiero wrote: (Could you add a blank line between the quoted reply and your content? It makes the content easier for me to read. Thanks.) > Neil Williams wrote: > > On Mon, 06 Apr 2009 01:13:19 -0400 > > Filipus Klutiero wrote: > > > > > > > > > That

Re: "Team uploads"

Raphael Hertzog writes: > On Mon, 06 Apr 2009, Russ Allbery wrote: >> Charles Plessy writes: >>> so in the end, can we use the “ * QA upload.” special first line for >>> non-uploader uploads without breaking the QA infrastructure? >> No, that is reserved for orphaned packages and triggers other

Re: .tdeb format (DEP-4: The TDeb specification.)

On Tue, 07 Apr 2009 10:23:37 -0400 Filipus Klutiero wrote: > > In a similar way to udebs. The .tdeb needs to be handled differently by > > package management tools (things like reprepro and dak) so that uploads > > of TDebs can be made by translation teams, so that the existing source > > package

Re: Improvements to ‘debian /watch’ for fetching from VCS

On Tue, Apr 07, 2009 at 10:06:18AM -0500, Manoj Srivastava wrote: > If the current version is what we are interested, why not get it > from the canonical site, the Debian archive? I am a new maintainer, and I have sponsors for various packages. People can check out the source code, and r

Re: lilo about to be dropped?

On Mon, Apr 6, 2009 at 9:21 PM, William Pitcock wrote: > Lilo upstream is dead (no release in quite a while), but the lilo > maintainer has also been seen as saying in various mailing lists etc, > that since Debian patches lilo that he has no interest in helping to fix > problems in our version.

Re: Improvements to ‘debian /watch’ for fetching from VCS

On Tue, Apr 07, 2009 at 10:00:05AM -0500, Manoj Srivastava wrote: > On Sat, Apr 04 2009, Noah Slater wrote: > > As a concrete benefit, my nightly cron to check uscan for all my > > packages will be able to alert me about the ones pulled from > > repository revisions, all I would need to do is add a

Re: Forthcoming changes in kernel-package

Hi, A few hours ago, a new version of kernel-package was uploaded to Experimental. This is a major change, the new kernel-package is far more nimble, more flexible, and supports people who make a minor change to a kernel, or who update the kernel sources (via git or otherwise), and wa

Re: Improvements to ‘debian/watch’for fetching f rom VCS

On Tue, Apr 7, 2009 at 11:06 PM, Manoj Srivastava wrote: >        What am I missing? One case I can think of; it is (possibly) common for sponsors to check that the result from get-orig-source matches the contents of the tarball uploaded to mentors by the sponsee. -- bye, pabs http://wiki.debi

Re: Improvements to ‘debian/watch’ for fetching from VCS

On Thu, Apr 02 2009, Noah Slater wrote: > On Fri, Apr 03, 2009 at 10:50:11AM +1100, Ben Finney wrote: >> That's the trouble though. AIUI, different VCSen have different ways >> of identifying a specific state of the working tree; we have not only >> revisions, but also tags, branches, threads, hea

Re: Forthcoming changes in kernel-package

On Thu, Feb 26 2009, Theodore Tso wrote: > On Fri, Feb 20, 2009 at 12:56:30PM -0600, Manoj Srivastava wrote: >> > BTW, I have a set of patches you might want to consider. I'll file >> > them in BTS if you're currently making make-kpkg. >> >> Please. I have been thinking about the request

Re: Improvements to ‘debian/watch’ for fetching from VCS

On Sat, Apr 04 2009, Noah Slater wrote: > On Sat, Apr 04, 2009 at 01:35:17PM -0600, Raphael Geissert wrote: >> opts=handler=svn http://domain.tld/svn/foo/...> >> would do the right thing. > > What about uscan being able to use custom make targets in debian/rules? > > There could be a way to tell u

.tdeb format (DEP-4: The TDeb specification.)

> > Package management tools need a way to tell a .deb from a .tdeb - the > > two need to be handled differently by tools like dak, britney, apt, > > dpkg, reprepro, deb-gview and others. > Do you mean that package management tools need a way to tell a > traditional/current .deb from a package

tdiff (DEP-4: The TDeb specification.)

Neil Williams wrote: On Mon, 06 Apr 2009 01:13:19 -0400 Filipus Klutiero wrote: > > > > > That would be a nice improvement, but let me suggest another > > > > > implementation. To avoid introducing a second diff, why not updating the > > > > > regular diff (in the case of non-native packages)

Bug#522934: ITP: python-whoosh -- pure-Python full text indexing, search, and spell checking library

Package: wnpp Severity: wishlist Owner: Daniel Watkins * Package name: python-whoosh Version : 0.1.13 Upstream Author : Matt Chaput * URL : http://whoosh.ca * License : Apache Programming Lang: Python Description : pure-Python full-text indexing, searc

Re: "Team uploads"

On Mon, 06 Apr 2009, Russ Allbery wrote: > Charles Plessy writes: > > so in the end, can we use the “ * QA upload.” special first line for > > non-uploader uploads without breaking the QA infrastructure? > > No, that is reserved for orphaned packages and triggers other checks to > ensure the main

D-I not using grub (was: lilo about to be dropped?)

Let's move this subthread back to d-boot. Reply-to set. Please let us know if you'd like to be CCed. Martin Wuertele wrote: > * Frans Pop [2009-04-07 02:54]: > >> Martin Wuertele wrote: >> > Actually lilo is installed by lenny d-i if you use root-sw-raid with >> > LVM, even if your /boot is an d

Bug#522924: ITP: agda-stdlib -- standard library for Agda - a dependently typed functional programming language and proof assistant

Package: wnpp Severity: wishlist Owner: Iain Lane * Package name: agda-stdlib Version : unreleased Upstream Author : Nils Anders Danielsson * URL : http://wiki.portal.chalmers.se/agda/agda.php?n=Libraries.StandardLibrary * License : MIT/X Programming Lang:

Bug#522921: ITP: haskell-ifelse -- Anaphoric and miscellaneous useful control-flow

Package: wnpp Severity: wishlist Owner: "Marco Túlio Gontijo e Silva" * Package name: haskell-ifelse Version : 0.85 Upstream Author : Jeff R. Heard and Wren Thornton * URL : http://hackage.haskell.org/cgi-bin/hackage-scripts/package/IfElse * License : BSD P

depending on obsolete packages

One finds packages depending on obsolete packages, e.g., # aptitude -F %p search ?obsolete | xargs -n 1 echo aptitude why|sh -x + aptitude why libicu38 i gimpDepends libwebkit-1.0-1 (>= 1.0.1) i A libwebkit-1.0-1 Depends libicu38 (>= 3.8-5) + aptitude why libltdl3 i php5-mcrypt Depe

Bug#522914: ITP: agda -- a dependently typed functional programming language and proof assistant

Package: wnpp Severity: wishlist Owner: Iain Lane * Package name: agda Version : 2.2.0 Upstream Author : Ulf Norell * URL : http://wiki.portal.chalmers.se/agda/ * License : MIT/X11 Programming Lang: Haskell Description : a dependently typed functional

Re: RFA: acpi-support -- glue layer for translating laptop buttons, plus legacy suspend support

[Michael Biebl] > As (co-)maintainer of pm-utils and hal, I'd prefer if we could work > towards standardizing on one power management stack in Debian (and > not install 3 by default [1]), i.e. I'd support in phasing out > acpi-support and would gladly accept patches for hal and pm-utils > which add

Re: DEP-4: The TDeb specification.

On Mon, 06 Apr 2009 01:13:19 -0400 Filipus Klutiero wrote: > > > > > That would be a nice improvement, but let me suggest another > > > > > implementation. To avoid introducing a second diff, why not updating > > > > > the > > > > > regular diff (in the case of non-native packages) but indicat

Re: Writing symbols files for C++ libraries.

On Tue, Apr 07, 2009 at 12:15:19PM +0200, Josselin Mouette wrote: > Le mardi 07 avril 2009 à 11:57 +0200, Mike Hommey a écrit : > > I found nothing better than using a version script. I'm lucky that the > > library in question (WebKit) only really exports C symbols, and C++ is only > > internal d

Re: Writing symbols files for C++ libraries.

Le mardi 07 avril 2009 à 11:57 +0200, Mike Hommey a écrit : > I found nothing better than using a version script. I'm lucky that the > library in question (WebKit) only really exports C symbols, and C++ is only > internal details, so I'm filtering everything that starts with _Z, now. BTW, for such

Re: Writing symbols files for C++ libraries.

On Tue, Apr 07, 2009 at 01:22:51AM +0200, Daniel Kobras wrote: > Hi! > > I'm currently fighting with deb symbols files for a C++ library I'm > packaging, and I'd like to get some insight in how others are coping > with this task. In particular, I wonder how to get rid of symbols from > standard

Writing symbols files for C++ libraries.

Hi! I'm currently fighting with deb symbols files for a C++ library I'm packaging, and I'd like to get some insight in how others are coping with this task. In particular, I wonder how to get rid of symbols from standard template instances that leak into the ABI, eg. $ cat test.cpp #include st

Transition from libmysqlclient15 to libmysqlclient16

Hi, I plan to move MySQL 5.1 from experimental to unstable really soon now, MySQL 5.0 will be dropped from Debian at the same time. This means 215 packages need to be rebuild. There should be no changes necessary on these packages, a simple rebuild should do it. Norbert -- To UNSUBSCR

Re: Why do we have to support tmpfs for /var/run (policy changes in 3.8.1)

On Mon, 2009-04-06 at 20:42 +0200, Michael Biebl wrote: > Steve Langasek wrote: > > I think he's referring to the fact that the FHS requires all files in > > /var/run to be cleared on boot. We have an init script > > (/etc/rcS.d/S36mountall-bootclean) that takes care of this at the system > > leve

Re: lilo about to be dropped?

On Mon, Apr 06, 2009 at 11:10:25PM +0200, Iustin Pop wrote: > On Mon, Apr 06, 2009 at 11:42:42AM -0500, William Pitcock wrote: > > On Mon, 2009-04-06 at 18:19 +0200, Vincent Zweije wrote: > > > On Mon, Apr 06, 2009 at 06:06:38PM +0200, Mike Hommey wrote: > > > > > > || On Mon, Apr 06, 2009 at 08:

Re: lilo about to be dropped?

On Mon, 2009-04-06 at 22:20 +0100, Stephen Gran wrote: > This one time, at band camp, William Pitcock said: > > The only way it is feasible to do so is to drop all of the Debian > > patches. Without this, upstream is not cooperative with us. > > Why is this? See my other mail, basically, lilo ups

Re: "Team uploads"

Charles Plessy writes: > Le Mon, Apr 06, 2009 at 11:51:54AM -0700, Russ Allbery a écrit : >> There still should be some humans in Maintainer/Uploaders who are >> taking primary responsibility for the package, but I think other team >> members should be able to do QA-style fixes and transition upl

Re: lilo about to be dropped?

Harald Braumann wrote: > * configuration of grub2 is really a PITA > > You can't specify boot options per entry (there's only a global option > in /etc/default grub, that applies to all entries). You may want to check bug 470398. The patch is probably outdated by now, though. Requiring bug/patch

Re: lilo about to be dropped?

* Frans Pop [2009-04-07 02:54]: > Martin Wuertele wrote: > > Actually lilo is installed by lenny d-i if you use root-sw-raid with > > LVM, even if your /boot is an differen partition/sw-raid. Therefore lilo > > should at least remain for sqeeze to ensure a proper upgrade path. > > I'm afraid you

Re: Why do we have to support tmpfs for /var/run (policy changes in 3.8.1)

Gunnar Wolf wrote: It does achieve not having bogus information on. If your system crashed, some crappy daemons will refuse to start if /var/run/crappyserver.pid exists, or will try to communicate with their peers using /var/run/sloppydaemon.socket, possibly failing cleanly, but possibly leading

Re: lilo about to be dropped?

Stephen Gran wrote: This one time, at band camp, William Pitcock said: The only way it is feasible to do so is to drop all of the Debian patches. Without this, upstream is not cooperative with us. Why is this? I think because of William Pitcock with: - his very strong words, - his attitude:

Re: lilo about to be dropped?

]] William Pitcock | Have you looked into ext2linux? It is intended to supercede lilo. I | think your usage requirements will be satisfied by it. It does not appear to exist in Debian? -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, ema

Re: lilo about to be dropped?

On Mon, 2009-04-06 at 18:46 +0200, Christian Perrier wrote: > Quoting Frans Pop (elen...@planet.nl): > > > I'm not sure where the original mail comes from, but IMO this should be > > From lilo package BTS which I was tracking for l10n purposes. So I > just happened to notice William's answer to

Re: UDD gatherer for DDTP translations (Was: Extended descriptions size)

On Sun, 5 Apr 2009, Martijn van Oosterhout wrote: While I'm not against the idea of version numbers (though it would have to be a list since a single translation may apply to dozens of versions) This might be discussed. it's not that hard to identify the description you want. What I often di

Re: "Team uploads"

On Tue Apr 07 10:38, Charles Plessy wrote: > so in the end, can we use the “ * QA upload.” special first line for > non-uploader uploads without breaking the QA infrastructure? That's wrong if the maintainer is not debian...@lists. Matt -- Matthew Johnson signature.asc Description: Digital si