On Sun, Mar 20, 2005 at 08:26:25AM +0100, Bastian Blank wrote:
> On Sat, Mar 19, 2005 at 09:39:56PM -0800, Steve Langasek wrote:
> > Both devmapper and dash are packages with RC bugs in unstable that need to
> > get into sarge.
> You forget lvm2.
What RC bug does the lvm2 update fix? I don't see
Steve Langasek <[EMAIL PROTECTED]> writes:
> > It seems to me that if a package is in NEW in order to fix a bug in
> > testing (especially an important or higher severity bug), then we
> > shouldn't freeze until the bug fix has propogated throught NEW
> > processing.
>
> Generally, yes. I don't
On Mon, Mar 21, 2005 at 07:18:45PM -0800, Thomas Bushnell BSG wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:
> > Because NEW processing is a treadmill, and not a release issue except in
> > select cases.
> Right, let me be more precise about what I'm suggesting.
> It seems to me that if a p
Steve Langasek <[EMAIL PROTECTED]> writes:
> On Mon, Mar 21, 2005 at 06:32:32PM -0800, Thomas Bushnell BSG wrote:
>
> > Can my lilypond upload (2.2.6-3) be pushed into testing despite
> > lacking arm binaries?
>
> Not without a reasonable expectation that mftrace itself will build
> successfully
On Mon, Mar 21, 2005 at 06:32:32PM -0800, Thomas Bushnell BSG wrote:
> Can my lilypond upload (2.2.6-3) be pushed into testing despite
> lacking arm binaries?
Not without a reasonable expectation that mftrace itself will build
successfully on arm.
> I would like the new lilypond to get exposure
Steve Langasek <[EMAIL PROTECTED]> writes:
> Because NEW processing is a treadmill, and not a release issue except in
> select cases.
Right, let me be more precise about what I'm suggesting.
It seems to me that if a package is in NEW in order to fix a bug in
testing (especially an important or h
On Mon, Mar 21, 2005 at 07:11:55PM -0800, Thomas Bushnell BSG wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:
> > Well, speaking as a gnucash user, I'd appreciate it if the spurious
> > dependencies were dropped ASAP, rather than waiting on a new library version
> > that might not make it out
Steve Langasek <[EMAIL PROTECTED]> writes:
> Well, speaking as a gnucash user, I'd appreciate it if the spurious
> dependencies were dropped ASAP, rather than waiting on a new library version
> that might not make it out of the NEW queue before we freeze.
Ok, I'll do what I can.
(Why not wait
Thomas,
On Mon, Mar 21, 2005 at 06:29:08PM -0800, Thomas Bushnell BSG wrote:
> Thanks for pushing gnucash into testing before the arm build
> finished. It's now been installed (along with grisbi and libofx, the
> packages tied to it) and the arm version should migrate too. I don't
> know whethe
Can my lilypond upload (2.2.6-3) be pushed into testing despite
lacking arm binaries? It's waiting because the new version of mftrace
is a build dependency: mftrace is number 182 on the arm list, because
it's priority extra.
I would like the new lilypond to get exposure since it is quite
possibl
Thanks for pushing gnucash into testing before the arm build
finished. It's now been installed (along with grisbi and libofx, the
packages tied to it) and the arm version should migrate too. I don't
know whether this happens automatically or not.
I would like to fix the bad advice I took on the
Bela,
I just net-installed Sarge on my new gateway with a sata HD. I had to
type "linux26" at the boot prompt. Otherwise, sarge would load the
default 2.4.xx kernel and would not find the HD.
good luck,
--Hannuman
belahcene wrote:
Hello world,
I 've just gotten a dell PC with sata controller HD
Hello world,
I 've just gotten a dell PC with sata controller HD ( model is ata ST3
800 13AS, driver ata_piix ), I tryed to install sarge ( netinstall
dowloaded in Dec 2004), but it is not recognized, while SL 3 (
scientific Linux based on RH , downloaded in Feb 2005 ) and Fedora
core
Newest penis enlargement system:
-Increases the penis length and girth
-Medically Proven (source: wikipedia)
-No Surgery
-Permanent Results
-Proven Traction Method
-100% Satisfaction Guaranteed
Find more info here:
http://www.lnches.com/e/viks
you whitewash me admire me you mullig
On Mon, 21 Mar 2005 13:10:09 +0100, Colin Watson wrote:
> This doesn't look right:
>
> - ;;
> - restart)
> - $0 start
> ;;
> *)
> echo "Usage: $0 {start|stop|restart|force-reload}" >&2
>
> i.e. "restart" argument implementa
Quoting Steve Langasek
> > The reason for my mail is that I thought new upstream releases
> > were not allowed.
>
> New upstream versions are discouraged; but we are not in a freeze. This
> particular emacs build includes security fixes we've been waiting on for a
> while.
Alright.
> > > $ grep
On Mon, Mar 21, 2005 at 01:25:42PM +0100, Jérôme Marant wrote:
> Quoting Steve Langasek <[EMAIL PROTECTED]>:
> > On Mon, Mar 21, 2005 at 10:59:28AM +0100, Jérôme Marant wrote:
> > > Emacs 21.4a-1 has been built in all architectures. It is basically 21.3
> > > plus the security patch which was appli
On Mon, Mar 21, 2005 at 01:25:42PM +0100, Jérôme Marant wrote:
> Quoting Steve Langasek <[EMAIL PROTECTED]>:
> > On Mon, Mar 21, 2005 at 10:59:28AM +0100, Jérôme Marant wrote:
> > > Emacs 21.4a-1 has been built in all architectures. It is basically 21.3
> > > plus the security patch which was appl
Quoting Steve Langasek <[EMAIL PROTECTED]>:
> On Mon, Mar 21, 2005 at 10:59:28AM +0100, Jérôme Marant wrote:
> > Emacs 21.4a-1 has been built in all architectures. It is basically 21.3
> > plus the security patch which was applied in 21.3+1-9, a fix for
> > a seriaous bug in debian/rules preventin
Adrian,
On Thu, Mar 17, 2005 at 07:58:30AM +0100, Adrian von Bidder wrote:
> [please cc: me, I don't read -release]
> In postgrey^s logcheck patterns, I have a made a minor mistake (a single
> occasional message which is not ignored as it should be.)
> I feel silly doing a new upload for a one
On Wed, Mar 16, 2005 at 08:47:25AM +, [EMAIL PROTECTED] wrote:
> ifupdown 0.6.4-4.12 was prepared with sarge in mind. The changes were
> limited to documentation improvements, low risk code tweaks and a
> necessary bugfix. -4.11 was uploaded two weeks ago and -4.12 was
> uploaded eleven days
On Mon, Mar 21, 2005 at 10:59:28AM +0100, Jérôme Marant wrote:
> Emacs 21.4a-1 has been built in all architectures. It is basically 21.3
> plus the security patch which was applied in 21.3+1-9, a fix for
> a seriaous bug in debian/rules preventing from building in some cases,
> as well as usual bug
Dear release managers,
Emacs 21.4a-1 has been built in all architectures. It is basically 21.3
plus the security patch which was applied in 21.3+1-9, a fix for
a seriaous bug in debian/rules preventing from building in some cases,
as well as usual bugfixes.
I think it can safely enter testing.
23 matches
Mail list logo
