On 1/22/20 11:25 PM, Witold Baryluk wrote:
> Yes, I did use the previous images and it did work.
> I just wanted to report on the new images with new kernel ;)
The images in the date folders should be considered untested.
There are a couple of things that I need to fix before I can
create reliable
Ok, thanks.
Yes, I did use the previous images and it did work.
I just wanted to report on the new images with new kernel ;)
Cheers,
Witold
On Wed, 22 Jan 2020 at 22:12, John Paul Adrian Glaubitz
wrote:
>
> Hello!
>
> On 1/22/20 11:08 PM, Witold Baryluk wrote:
> > I tried alpha ISO, and it does
Hello!
On 1/22/20 11:08 PM, Witold Baryluk wrote:
> I tried alpha ISO, and it does boot, and I can proceed with most of the
> steps, but debootstrap does fail installing init_1.57_alpha.deb
Just use one of the older images for the time being. Such installation issues
can occur when images were bui
Hi John, and thanks a lot for the new images.
I tried alpha ISO, and it does boot, and I can proceed with most of the
steps, but debootstrap does fail installing init_1.57_alpha.deb
>From logs it reads: init pre-depends on systemd-sysv | sysvinit-core.
But none is installed.
There is also a bunc
Hi!
On 12/1/19 1:07 AM, Bob Tracy wrote:
> All that being said, I'd *definitely* think twice about blindly changing
> the sleep values. Again, you'll never see this issue on the "buildd"
> systems. If I were the package maintainer, I'd reject this patch :-).
>
> (file is in "guile-2.2-2.2.6+1/t
On Sat, Nov 30, 2019 at 05:51:45PM +0100, John Paul Adrian Glaubitz wrote:
> > On Nov 30, 2019, at 4:54 PM, Skye wrote:
> >
> > Bob, that is excellent information. Thank you for sharing!
>
> I suggest turning this into a patch. Fixing guile-2.0 and guile-2.2 on alpha
> is dearly needed, so p
; debian-alpha@lists.debian.org
Subject: Re: Updated installation images for Debian Ports 2019-11-22
Hi!
> On Nov 30, 2019, at 4:54 PM, Skye wrote:
>
> Bob, that is excellent information. Thank you for sharing!
I suggest turning this into a patch. Fixing guile-2.0 and guile-2.2 on
Hi!
> On Nov 30, 2019, at 4:54 PM, Skye wrote:
>
> Bob, that is excellent information. Thank you for sharing!
I suggest turning this into a patch. Fixing guile-2.0 and guile-2.2 on alpha is
dearly needed, so patches are really welcome.
Adrian
Debian Ports 2019-11-22
On Sat, Nov 30, 2019 at 01:59:36PM +1300, Michael Cree wrote:
> (...) It passes more often than not and
> only fails occasionally. I see that there is a patch in the
> debian/patches directory to avoid a race condition in this test.
> But I don't kn
On Sat, Nov 30, 2019 at 01:59:36PM +1300, Michael Cree wrote:
> (...) It passes more often than not and
> only fails occasionally. I see that there is a patch in the
> debian/patches directory to avoid a race condition in this test.
> But I don't know guile so don't understand the code.
There are
On Sat, Nov 30, 2019 at 12:10:28PM +1300, Michael Cree wrote:
> ERROR: 00-repl-server.test: repl-server: HTTP inter-protocol attack -
> arguments: ((system-error "fport_write" "~A" ("Broken pipe") (32)))
>
> Bob: how did you get past this test or did it pass on your build?
It passed on mine. I
On Sat, Nov 30, 2019 at 12:10:28PM +1300, Michael Cree wrote:
> On Wed, Nov 27, 2019 at 02:15:30PM +0100, John Paul Adrian Glaubitz wrote:
> I've done a test on an XP1000 (UP) and it got past the failure seen
> on the buildds but errored out in one of 4 or so tests in the
> test suite.
>
> Rel
On Wed, Nov 27, 2019 at 02:15:30PM +0100, John Paul Adrian Glaubitz wrote:
> On 11/26/19 4:49 AM, Michael Cree wrote:
> > Taking it that you did use up to date toolchain then that is rather
> > interesting that guile-2.0 built for you. I ran a test rebuild a
> > week or two ago and it failed.
> >
Hi,
I wonder if the (untested) simple recipe below would work.
It would confirm that the missing QLOGIC firmware
was indeed the culprit.
I hope it will help !
Regards,
JH Chatenet
# download firmware-qlogic
apt-get download firmware-qlogic
# become root (to preserve rights)
su -
# install gen
On 11/26/19 4:49 AM, Michael Cree wrote:
> Taking it that you did use up to date toolchain then that is rather
> interesting that guile-2.0 built for you. I ran a test rebuild a
> week or two ago and it failed.
>
> Maybe I should try again, but if it fails for me again that would
> raise issues o
On 11/27/19 8:13 AM, Darren Goossens wrote:
> I am thinking I am going to have to make my own installer, since
> apparently the DFSG prevent the requisite firmware going on the disk.
No, it's not the DFSG. It's my lack of time to patch the debian-cd package
to support building firmware images for
Just recording this simpleton's experience.
I booted the 22 Nov image. AlphaServer1200
It boots fine, but asks for qlogic 1040.bin firmware on removable media.
The system has a PCI card that controls an IDE HDD and an IDE CDRW,
plus a SCSI CDROM (that I boot off) plus a floppy drive plus a PCI U
(This is a separate copy to the list, just to keep everyone informed.
No attachment included.)
On Tue, Nov 26, 2019 at 04:49:15PM +1300, Michael Cree wrote:
> I don't seem to have received that message.
I'll try sending again just to you... The attached "packages" file was
on the order of 500k,
On Mon, Nov 25, 2019 at 07:02:15PM -0600, Bob Tracy wrote:
> On Tue, Nov 26, 2019 at 12:00:59PM +1300, Michael Cree wrote:
> > Did you build with latest toolchain? I suspect the issue has
> > appeared with toolchain changes (hard to pin down when because there
> > was quite a period in which a new
On Tue, Nov 26, 2019 at 12:00:59PM +1300, Michael Cree wrote:
> Did you build with latest toolchain? I suspect the issue has
> appeared with toolchain changes (hard to pin down when because there
> was quite a period in which a new version of guile-2.0 was not
> uploaded).
>
> And the bug (a segf
On Mon, Nov 25, 2019 at 06:40:04AM -0600, Bob Tracy wrote:
> On Sat, Nov 23, 2019 at 07:36:11AM +1300, Michael Cree wrote:
> > That's not going to help at the moment because vim is bd-uninstallable.
> >
> > The real problem is guile-2.0 and guile-2.2, both of which FTBFS, and
> > are blocking the
[mailto:glaub...@physik.fu-berlin.de]
Sent: Monday, November 25, 2019 8:44 AM
To: Skye; 'Bob Tracy'; 'Michael Cree'; debian-alpha@lists.debian.org
Subject: Re: Updated installation images for Debian Ports 2019-11-22
On 11/25/19 4:41 PM, Skye wrote:
> Are the build servers
Hi Bob!
On 11/25/19 1:40 PM, Bob Tracy wrote:
> I downloaded the Debian source for "guile-2.0_2.0.13+1-5.3" and successfully
> built the binary packages on my PWS-433au without having to modify anything.
> My guess is some kind of toolchain or other build environment issue on
> the "buildd" server
Paul Adrian Glaubitz; debian-alpha@lists.debian.org
Subject: Re: Updated installation images for Debian Ports 2019-11-22
On Sat, Nov 23, 2019 at 07:36:11AM +1300, Michael Cree wrote:
> That's not going to help at the moment because vim is bd-uninstallable.
>
> The real problem is
On 11/25/19 4:41 PM, Skye wrote:
> Are the build servers for Alpha public facing? I plan to test install on
> Alpha in a few day and having access to the code and environment could prove
> useful.
What do you mean with "public facing"? They are on the internet, of course,
but they are not publicl
On Sat, Nov 23, 2019 at 07:36:11AM +1300, Michael Cree wrote:
> That's not going to help at the moment because vim is bd-uninstallable.
>
> The real problem is guile-2.0 and guile-2.2, both of which FTBFS, and
> are blocking the building of many other packages.
I downloaded the Debian source for
On 11/24/19 9:53 PM, rkn wrote:
> Unfortunately, it now fails during the base system install, there seems to be
> something
> wrong with the whiptail package. It doesn't give a specific error.
Yes, it's the broken vim package that needs to be fixed as I mentioned in my
initial mail.
vim is con
Thank you for the help, I've re-downloaded and re-burned the image, I
must have been using an older version because it does now sense the
hardware.
Unfortunately, it now fails during the base system install, there seems
to be something wrong with the whiptail package. It doesn't give a
speci
On 11/23/19 1:04 AM, rkn wrote:
> I'm reporting the exact readout that the system gives me when I run uname -a,
> I don't know anything more than that and I've done nothing to the image but
> burn it. The error states that it is probably due to a mismatch between the
> kernel the installer uses an
On 11/23/2019 8:41 AM, John Paul Adrian Glaubitz wrote:
On 11/23/19 12:24 AM, rkn wrote:
uname -a gives: 5.3.0-2-alpha-generic and Debian 5.3.9-2 (2019-11-12). Exact
error message is that no kernel modules can be found.
But the ISO image contains the correct module packages. I just verified
On 11/23/19 12:24 AM, rkn wrote:
> uname -a gives: 5.3.0-2-alpha-generic and Debian 5.3.9-2 (2019-11-12). Exact
> error message is that no kernel modules can be found.
But the ISO image contains the correct module packages. I just verified that
again.
> I'm using the ISO image from the pool, I
uname -a gives: 5.3.0-2-alpha-generic and Debian 5.3.9-2 (2019-11-12).
Exact error message is that no kernel modules can be found.
I'm using the ISO image from the pool, I'm installing from a CD to a raw
disk on a system that does not have Linux on it.
On 11/23/2019 7:47 AM, John Paul Adria
On 11/22/19 11:41 PM, rkn wrote:
> Alpha installer errors with a mismatch between installer kernel version and
> archive kernel version.
Are you sure about that? I just checked the CD image contents in pool-alpha/
main/l/linux/ and the udebs have the correct version number which is 5.3.9-3.
What
Alpha installer errors with a mismatch between installer kernel version
and archive kernel version.
On 11/22/2019 7:23 PM, John Paul Adrian Glaubitz wrote:
Hi!
I just uploaded updated installation images 2019-07-22 for the
following Debian Ports architectures [1]:
* alpha
* hppa
* ia64
On Fri, Nov 22, 2019 at 03:09:09PM +0100, John Paul Adrian Glaubitz wrote:
> On 11/22/19 2:40 PM, Bob Tracy wrote:
> > I've noticed I haven't been able to update the "vim" packages for a long
> > time. Michael Cree -- if you see this, I think you explained the
> > problem to me many moons ago. In
Hi!
On 11/22/19 2:40 PM, Bob Tracy wrote:
> I've noticed I haven't been able to update the "vim" packages for a long
> time. Michael Cree -- if you see this, I think you explained the
> problem to me many moons ago. In any event, there has been a held
> update to "vim-common" on alpha for at *le
On Fri, Nov 22, 2019 at 11:23:10AM +0100, John Paul Adrian Glaubitz wrote:
> (...)
> The images for alpha and ia64 could have issues because of the missing
> vim package [3]. Someone needs to have a look at vim on these two
> architectures.
>
> (...)
> > [3] https://buildd.debian.org/status/packag
Hi!
I just uploaded updated installation images 2019-07-22 for the
following Debian Ports architectures [1]:
* alpha
* hppa
* ia64
* m68k
* powerpc
* ppc64
* sparc64
debian-installer images for netboot and sh4 can be found in [2].
I have successfully tested the sparc64 image, but not the
38 matches
Mail list logo
