Hi,
I finally got time to perform those archive rebuilds.
Results are available at http://qa-logs.debian.net/2024/01/11/
I did a first archive rebuild (all packages on arm64, armhf, armel), and
then did a second one, restricted to packages that failed at on at least
one architecture.
Results in
On 14/08/23 at 14:53 +0200, Emanuele Rocca wrote:
> Hi Lucas,
>
> On 2023-08-12 08:18, Lucas Nussbaum wrote:
> > Results:
> > http://qa-logs.debian.net/2023/08/11.stackclash-arm/
> >
> > I only included logs for builds that succeeded in a vanilla build,
>
Hi Emanuele,
On 10/08/23 at 16:57 +0200, Emanuele Rocca wrote:
> Hi,
>
> On 2023-08-10 02:43, Lucas Nussbaum wrote:
> > What I would need is a script that customizes a chroot.
>
> This is what I'm passing to sbuild --chroot-setup-commands for my
> builds:
>
On 10/08/23 at 10:49 +0200, Emanuele Rocca wrote:
> Hi,
>
> On 2023-08-06 11:25, Moritz Mühlenhoff wrote:
> > I worked with Lucas a while back and he made an archive rebuild on amd64,
> > only a minimal list of packages will need to be adapted:
> > http://qa-logs.debian.net/2023/05/24/
>
> Can we
On 22/01/23 at 20:23 +0100, Arne Ploese wrote:
> Am Sonntag, dem 22.01.2023 um 18:13 +0100 schrieb Lucas Nussbaum:
> > On 22/01/23 at 17:56 +0100, Arne Ploese wrote:
> > > Hi,
> > >
> > > Im testing (just for fun) an Olimex OLuxino A20-Lime2.
> > > Th
On 22/01/23 at 17:56 +0100, Arne Ploese wrote:
> Hi,
>
> Im testing (just for fun) an Olimex OLuxino A20-Lime2.
> The system can't bring up the interface end0 on rebooting (only reboot
> - and not poweroff and then restart by power-button).
>
> "ip a" tells me that end0 is unconfigured.
> "ifup
Hi,
On 17/12/20 at 09:24 +0900, Ryutaroh Matsumoto wrote:
> (1) CONFIG_DRM_V3D has no effect, as
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977441#18
>
> (3) /dev/dri/render* does not appear unlike
>
> https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880125/comments/14
> http
On 05/12/20 at 17:19 +, peter green wrote:
> severity 976572 normal
> thanks
>
> > During a rebuild of all packages in sid, your package failed to build
> > on arm64 (I don't know if it also fails on amd64).
>
> It's cool that you have expanded your rebuild tests to include arm64, but it
> s
Hi,
Can you confirm that it's not
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964915
?
Thanks
Lucas
On 30/07/20 at 21:28 +0200, basti wrote:
> Hello I have done some more tests.
> What I see. The Initram has different size. I think it sould be the same
> size, if no module are added or
Hi,
On 30/06/20 at 23:27 -0500, Gunnar Wolf wrote:
> - However... There is a _very_ odd problem we will have to look into:
> The image works fine in the 4GB version of the Rpi4. The 8GB version
> does bring up wireless networking, but still does not manage to
> enable USB :-( (we haven't yet
/brcmfmac43455-sdio.bin
https://github.com/RPi-Distro/firmware-nonfree/raw/master/brcm/brcmfmac43455-sdio.txt
https://github.com/RPi-Distro/firmware-nonfree/raw/master/brcm/brcmfmac43455-sdio.clm_blob
to /lib/firmware/brcm/
Lucas
On 26/04/20 at 21:58 +0200, Lucas Nussbaum wrote:
> ( Ccing debian-arm for i
Hi Gunnar,
I tried booting the RPI2 image from
https://raspi.debian.net/daily/raspi_2.img.xz
Boot fails. It never leaves the colorful screen on HDMI.
Rebuilding the image myself worked. But even then, the serial console
does not work (only HDMI worked). The image uses console=ttyS1 in
cmdline.tx
On 27/04/20 at 20:46 +0200, basti wrote:
> Am 27.04.20 um 18:28 schrieb Lucas Nussbaum:
> > On 27/04/20 at 15:30 +0200, basti wrote:
> > > Hello lucas,
> > >
> > > thanks for the tip you provide there
> > > (https://github.com/lategoodbye/rpi-zero/issu
On 27/04/20 at 15:30 +0200, basti wrote:
> Hello lucas,
>
> thanks for the tip you provide there
> (https://github.com/lategoodbye/rpi-zero/issues/43#issuecomment-619974846)
>
> As I can see in this Post here you have a working Image with Kernel 5.5
> without USB Support. I need the USB Support.
( Ccing debian-arm for info )
Hi Gunnar,
I (finally) wrapped up my work on building an RPI4 image. You will find
a suitable raspi_4.yaml file in
https://salsa.debian.org/raspi-team/image-specs/-/blob/rpi4/raspi_4.yaml
I did not try merging it into the raspi_*.yaml generation script yet. I
don't
ith Kernel 5.6 does nothing. No monitor output, no output
> on serial.
>
> When I try to upgrade the image with kernel 5.5 to 5.6 and reboot there
> is the same described above. (Kernel 5.6. is upgraded from your repo.)
>
>
> On 15.04.20 20:40, Lucas Nussbaum wrote:
> > O
On 15/04/20 at 12:13 +0200, basti wrote:
> Hello,
> i have try to boot rpi4 with real debian kernel.
>
> I have try:
> - build kernel from source -> boot with dtb from ubuntu, but do not find
> an sdcard
> - use uefi -> install via debian installer, does not boot after install
> is finished, can't
On 31/03/20 at 16:24 +0200, Ralph Aichinger wrote:
> Hello!
>
> With a little bit of envy I discovered that Ubuntu not only runs
> in a vanilla flavour on the Raspberry Pi, but that there is
> a very straightforward download page and stuff seems reasonably
> documented. In both 32 and 64 bit.
>
>
On 03/01/12 at 22:54 +, Adam D. Barratt wrote:
> (fwiw, the not-yet-built list includes webkit and ruby1.9.1, each of
> which have a number of other packages directly or indirectly stuck
> behind them).
Hi,
FYI, we are considering making 1.9.X the default version of Ruby in
wheezy. It scares
On 03/11/11 at 21:27 +0100, Julien Cristau wrote:
> On Sun, Oct 23, 2011 at 14:11:26 +0200, Lucas Nussbaum wrote:
>
> > At this point, I'm confident that we can reach a (at least partially)
> > working Ruby on kfreebsd, sparc and armel at some point. I'm l
08/11 at 23:48 +0200, Lucas Nussbaum wrote:
> Ruby 1.9.3 is going to be released in september, and is a candidate for
> the default ruby version in wheezy. A snapshot is available in
> experimental. Now is an ideal time to work on porting issues and get the
> fixes integrated upstream.
Hi,
Ruby 1.9.3 is going to be released in september, and is a candidate for
the default ruby version in wheezy. A snapshot is available in
experimental. Now is an ideal time to work on porting issues and get the
fixes integrated upstream. Ruby has a fairly large test suite, which
makes finding pro
On 14/06/11 at 17:10 +0200, Lucas Nussbaum wrote:
> Hi,
>
> ruby1.8 and ruby1.9.1 both FTBFS on armel on sid, due to a test failure.
>
> I did some tests on abel.debian.org on 2011-06-10, and the same packages
> are building fine on squeeze and wheezy.
>
> The same packa
Hi,
ruby1.8 and ruby1.9.1 both FTBFS on armel on sid, due to a test failure.
I did some tests on abel.debian.org on 2011-06-10, and the same packages
are building fine on squeeze and wheezy.
The same packages don't fail on sid on other architectures.
could someone take a look?
Thanks,
- Lucas
24 matches
Mail list logo
