On Sat, Dec 17, 2011 at 11:37:08AM +, Mark Morgan Lloyd wrote:
I still hope, that the next Debian release on SPARC will be better. I
can't believe, that such a buggy SPARC release as Squeeze was released
as stable.. :(
Bugs only have a chance of getting fixed if they are reported.
On Sat, Dec 17, 2011 at 05:22:23PM +, Jurij Smakov wrote:
I didn't report this bug even though I ran into it. What is a good place to
report them should I find more?
The easiest way is [...]
http://www.google.com/search?q=how+to+report+a+bug+in+debian
The first hit should be
Josip Rodin wrote:
Quite frankly, I gave up trying to work out detailed fixes for
things
Nobody's really expecting people to work out detailed fixes, just to report
bugs to the BTS. Jurij's sentence above was probably unclear - it's certain
that hoping won't make it better, and it's certain
On Tue, Dec 20, 2011 at 02:51:08PM +, Mark Morgan Lloyd wrote:
I'm happy with that, but I'd suggest that it does need the more
experienced user/developers to ride herd on the rest of us, and when
somebody has an issue to say one of:
* That's a known issue which won't be changed for a
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570955 looks like the same
problem, for i386/amd64. Reported Feb 2010.
Experienced Debianers -- is this good strategy: add more info to that
and/or bring it to the forefront?
Patrick
On Tue, Dec 20, 2011 at 9:12 AM, Josip Rodin
Hi,
On ppc64, both packages of gcc-4.7 (4.7-20111217-2) and gcj-4.7
(4.7-20111217-1) were built without any problem.
Matthias Klose wrote:
Please have a look at the gcc-4.7 package in experimental, update patches
(hurd,
kfreebsd, ARM is fixed in svn), and investigate the build failures
Josip Rodin wrote:
On Tue, Dec 20, 2011 at 02:51:08PM +, Mark Morgan Lloyd wrote:
I'm happy with that, but I'd suggest that it does need the more
experienced user/developers to ride herd on the rest of us, and when
somebody has an issue to say one of:
* That's a known issue which won't be
7 matches
Mail list logo
