On Sun, May 08, 2011 at 05:24:09AM +0100, Ben Hutchings wrote:
> On Sat, 2011-05-07 at 22:43 -0400, Ted Ts'o wrote:
> [...]
> > Should we try to make this work (at best badly) since a change in
> > mount options in /etc/fstab would only take effect at the next
> > mkinitramfs and/or update-grub inv
On Sat, 2011-05-07 at 22:43 -0400, Ted Ts'o wrote:
[...]
> Should we try to make this work (at best badly) since a change in
> mount options in /etc/fstab would only take effect at the next
> mkinitramfs and/or update-grub invocation? Or should we just close
> out this bug and say, "tough luck, ki
reassign 616317 base
thanks
This isn't a bug in e2fsprogs; e2fsprogs has absolutely nothing to do
with mounting the file system.
Debian simply doesn't support the mount options for the root file
system in /etc/fstab having any effect on how the root file system is
mounted. The root file system i
Le Sat, May 07, 2011 at 03:43:11PM +0200, Enrico Zini a écrit :
>
> a GR was needed to be able to proceed, because the hands of FD were
> rather tied by this other GR: http://www.debian.org/vote/2008/vote_002
Hi Enrico,
the 2008 GR invites to seek consensus, and in my opinion, what prove to be
a
On Sat, 07 May 2011, Tollef Fog Heen wrote:
> | The problem is that autoreconf offers NO command line options for you to
> | pass the required -I parameters for aclocal, nor is there a way to encode
> | that information in the one place where it could conveniently live
> | (configure.ac) AFAIK.
>
On Sat, 07 May 2011 at 13:33:53 +0200, Enrico Weigelt wrote:
> c) does _NOT_ call configure
As much as I wish this had been the convention, it isn't - the convention is
that autogen.sh *does* call ./configure (often with options suitable for
developers of the project, whereas the ./configure defau
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
* Package name: ruby-shoulda-context
Version : 1.0.0.beta1
Upstream Author : Several authors
* URL : https://github.com/thoughtbot/shoulda-context
* License : MIT
Programming Lang: Ruby
Description
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
* Package name: ruby-shoulda-matchers
Version : 1.0.0.beta2
Upstream Author : Several authors
* URL : https://github.com/thoughtbot/shoulda-matchers
* License : MIT
Programming Lang: Ruby
Description
* Henrique de Moraes Holschuh schrieb:
> > I'm (as upstream) using serval macros in their own .m4 files (eg.
> > in ./m4/, maybe even sorted into subdirs). Can autoreconf figure
> > out the required search pathes all on its own ?
>
> The problem is that autoreconf offers NO command line options
]] Henrique de Moraes Holschuh
Hiya,
| The problem is that autoreconf offers NO command line options for you to
| pass the required -I parameters for aclocal, nor is there a way to encode
| that information in the one place where it could conveniently live
| (configure.ac) AFAIK.
Can't you use
On Sat, 07 May 2011, Enrico Weigelt wrote:
> * Henrique de Moraes Holschuh schrieb:
> > Yes. I think it was Cyrus IMAP that required -I in places where
> > autoreconf doesn't reach, so I called each tool separately. Which is
> > obviously a problem in autoreconf.
>
> Is it really a problem of a
On Sat, May 07, 2011 at 12:25:15PM +0200, Aurelien Jarno wrote:
> On Wed, May 04, 2011 at 02:30:35PM +0200, Aurelien Jarno wrote:
> > Le 04/05/2011 07:42, Steve M. Robbins a écrit :
> > > P.S. I tried rebuilding glibc myself locally, but gcc also segfaults
> > > in the process :-(
> >
> > Are yo
On Fri, 6 May 2011, Chris Warburton wrote:
On Fri, 2011-05-06 at 11:29 -0400, Scott Kitterman wrote:
On Friday, May 06, 2011 11:23:50 AM Tshepang Lekhonkhobe wrote:
On Fri, 2011-05-06 at 09:11 -0400, Scott Kitterman wrote:
On Friday, May 06, 2011 08:56:21 AM Chris Warburton wrote:
Programm
Enrico Zini wrote:
> On Fri, May 06, 2011 at 02:04:20PM -0400, Michael Gilbert wrote:
>
> > It wasn't the GR itself. It was the fact that these changes to the NM
> > process were actually made. I suppose it is arguable that those changes
> > simply would not have happened without the GR, but that
On Tue, May 03, 2011 at 03:05:34PM +0200, Pierre Habouzit wrote:
> I know it's not simple, but it's not necessarily harder than making
> testing usable, I think Joss made a pretty good case about that on his
> blog.
FWIW (#1), for the non-planet readers this is at
http://np237.livejournal.com/3186
> As we already noted in our meeting minutes, there is one difference in
> the files that you might notice: The order of the fields within one
> entry is different. This should not create any trouble with compliant
> 822 parsers, as order does not matter, but in case you do some weird
> parsing on
On Sat, 7 May 2011 16:51:01 +0200
Enrico Weigelt wrote:
> * Neil Williams schrieb:
>
> > Nonsense. It is not the job of ./autogen.sh to revert to the VCS state
>
> It is it's job to produce a clean state where *all* generated
> files have been regenerated and the next stage (configure)
> can s
* Neil Williams schrieb:
> Nonsense. It is not the job of ./autogen.sh to revert to the VCS state
It is it's job to produce a clean state where *all* generated
files have been regenerated and the next stage (configure)
can start from here, w/o any manual intervention or workarounds.
> and there
On Sat, 7 May 2011 15:41:22 +0200
Enrico Weigelt wrote:
> * Neil Williams schrieb:
>
> > No. Reverting the build to the point where it is equivalent to only
> > what is in the VCS adds completely unnecessary build dependencies and
> > build stages.
>
> Which ones exactly (besides the usual aut
* Sean Finney schrieb:
IOW: all the fun of indeterministically self-modifying code ...
cu
--
--
Enrico Weigelt, metux IT service -- http://www.metux.de/
phone: +49 36207 519931 email: weig...@metux.de
mobile: +49 151 2
On Fri, May 06, 2011 at 02:04:20PM -0400, Michael Gilbert wrote:
> It wasn't the GR itself. It was the fact that these changes to the NM
> process were actually made. I suppose it is arguable that those changes
> simply would not have happened without the GR, but that indicates more
> of a lack of
* Neil Williams schrieb:
> No. Reverting the build to the point where it is equivalent to only
> what is in the VCS adds completely unnecessary build dependencies and
> build stages.
Which ones exactly (besides the usual autotools) ?
> VCS is not the final source, it's a tool for upstream to cr
Package: wnpp
Severity: wishlist
Owner: Georges Khaznadar
* Package name: wims-help
Version : 4.01
Upstream Authors : Bernadette Perrin-Riou ,
Marie-Claude David ,
Association WIMSEDU
* URL : http://www.wimsedu.info
* License
On Sat, May 07, 2011 at 12:51:46PM +0200, Jakub Wilk wrote:
> This works both ways. If a NMUer uploaded my package without a delay
> and without a good reason[0], I want to be able to yell at him „you
> are
> a jerk (according to Developers Reference)!”
>
> Unfortunately, clueless NMUers do exist.
On Sat, 7 May 2011 12:51:46 +0200
Jakub Wilk wrote:
> [0] No, 7 days without activity in the bug log is not a good enough
> reason. Let's turn our empathy on and face it: we are not bug-fixing
> monkeys and 7 days is a very short time frame.
It's 7 days without maintainer response - if you're
On Sat, 7 May 2011 13:33:53 +0200
Enrico Weigelt wrote:
> * Josue Abarca schrieb:
>
> > From: /usr/share/doc/autotools-dev/README.Debian.gz
> > "Example autogen.sh and debian/rules files can be found in
> > /usr/share/doc/autotools-dev/examples. Do not use them as-is. Rather,
> > properly cust
* Henrique de Moraes Holschuh schrieb:
> Yes. I think it was Cyrus IMAP that required -I in places where
> autoreconf doesn't reach, so I called each tool separately. Which is
> obviously a problem in autoreconf.
Is it really a problem of autoreconf ?
Imagine the following situation:
I'm (as
On Sat, 7 May 2011 13:48:00 +0200
Enrico Weigelt wrote:
> * Neil Williams schrieb:
>
> > Not every generated file needs to be cleaned. The list can vary if the
> > package is very old and depends on how the package itself handles the
> > clean internally.
>
> IMHO, *all* generated files should
* Henrique de Moraes Holschuh schrieb:
> 1. No spawn from autotooling allowed in the VCS. EVER. .gitignore it
>away at once. Autogenerated files inside the VCS repo are almost
>always a bad idea. It was madness with CVS, it was bad mojo with
>SVN, and it is certainly at least an a
Hi,
On Sat, 07 May 2011, Jakub Wilk wrote:
> This works both ways. If a NMUer uploaded my package without a delay
> and without a good reason[0], I want to be able to yell at him „you
> are a jerk (according to Developers Reference)!”
No.
First off, I never said that the rules are there to be ab
Le Fri, May 06, 2011 at 11:14:55PM +0200, Lucas Nussbaum a écrit :
>
> - The dev-ref documents the "default" choice. While there are cases where I
> agree that uploading the fixed package ASAP is necessary, in most cases, we
> can probably survive two more days with the bug, if we already surv
* Neil Williams schrieb:
> Not every generated file needs to be cleaned. The list can vary if the
> package is very old and depends on how the package itself handles the
> clean internally.
IMHO, *all* generated files should be cleaned away, just to be sure.
In the last decade I've encountered a
* Josue Abarca schrieb:
> From: /usr/share/doc/autotools-dev/README.Debian.gz
> "Example autogen.sh and debian/rules files can be found in
> /usr/share/doc/autotools-dev/examples. Do not use them as-is. Rather,
> properly customize your own."
>
> and from /usr/share/doc/autotools-dev/examples/a
* Raphael Hertzog , 2011-05-07, 09:12:
A patch was proposed (#625449) to implement in dvelopers-reference the
"DELAYED/0 for upload fixing only release-critical bugs older than 7
days, without maintainer activity for 7 days" policy.
I don't think that this policy is a good idea. But, since I w
On Wed, May 04, 2011 at 02:30:35PM +0200, Aurelien Jarno wrote:
> Le 04/05/2011 07:42, Steve M. Robbins a écrit :
> > On Wed, May 04, 2011 at 12:10:48AM -0500, Jonathan Nieder wrote:
> >
> >> Sounds like http://sourceware.org/bugzilla/show_bug.cgi?id=12518
> >> which is fixed (sort of) by commit 0
On Saturday 07 May 2011 09:41:34 Raphael Hertzog wrote:
> Hi,
Hi,
> On Fri, 06 May 2011, George Danchev wrote:
> > * writing a meaningful ITP helps to grab attention, especially if there
> > are multiple alternatives. Prove your point (ref: I'm upstream and I
> > want to maintain it, doesn't magi
On Fri, 06 May 2011, Lucas Nussbaum wrote:
> A patch was proposed (#625449) to implement in dvelopers-reference the
> "DELAYED/0 for upload fixing only release-critical bugs older than 7 days,
> without maintainer activity for 7 days" policy.
>
> I don't think that this policy is a good idea. But,
37 matches
Mail list logo
