Bug#799939:

200 @@ -0,0 +1,308 @@ +From 4636f5bb744c0828ac853e1a513e375886fcd424 Mon Sep 17 00:00:00 2001 +From: Riku Voipio <riku.voi...@linaro.org> +Date: Thu, 5 Nov 2015 15:34:36 -0800 +Subject: [PATCH] arm64: clang assembler compatability + +Fixes to compile with clang (3.7) + +- Fix fmul syntax: + fmu

Bug#805796: www.debian.org: please mention httpredir.d.o on mirror page(s)

Hi, While at it: https://packages.debian.org/sid/arm64/bash/download Doesn't mention httpredir either. Riku

Bug#799939: chromium not available for armhf/arm64

+ + -- Riku Voipio <riku.voi...@linaro.org> Thu, 02 Jun 2016 21:20:42 +0300 + chromium-browser (51.0.2704.63-2) unstable; urgency=medium * Fix libspeechd build error. diff -Nru chromium-browser-51.0.2704.63/debian/control chromium-browser-51.0.2704.63/debian/control --- chromium-browser-51.0.2

Bug#827525: kvmtool: FTBFS on mips64el: guest/guest_init.o: linking 32-bit code with 64-bit code

On 17 June 2016 at 15:04, Dejan Latinovic wrote: > Package kvmtool FTBFS for mips64el with the following error: > >> LINK lkvm >> /usr/bin/ld: guest/guest_init.o: warning: linking abicalls files with >> non-abicalls files >> /usr/bin/ld: guest/guest_init.o:

Bug#813141: chroot upgrade from jessie to stretch disables predictable network interface names

reassign 813141 udev thanks # we enabled net.ifnames in 220-7 by default; don't change iface names in # virtualized envs (where 75-persistent-net-generator.rules didn't work) I think we need a more precise check for affected systems rather than the lack of existance of

Bug#817962: kvmtool: does not work with Debian kernels

severity 817962 normal thanks > I don't think we should ship kvmtool in stretch without a Linux kernel > flavour for it. If you agree, please upgrade this bug to serious. Right > now the Debian Linux kernel packages don't have CONFIG_NET_9P_VIRTIO > and CONFIG_VIRTIO_NET enabled. For kvmtool we

Bug#817965: kvmtool: dumps core when Linux reboots: in gdb: Program received signal SIG34, Real-time event 34.

Hi, On 12 March 2016 at 07:27, Paul Wise wrote: > Due to #817962, Linux reboots after not finding the filesystem and then > lkvm crashes due to not handling the reboot properly. gdb gives this: > Program received signal SIG34, Real-time event 34. I couldn't reproduce with. lkm

Bug#820220: [Pkg-julia-devel] Bug#820220: Bug#820220: Bug#820220: Bug#820220: julia: FTBFS on armel/armhf

On Sat, Apr 09, 2016 at 12:02:44PM +0200, Graham Inggs wrote: > On 9 April 2016 at 00:53, peter green wrote: > > It would be useful if someone can reproduce the issue and get a dissasembly > > of the failure location. > > I hope this is useful. I'll leave my screen session

Bug#794326: enable arm64 assember routines

tags 794326 +patch thanks The attached patch gives 2x-10x improvements on aes-128-ctr and sha256 tests with openssl speed (tested on cortex-a53 and cortex-57) diff -Nru openssl-1.0.2g/debian/patches/debian-targets.patch openssl-1.0.2g/debian/patches/debian-targets.patch ---

Bug#769364: arm64: Error in `Xtightvnc': free(): invalid next size (fast)

