On Tue, Aug 30, 2005 at 08:23:02PM -0400, Roberto C. Sanchez wrote:
> > Option a) doesn't seem particularly sensible to me, btw, because the
> > "risk" is near certain...
> Incidentally, is it possible to put udev on hold, upgrade everything
> else, install a new kernel and then select udev for up
On Wed, Aug 31, 2005 at 01:59:26AM +0200, Marco d'Itri wrote:
> On Aug 31, Steve Langasek <[EMAIL PROTECTED]> wrote:
>
> > If you aren't
> > satisfied with the current solution, the answer is to figure out a
> > better one rather than lamenting that no one else has. (I do have a
> This is where t
I didn't get as much done today as I was hoping, but some progress was
made. I've filed new RC bugs for the transition against:
blacs-mpi
scalapack
and have followed up to Bug#323744 with a more complete patch and an
additional note that this rebuild is needed for the transition.
I have
On Tue, Aug 30, 2005 at 08:23:02PM -0400, Roberto C. Sanchez wrote:
> On Tue, Aug 30, 2005 at 04:59:48PM -0700, Steve Langasek wrote:
> >
> > > Becuase I roll my own kernel. If I upgrade the kernel with gcc-3.3
> > > (currently the Sarge default) and then upgrade to Etch (which will have
> > > gc
On Aug 31, "Roberto C. Sanchez" <[EMAIL PROTECTED]> wrote:
> Incidentally, is it possible to put udev on hold, upgrade everything
> else, install a new kernel and then select udev for upgrade?
Everything else which does not depend on the new version of conflicts
with the old version, which will be
On Tue, Aug 30, 2005 at 12:05:02PM +0200, Petter Reinholdtsen wrote:
> In two days, dmidecode will have passed its 10 day waiting period, and
> should be ready to go into testing. As it is frozen (creating an
> udeb), I need help from someone to get it into testing. I start this
> discussion a b
Steve Langasek wrote:
I agree that it warrants documenting, though I also suspect
that most users running self-compiled 2.6 kernels are going to be
running something a bit newer than 2.6.8 anyway.
Exactly. As long as I didn't need such fresh features like vserver 2.0
or the latest v4l snapsho
On Tue, Aug 30, 2005 at 04:59:48PM -0700, Steve Langasek wrote:
>
> > Becuase I roll my own kernel. If I upgrade the kernel with gcc-3.3
> > (currently the Sarge default) and then upgrade to Etch (which will have
> > gcc-4.0 for a default) I will run into problems if I decide to add new
> > modul
On Tue, Aug 30, 2005 at 01:16:43PM -0400, Adam C Powell IV wrote:
> > > - Get someone to hand-build the new illuminator package on a sparc
> > > running 2.6. The drawbacks of this are that it hides the buildd issue
> > > rather than ensuring it gets fixed, and that sparc porters are
> > > cu
On Tue, Aug 30, 2005 at 01:06:39AM -0400, Roberto C. Sanchez wrote:
> On Mon, Aug 29, 2005 at 09:43:33PM -0700, Steve Langasek wrote:
> > > > 1) upgrade your kernel
> > > > 2) dist-upgrade
> > > > That doesn't seem terribly elaborate to me? And if people choose not to
> > > > read, well, they get
On Aug 31, Steve Langasek <[EMAIL PROTECTED]> wrote:
> If you aren't
> satisfied with the current solution, the answer is to figure out a
> better one rather than lamenting that no one else has. (I do have a
This is where these threads usually end...
--
ciao,
Marco
signature.asc
Description:
On Tue, Aug 30, 2005 at 11:48:17PM +0200, Frans Pop wrote:
> (pruning CC list; AFAIK all will still get the message this way)
> On Tuesday 30 August 2005 04:56, Steve Langasek wrote:
> > > So we're going to have another release with a very elaborate upgrade
> > > procedure in the release notes (wh
(pruning CC list; AFAIK all will still get the message this way)
On Tuesday 30 August 2005 04:56, Steve Langasek wrote:
> > So we're going to have another release with a very elaborate upgrade
> > procedure in the release notes (which a lot of users, especially
> > desktop users, don't read anyway
Adam C Powell IV <[EMAIL PROTECTED]> writes:
> I'm doing builds (and uploads) of the (non-free) parmetis and hypre as
> we speak, will address this dependency issue in hypre. I'm also fixing
> another couple of errors in parmetis, which will make shared lib deps
> work better for that package.
E
Hello,
Just catching up on Debian stuff and found this email... Let me reply
to the parts relevant to my packages.
On Mon, 2005-08-29 at 20:02 -0700, Russ Allbery wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:
>
> > Package: hypre
>
> Uses mpicc and therefore statically linked, and doesn'
On August 29, 2005 19:37, Frank Lichtenheld wrote:
> As Qt and kdelibs also have made their C++ transition in unstable we
> should be able to target allmost all g++ 4.0 related bugs this time. On
> the other hand this means that a Qt or kdelibs build-dependency is no
> excuse anymore for not fixing
On Tuesday 30 August 2005 12:05, Petter Reinholdtsen wrote:
> And wearing my non-di-developer hat, I must say that having my package
> frozen just because I was friendly and made an udeb available, is most
> inconvinient, and I wish such hospitality would not be punished with
> an unwelcome package
In two days, dmidecode will have passed its 10 day waiting period, and
should be ready to go into testing. As it is frozen (creating an
udeb), I need help from someone to get it into testing. I start this
discussion a bit early, as I expect it to take at least two days to
make a decision. :)
Th
18 matches
Mail list logo
