John Paul Adrian Glaubitz wrote...
> On 09/20/2016 11:16 PM, Niels Thykier wrote:
> >- powerpc: No porter (RM blocker)
>
> I'd be happy to pick up powerpc to keep it for Stretch. I'm already
> maintaining powerpcspe which is very similar to powerpc.
For somewhat personal reasons I'm interest
Mathieu Malaterre wrote...
> Since there has been some fuss about powerpc recently, let's see if I
> can get some help on issue(s) I'd like to fix for Stretch.
Let's see what I can do (and I'm subscribed to debian-powerpc now, so
no need for Cc: in the future :)
> 1. Secret GRUB option in d-i.
>
Hello,
just to make sure I got things right: The 74xx/G4 processors are
to be supported by Debian's powerpc architecture?
Background: On my G4 boxes I encounter SIGILL from several packages,
turns out they were built with compiler options for more recent CPUs,
hence the program abort. The buildds
Rick Thomas wrote...
> Can you give us some more details?
In general I'm somewhat reluctant since first conclusions are usually
wrong and I certainly don't want to create noise at the wrong place.
So I'd rather debug a little longer until I can identify the real
cause, and create a patch to prove
Mathieu Malaterre wrote...
> Don't forget to set the usertags so that we can track those.
#840354 about the syslog-ng issue (which is actually in src:pcre3 as
assumed). I'm not sure if usertags can be set that way, we'll see.
Christoph
signature.asc
Description: Digital signature
Lennart Sorensen wrote...
> On Mon, Oct 31, 2016 at 09:09:56AM -0700, Herminio Hernandez Jr. wrote:
> > Is there even a chance for PowerPC to return as a release architecture for
> > Debian 10 or is that just wishful thinking.
>
> Well as pointed out in the meeting, it does not seem any archit
Herminio Hernandez, Jr. wrote...
> On Mon, Oct 31, 2016 at 4:13 PM, Rick Thomas wrote:
>
> > Will there be an LTS (long-term-support) release for powerpc — best would
> > be one based on Jessie?
>
> No there is no lts for ppc only i386, amd64, and arm
>
> https://wiki.debian.org/LTS/
Perhaps R
Herminio Hernandez Jr. wrote...
> I saw that after I asked the question. It just really stinks.
Keep it down. From an outsider's point of view the decision is more
than understandable. Their interest is only "are there enough people
willing to support powerpc?", and the indications were pretty
luigi burdo wrote...
> Im thinking to start a petition about ... "dont kill debian penguins on
> powerpc"
Don't. The release team folks are not politicians who get convinced by
a lot of noise. Unless I completely misunderstand their position, the
only question that matters is: Can we (as the Deb
Herminio Hernandez Jr. wrote...
> To say that no one stepped forward is not true. Adrian stepped up
> and asked to be the porter for PowerPC.
Digging in the past isn't very helpful, but there one thing I'd like
to understand: Nobody responded to the initial role call in August.
Some folks had do
Aurelien Jarno wrote...
> > FAIL: colors
> >
> >
> > diff: standard output: Broken pipe
> > FAIL colors (exit status: 1)
This is the related code:
| mkfifo fifo
| printf '%*s-a' 100 > a
| printf '%*s-b' 100 > b
| head -c 10 < fifo > /dev/null &
+ diff --color=always ---presu
Santiago Vila wrote...
> Are you sure we need a super-fast computer and not a super-slow one?
There is no lack of super-slow computers so this would have been noticed
earlier ... on the other hand, recent ppc64 boxes can be really, really
fast. Where "fast" has many aspects, and there might be so
ilko Iliev wrote...
> image = /boot/ vmlinux
(...)
> initrd = /boot/ initrd . img
Do these files actually exist? When setting up two installations during
the weekend, they were missing. This ought to be a bug in yaboot but I
didn't get around to debug this.
So either: Remove the "/boot"
Hi there,
while preparing other tests I created two installations on two hosts
with identical hardware (LPARs on IBM POWER):
- powerpc (64 bit kernel, 32 bit userland)
- ppc64 (64 bit kernel, 64 bit userland)
Both are up-to-date sid with systemd held to 232-10 (#852811).
Now the surprise: Using
John Paul Adrian Glaubitz wrote...
> Please test and report back on the individual architecture
> mailing lists
So far, the ride for ppc64 has been *extremely* painful. This is not
necessarly due to your efforts, but it feels a lot like nobody ever has
tried to set up Debian on a G5 using netboot
Frank Scheiner wrote...
> Let's continue this on the corresponding mailing list.
Jupp, that's how it was meant to be.
> >* Any reasonable documentation on this anywhere? No about how to set up
> > DHCP/TFTP server, I've done this many time. But what about which files
> > are needed, and how
Hello,
since a few days ago, I get messages like
| Unpacking libsmartcols1:ppc64 (2.31.1-0.4) over (2.30.2-0.3) ...
| dpkg-deb (subprocess): decompressing archive member: lzma error: compressed
data
| is corrupt
| dpkg-deb: error: subprocess returned error exit status 2
| dpkg: error processin
Christian Göttsche wrote...
> the package logrotate in version 3.14.0-2 fails to build on ppc64el
> due to a test suite failure [1].
That looks familiar. Is the patch
debian/patches/fix-test-pagesize.patch
I created for 3.11.0-0.1 still part of your packaging?
And by the way, thanks for ta
Carsten Jacobi wrote...
> The reason is that in one makefile the compiler options "-mcrypto" and
> "-mvsx" were turned. Hence, there are Power-7 instructions now in
> libfreeblpriv3.so:
Ouch. That could also happen when the build system guesses some possible
additional compile options from the CP
19 matches
Mail list logo