/debian/changelog 2016-01-24 21:23:35.0 +0200 +++ tightvnc-1.3.9/debian/changelog 2016-03-23 15:24:23.0 +0200 @@ -1,3 +1,10 @@ +tightvnc (1.3.9-7.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Add patch to complete arm64 port, Closes: #769364 + + -- Riku Voipio <riku.

Bug#769364: arm64: Error in `Xtightvnc': free(): invalid next size (fast)

+1,10 @@ +tightvnc (1.3.9-7.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Add patch to complete arm64 port, Closes: #769364 + + -- Riku Voipio <riku.voi...@linaro.org> Wed, 23 Mar 2016 15:23:49 +0200 + tightvnc (1.3.9-7) unstable; urgency=medium * Applied a patch from up

Bug#799939:

On 9 March 2016 at 11:00, Raphael Hertzog wrote: > what's the status of this bug? I would love to see chromium on armhf and > arm64. I've have armhf/arm64 builds of chromium for jessie at: http://repo.linaro.org/ubuntu/linaro-overlay/pool/main/c/chromium-browser/ > Michael,

Bug#819890: haskell-http2: FTBFS on armel buildds (was: Re: Please give back haskell-http2 on armel)

On Sun, Apr 03, 2016 at 03:11:39PM +0100, Steven Chamberlain wrote: > Wookey wrote: > > +++ Steven Chamberlain [2016-04-01 10:31 +0100]: > > > Currently haskell-http2 FTBFS on only armel: > > > https://buildd.debian.org/status/package.php?p=haskell-http2=unstable > > > delaying the package's

Bug#730903: mutrace: FTBFS: b-d on libiberty-dev instead of binutils-dev No such file or directory

On 12 May 2016 at 19:47, Fernando Seiti Furusato wrote: > Actually, this works, not replacing build-deps, but adding > libiberty-dev in addition to binutils-dev. Thanks, uploading fixed version. > With that and adding -I/usr/include/libiberty as suggested by > YunQiang Su,

Bug#737030: libgcrypt uses processor features not allowed for armhf (and i386?)

> hmm, looking further into the code, it looks like libgcrypt implements > it's own way to detect hw features. But maybe somebody could confirm this Correct. Debian armhf/armel buildd's don't have NEON unit yet testsuite passes fine, so we even know the hw feature detection works fine. This bug

Bug#803031: patch: support serial serial dev/serial/by-path names

On 27 June 2016 at 21:56, Marc Haber <mh+debian-packa...@zugschlus.de> wrote: > On Sun, Jun 26, 2016 at 10:39:04PM +0200, Marc Haber wrote: >> On Mon, Oct 26, 2015 at 10:10:35AM +0200, Riku Voipio wrote: >> > ser2net uses : as field separator in ser2net.conf. Udev create

Bug#853170: fails to boot on debian's MP30-AR1 systems [regression]

Quick test with 4.9.2-2 with new arm64 kernel config: boots 4.9.6-3 work old arm64 kernel config: booms This hints that numerous kernel config changes we did are probably not the reason, but some of the kernel changes between 4.9.2 and 4.9.6. Especially between 4.9.5 and 4.9.6 a bulk of arm64

Bug#853170: fails to boot on debian's MP30-AR1 systems [regression]

On Tue, Jan 31, 2017 at 02:30:10PM +, Riku Voipio wrote: > This hints that numerous kernel config changes we did are probably > not the reason, but some of the kernel changes between 4.9.2 and 4.9.6. The offending commit is: http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stab

Bug#854079: firefox-esr: firefox dies immediately on arm64

Mike Hommey wrote: > That's fixed in 47.5.0esr-3. Can you check if you still get crashes with > that version? Thanks Mike for looking into this. Indeed firefox-esr doesn't segfault in jemalloc anymore. However, I get a new crash - I assume Aaro will get the same. Looking at

Bug#854079: firefox-esr: firefox dies immediately on arm64

On Tue, Feb 07, 2017 at 02:12:00PM +0900, Mike Hommey wrote: > Okay, that one was fixed upstream in > https://bugzilla.mozilla.org/show_bug.cgi?id=1257055 > Can you try applying the patch there and see how things go from there? > (I'd rather avoid doing multiple uploads if it turns out not to be

Bug#853888: bpfcc not building on ppc64el and aarch64

Hi, If you submit a build to experimental, I'd be happy to test it on aarch64 and armhf. Riku

Bug#853108: [Pkg-chromium-maint] Bug#853108: chromium: fails to build on armhf

On Sun, Jan 29, 2017 at 02:59:40PM -0500, Michael Gilbert wrote: > package: src:chromium-browser > severity: grave > version: 56.0.2924.76-1 > The upload to experimental fails to build on armhf due to new NEON code. I have a fix for this (backport patch from upstream - NEON buildd is still

Bug#852493: Please enable Thunder NIC virtual function driver

On Wed, Jan 25, 2017 at 02:05:06AM +, Ben Hutchings wrote: > Control: tag -1 moreinfo > > On Tue, 2017-01-24 at 22:13 +, Punit Agrawal wrote: > > Source: linux > > Severity: wishlist > > Tags: patch > > > > While testing device passthrough with a debian guest on a Cavium > > Thunder, I

Bug#854582: chromium extensions no longer enabled bu default

package: chromium forcemerge 852398 854582 thanks See the original issue at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786909 https://news.ycombinator.com/item?id=9724409 to re-enable the setting use: export CHROMIUM_FLAGS='--enable-remote-extensions' See also

Bug#855372: vagrant: please add recommends on vagrant-libvirt

Package: vagrant Version: 1.9.1+dfsg-1 Severity: wishlist Dear Maintainer, Considering that virtualbox wont be part of stretch (#794466), please add recommends for vagrant-libvirt - which appears to be the only vagrant provider available easily. Riku -- System Information: Debian Release: 9.0

Bug#851832: qtermwidget: missing qtf8proc support

Source: qtermwidget Version: 0.7.1-1 Severity: normal Tags: patch The build log states: -- Could NOT find UTF8PROC (missing: UTF8PROC_LIBRARY UTF8PROC_INCLUDE_DIR) https://buildd.debian.org/status/fetch.php?pkg=qtermwidget=amd64=0.7.1-1=1482363037=0 adding Build-dep helps: ---

Bug#851761: obs-worker: fails to start, missing user: obsrun

Package: obs-worker Version: 2.7.1-9 Severity: normal Dear Maintainer, After enabling in defaults, Starting obswork fails: root@obs-worker:~# systemctl start obsworker Job for obsworker.service failed because the control process exited with error code. See "systemctl status obsworker.service"

Bug#835099: ITP: skales -- Boot image creation tools for qualcomm boards

Package: wnpp Severity: wishlist Owner: Riku Voipio <riku.voi...@linaro.org> * Package name: skales Version : 0.20160202 Upstream Author : Stephen Boyd * URL : git://codeaurora.org/quic/kernel/skales * License : BSD (3 clause) Programming Lang:

Bug#856183: [Pkg-chromium-maint] Bug#856183: Acknowledgement (chromium: safe or unsafe defaults)

On Sun, Feb 26, 2017 at 02:49:25AM -0500, Michael Gilbert wrote: > Let me clarify. I am not going to make a decision about this, you are. > Form a consensus (all involved must agree), and I will accept an > implementation of what ever that turns out to be, but I reserve the > right to exclude

Bug#842140: ITP: obs-signd -- open build service signer client and daemon

Hi, What's the status with this? Is there some preliminary packaging already? Riku

Bug#837068: ITP: glshim -- Shim that translates OpenGL 1.x into OpenGL ES.

Package: wnpp Severity: wishlist Owner: Riku Voipio <riku.voi...@linaro.org> * Package name: glshim Version : 0.0.20160225 Upstream Author : Ryan Hileman <lunixbo...@gmail.com> * URL : https://github.com/lunixbochs/glshim * License : Expat Program

Bug#837995: libvirt: please run tests on arm architectures

Source: libvirt Version: 2.2.0-1 Severity: wishlist Tags: patch In my tests, libvirt tests pass fine on armhf/arm64. I take we have newer kernel than debian builders, so it could fail in Debian. To play safe, I suggest running tests but not failing them on arm/arm64. This what the patch below

Bug#799939: chromium not available for armhf/arm64

On Wed, Oct 05, 2016 at 09:59:00PM -0400, Michael Gilbert wrote: > On Wed, Oct 5, 2016 at 2:56 PM, Riku Voipio wrote: > > I understand if you feel the arm builds are a burden of extra work for > > you. The churn of code in chromium and the rapidly rolling security > > u

Bug#791963: Please support ARM64

retitle 791963 Please support ARM64 tags 791963 + patch thanks Upstream support exists in kernel and compiling makedumpfile is just oneline change in debian/control now. Riku diff --git a/debian/control b/debian/control index e4174f2..c0396eb 100644 --- a/debian/control +++ b/debian/control @@

Bug#799939: chromium not available for armhf/arm64

Hi Michael, All patches to support Chrome on arm64 and armhf have been upstreamed. The attached patch against debian packages build and runs chromium on my test machines (samsung chromebook for armhf and Dragonboard 410c). I understand if you feel the arm builds are a burden of extra work for

Bug#843624: [Pkg-chromium-maint] Bug#843624: chromium: since upgrade to latest libnss3-1d chromium shows only "Aw, Snap!"

severity 843624 normal tags 843624 +wheezy thanks On Tue, Nov 08, 2016 at 01:32:25PM +0100, J.Coltrane wrote: > I'm running some full up to date installations of Wheezy, x86 and amd64. Since > an update of some nameservice switch related libraries (libnspr4-0d, > libnss3-1d > and libnss3)

Bug#843032: qemu-user-static: Upgrade fails: unable to close /proc/sys/fs/binfmt_misc/register

t; change doesn't actually make the script a bash script. But before I invest more time into this I'd like to know if others agree this change is the right way. The other option is to revert the change from #829243 until a better way to handle the change is done. Riku >From 919a7df74f4191092b9

Bug#839549: aisleriot: Takes an eternity to build, possibly related to network access

severity 839549 important thanks I can confirm this, the latest build took 4h on armhf buildd, yet the buildd's cpu usage was 0% during this time. https://buildd.debian.org/status/fetch.php?pkg=aisleriot=armhf=1%3A3.22.1-1=1478592921 On amd64 build clearly see network access: /usr/bin/xmllint

Bug#799939: chromium not available for armhf/arm64

On Sun, Nov 06, 2016 at 08:51:45PM -0500, Michael Gilbert wrote: > On Thu, Oct 6, 2016 at 1:43 AM, Riku Voipio wrote: > > Just requested on the alioth project and subscribed to the list. > It took some time to get a response from alioth admins. I've accepted > your request now.

Bug#843868: ocamlbuild: invalid build-dependency: ocaml-best-compilers

Package: ocamlbuild Version: 0.9.3-3 Severity: grave Tags: experimental ocamlbuild is failing to build since ocaml-best-compilers is a virtual package: https://buildd.debian.org/status/package.php?p=ocamlbuild=experimental

Bug#845621: guestfs: please change build-deps for backport/arm64

Package: libguestfs Version: 1:1.32.7-1~bpo8+1 Severity: wishlist Tags: patch libguestfs backport isn't building for arm64, because lzop is missing in jessie/arm64: https://buildd.debian.org/status/package.php?p=libguestfs=jessie-backports The attached patch appears to work, with I guess

Bug#842911: please reconsider dropping libvirt-bin

Package: libvirt Version: 2.3.0-3 Severity: wishlist Hi, libvirt-bin is still referred to in many places, for example in openstack devstack. The replacement -clients and -daemon-system packages are not yet available in the latest ubuntu LTS. This leads to some inconvinient "if ubuntu then else

Bug#842911: [Pkg-libvirt-maintainers] Bug#842911: please reconsider dropping libvirt-bin

On Wed, Nov 02, 2016 at 09:23:53PM +0100, Guido Günther wrote: > On Wed, Nov 02, 2016 at 09:36:21AM +0000, Riku Voipio wrote: > > libvirt-bin is still referred to in many places, for example in openstack > > devstack. The replacement -clients and -daemon-system packages are not ye

Bug#837574: Patch for the qemu PIE FTBFS

On Wed, Oct 26, 2016 at 06:29:49PM +0300, Michael Tokarev wrote: > 25.10.2016 11:31, Adrian Bunk wrote: > > -LD_REL := $(CC) -nostdlib -Wl,-r $(LD_REL_FLAGS) > > +LD_REL := $(CC) -nostdlib -r $(LD_REL_FLAGS) > Adrian, can you elaborate on this a bit please? I really wish gcc manpage explained

Bug#734218: spice: Please support powerpcspe (and maybe other architectures)

severity 734218 important user debian-...@lists.debian.org usertags 734218 arm64 thanks Wookeys patch looks good to me. Liang, Michael, can you upload or are you ok with an NMU? Riku

Bug#846648: [Pkg-chromium-maint] Bug#846648: another data point

On Tue, Dec 06, 2016 at 04:02:00PM -0500, Robert Lange wrote: > Debian stretch with chromium 55.0.2883.75-1 (and only chromium) pulled > in from unstable. With a brand new profile (i.e., by deleting > .cache/chromium and .config/chromium and starting Chromium) Chromium > aw-snaps on gfycat.com

Bug#851494: please upload new upstream version: 0.7.3

Package: dstat Severity: wishlist The homepage of dstat links to https://github.com/dagwieers/dstat/archive/0.7.3.tar.gz While the watch file errors out, so I guess that needs updating too.

Bug#827525: kvmtool: FTBFS on mips64el: guest/guest_init.o: linking 32-bit code with 64-bit code

dre.przyw...@arm.com] > Sent: Monday, June 20, 2016 11:13 AM > To: Riku Voipio; Dejan Latinovic; 827...@bugs.debian.org; k...@vger.kernel.org > Subject: Re: Bug#827525: kvmtool: FTBFS on mips64el: guest/guest_init.o: > linking 32-bit code with 64-bit code > > Hi, > > (thank

Bug#849569: spice: Please package 0.13 branch to experimental

Hi Marc-André, Do you think virgl code in spice-server 0.13 is solid enough to be included in Debian stretch release? Michael wrote: > So, maybe we really should let 0.13 to stretch, together with gl? Full background at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849569 Riku

Bug#853161: #853161: All workers run as one systemd unit

Hi, > obs-worker is a, well, not very nice init script which runs all the > worker instances (under screen of all things). Digging under the hood, adapting this initscript to the brave new world doesn't perhaps make much sense. The initscript downloads bs_worker from obs server and starts it

Bug#859711: bs_dodop needs gpg2

Package: obs-server Version: 2.7.1-10 Severity: normal bs_dodop calls gpg2, so a recommends: on gnupg2 would good. Apr 06 09:12:13 obs bs_dodup[97]: 2017-04-06 09:12:13: checking CentOS:CentOS-7/standard/x86_64... Apr 06 09:12:13 obs bs_dodup[97]: updating metadata for rpmmd repo at

Bug#868454: u-boot-menu: wrong path for fdtdir in extlinux.conf

severity 868454 minor thanks Thanks for trying out u/boot menu. On 15 July 2017 at 17:38, Diego Roversi wrote: > Package: u-boot-menu > Version: 2 > Severity: important > > Entries in extlinux.conf contain this line: > > fdtdir /usr/lib/linux-image-4.9.0-3-armmp-lpae This is

Bug#868802: installation-reports: Successful install on X370-PRO on NVME storage

Package: installation-reports Severity: wishlist Dear Maintainer, -- Package-specific info: Boot method: usb Image version: netinst Date: July 5th 2017 Machine: X370-PRO Partitions: Filesystem Type 1K-blocks Used Available Use% Mounted on udev devtmpfs8171700

Bug#864847: CP15 Barrier emulation performance?

On Tue, Jul 11, 2017 at 09:45:49AM +0100, Ian Campbell wrote: > On Tue, 2017-07-11 at 08:56 +0100, Edmund Grimley Evans wrote: > > > Does this emulation take a considerable performance hit, as opposed > > > to > > > running on armhf hardware/kernel, where the instruction doesn't > > > appear > > >

Bug#869808: kdump-tools builds incorrectly on some archs

Package: kdump-tools Version: 1:1.6.1-1 Severity: important Tags: patch Dear Maintainer, When building makedumpfile on arm64 host, kdump-tools becomes uninstallable (etc/default/grub.d/ becomes missing). I recommend dropping the arch-specific logic from debian/rules, since the generated package

Bug#866580: obs-build: Please add depends to sudo, libarchive-tools

Package: obs-build Version: 20170201-2 Severity: normal Tags: patch Dear Maintainer, If sudo is not installed, osc build will fail with: Running build sudo: No such file or directory If bsdtar is not installed, rpm based distro installs will fail: [4s] [38/49] preinstalling sed... [

Bug#861384: arm64: emulate deprecated instructions

Package: linux Version: 4.10.7-1~exp1 Severity: wishlist Tags: patch User: debian-...@lists.debian.org Usertag: arm64 After some consideration, I think indeed this kernel option needs to be enabled. 1) Rasperry pi binaries While using rasperry-pi targetted Docker images is terrible for

Bug#857986: npm: This pakcage is 3 years old? (consider removal)

Jérémy Lal: > To others, preoccupied that npm won't be available in debian: > - please help with npm maintenance > - hopefully we'll make an updated version installable through debian backports Are there any complications to building npm as part of nodejs package? Riku

Bug#857986: npm: This pakcage is 3 years old? (consider removal)

On Fri, May 19, 2017 at 12:15:32PM +0200, Jérémy Lal wrote: > 2017-05-19 12:07 GMT+02:00 Riku Voipio <riku.voi...@iki.fi>: > > > Jérémy Lal: > > > To others, preoccupied that npm won't be available in debian: > > > - please help with npm maintenance > > &

Bug#874188: fai-client: Integrate some form of file templating system

Hi, I've used envsubst[1] in my fai setup. envsubst comes from gettext-base so most people have installed and it's very easy to use. jinja2 is more powerful (can do loops etc), so there are some cases where it is more useful. Riku [1] http://manpages.debian.net/envsubst

Bug#872782: lava-tool: missing debpendency: python-simplejson

Package: lava-tool Version: 0.21-1 Severity: important Dear Maintainer, Looks like a dependency on python-simplejson is needed: $ sudo apt install lava-tool Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically

Bug#880584: [PATCH] auto_add_modules: add mfd in MODULES==most

=most, update-initramfs doesn't pick mfd modules. Since mfd is quite small (284K on arm64), just add them all to most. This may also open the road to make some currently built-in CONFIG_MFD drivers modules. Signed-off-by: Riku Voipio <riku.voi...@linaro.org> --- hook-functions | 1 + 1 file c

Bug#880584: [PATCH] auto_add_modules: add mfd in MODULES==most

Hi Ben, On Thu, Nov 02, 2017 at 02:46:47PM +, Riku Voipio wrote: > Package: initramfs-tools > Version: 0.130 > Severity: normal > Tags: patch > > Multi Function Devices may carry essential functions on arm/arm64 > platforms. For example in 96boards HiKey mfd/hi655

Bug#901290: version 68 arm build causes internal compiler error

Verified this affects gcc6, gcc7 and gcc8. I'll file a bug against GCC once I get a reduced testcase. Compile with clang6 works. Riku

Bug#901290: Gcc ICE on compiling chromium 68 [arm64 armhf]

reassign 901290 gcc-6 notfound 901290 68.0.3440.7-1 found 6.4.0-17 thanks Compiling chrome 68 with results an gcc ICE. This affects both arm64[1] and armhf[2]. Filing against gcc-6 as this what buildd used, but this affects other versions too: +---+---+---+---+ | | gcc-6 |

Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.

added an arm64 specific CONFIG_ACPI_NFIT=y, overriding the default of =m, but > the > commit message mentions nothing about why this was done. > > Remove the arm64 specific setting and use the default of module build. > > Cc: Riku Voipio > Signed-off-by: Geoff Levand > --- &

Bug#887110: #887110: Debian Testing Cannot be installed on Macchiatobin

Hi, The first hang is because your firmware doesn't provide everything in DTB: https://patchwork.kernel.org/patch/10146687/ You need to updateyour EFI. The later hang is caused by omap_rng driver - so I've disabled in the Debian kernel as of 4.14.13-1 Riku

Bug#891062: [Pkg-chromium-maint] Bug#891062: chromium: skia fails to build on arm64

On Wed, Feb 21, 2018 at 09:59:18PM -0500, Michael Gilbert wrote: > Starting with chromium 65, arm64 fails while building skia. > > ../../third_party/skia/src/jumper/SkJumper_stages.cpp: In function 'F > from_half(U16)': > ../../third_party/skia/src/jumper/SkJumper_stages.cpp:670:12: error: >

Bug#891062: [Pkg-chromium-maint] Bug#891062: Bug#891062: chromium: skia fails to build on arm64

tags 891062 +pending thanks On Thu, Feb 22, 2018 at 11:48:10AM +, Riku Voipio wrote: > +// On ARM we expect that you're using Clang if you want SkJumper to be fast. > +// If you are, the baseline float stages will use NEON, and lowp stages will > +// also be available. (If someh

Bug#904796: chromium for arm64 lacks security updates

tags 904796 + patch upstream thanks On Mon, Jul 30, 2018 at 01:37:57AM +, Riku Voipio wrote: > On Sat, Jul 28, 2018 at 05:23:14PM -0400, Michael Gilbert wrote: > > > Chromium on arm64 in Debian Stretch stopped receiving security updates. > > > Chromium for i386, amd

Bug#904796: chromium for arm64 lacks security updates

On Sat, Jul 28, 2018 at 05:23:14PM -0400, Michael Gilbert wrote: > > Chromium on arm64 in Debian Stretch stopped receiving security updates. > > Chromium for i386, amd64 and armhf received updates for versions 67 and > > 68, however chromium for arm64 is stuck on version 66. > There was a build

Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.

On Thu, Jun 14, 2018 at 09:58:56AM +0100, Ian Campbell wrote: > On Wed, 2018-06-13 at 12:25 -0700, Geoff Levand wrote: > > On 06/09/2018 05:15 AM, Ian Campbell wrote: > > > > > I think this is probably something for the arch (or perhaps > > > platform) > > > code to deal with. See for example all

Bug#904796: chromium for arm64 lacks security updates

On Thu, Aug 02, 2018 at 11:53:04PM +, Riku Voipio wrote: > The issue seems to be binutils in stable not supporting LR = x30 alias. I've > built a fixed version. I'm travelling now, but once I get back, I'll test the > fix and submit patch upstream. Similar issue for armhf, but we d

Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.

On Tue, Sep 04, 2018 at 11:43:07AM -0700, Geoff Levand wrote: > > Is it resolved? Graeme Gregory claimed > > (https://www.spinics.net/lists/arm-kernel/msg669946.html) that "most > > people are running the firmware provided from HPe support but was never > > put on release site". > > I took that

Bug#886122: android-platform-system-core: ftbfs with GCC-7

:06.0 +0300 +++ android-platform-system-core-7.0.0+r33/debian/changelog 2018-01-12 10:41:37.0 +0200 @@ -1,3 +1,10 @@ +android-platform-system-core (1:7.0.0+r33-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix build + + -- Riku Voipio <riku.voi...@linaro.org> Fri,

Bug#876774: tested with 4.16-rc6, patch

tags +876774 pending thanks On Wed, Apr 04, 2018 at 07:08:01PM +0200, Josua Mayer wrote: > Greetings once again, > > I have now rebuilt the current kernel package from sid, with the > necessary config changes. > So far it boots, and network works. I haven't tested anything else yet. > > Please

Bug#564935: gmod: should this package be removed?

reassign 564935 ftp.debian.org retitle 564935 gmod -- RoM; ancient; abandoned upstream; thanks On Mon, Apr 16, 2018 at 07:19:36PM +0200, Moritz Muehlenhoff wrote: > On Tue, Jan 12, 2010 at 09:08:39PM +, Simon McVittie wrote: > > Source: gmod > > Severity: wishlist > > User:

Bug#894212: please add dragonboard 820c support

Package: u-boot-qcom Version: 2018.03+dfsg1-1 Severity: wishlist Tags: patch Hi, I've created a merge request to add Dragonboard 820c support in debian u-boot build: https://salsa.debian.org/debian/u-boot/merge_requests/1 Riku

Bug#894212: please add dragonboard 820c support

On Tue, Mar 27, 2018 at 01:52:46PM -0700, Vagrant Cascadian wrote: > On 2018-03-27, Riku Voipio wrote: > > I've created a merge request to add Dragonboard 820c support > > in debian u-boot build: > > > > https://salsa.debian.org/debian/u-boot/merge_requests/1 > &

Bug#881333: Qt with GLES on arm64 maintainer's decision - Was:: Upcoming Qt switch to OpenGL ES on arm64

On Mon, Nov 26, 2018 at 12:37:57PM +0100, Raphael Hertzog wrote: > were in the week-end). I was aware of the discussion but did not > had the time to chime in, yet I was the person who re-opened the bug > #881333 in the first place. > I also invited someone else who is working on a concrete

Bug#868454: Bug#908593: u-boot-menu: U_BOOT_PARAMETERS should be "ro quiet" (not empty) by default

Hi Jonas, Please go for it! I'm never offended if people fix bugs in my packages :) Riku On Sun, 31 Mar 2019 at 13:51, Jonas Smedegaard wrote: > Dear Riku, > > Are you still interested in maintaining the package u-boot-menu? > > I notice that your last upload was 1.5 years ago, and you have

Bug#928097: chromium: crc32 build errors on arm64

Hi, Sorry for missign this bug completly. I'll get into fixing at. Riku

Bug#928097: chromium: crc32 build errors on arm64

On Thu, Jun 06, 2019 at 11:07:31AM +, Riku Voipio wrote: > Sorry for missign this bug completly. I'll get into fixing at. I pushed a fix to the arm64 branch: https://salsa.debian.org/chromium-team/chromium/commit/945283642d205c7b5a5129030f525109ee7b22c1 Riku

Bug#930348: chromium: missing intrinsics on armhf

The build is fixed in: https://salsa.debian.org/chromium-team/chromium/commits/arm-fixes/debian I can make an upload if you prefer, or I can wait for you. Cheers, Riku

Bug#931707: linux: HW_RANDOM_OMAP disabled for arm64 --> please enable

SSH > > were > > coming up extremely slow, taking over a minute to start. > > > > This is caused by somebody disabling the rng driver for arm64 kernels a > > long time ago: > > linux (4.14.13-1) unstable; urgency=medium > > ... > > [ Riku Voipio ] &

Bug#970640: ITS: mtd-utils

On Sun, 20 Sep 2020 at 20:00, Bastian Germann wrote: > I would like to salvage the mtd-utils package. The current maintainer is > unresponsive on the open issues (2014 was the last answer). His last > main package action was in August 2019, packging the version 2.1.1-1. > This year, he sponsored

Bug#970640: ITS: mtd-utils

Hi, On Mon, 21 Sep 2020 at 12:29, Bastian Germann wrote: > Hi Riku, > > Thanks, please upload the NMU. As I am not a DD, I do not have commit > access on the salsa repository. Would you please grant me permission > (Gitlab user bage)? Both should be done now, Riku

Bug#964188: crashes in latest chromium

This should fix it: https://salsa.debian.org/chromium-team/chromium/-/commit/b904fa41d40b967dcc8f6984db52f7a2f6a2c83d We are not building with GCC but this seems to be exactly the place where the crash happens. chromium built with this patch has not crashed for the last few hours for me, while

Bug#964145: Chromium slow after security update

forcemerge 964161 964167 964145 thanks

Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it

Hi, On Wed, Dec 02, 2020 at 09:41:01AM +0100, Vincent Bernat wrote: > ❦ 1 décembre 2020 22:28 +01, Moritz Mühlenhoff: > > Michael has been heroically keeping up with this beast of a codebase for > > years, > > but we clearly need a broader base to sustain it going forward. > In the past, it

Bug#971442: qemu: No arm64 package in buster-backports

) buster-backports; urgency=medium + + * Rebuild for buster-backports. + * Disable libpmem on arm64. Closes: #971442 + + -- Riku Voipio Tue, 17 Nov 2020 14:55:13 +0200 + qemu (1:5.0-14~bpo10+1) buster-backports; urgency=medium * Rebuild for buster-backports. diff --git debian/control

<    5   6   7   8   9   10