Hello Salvatore,
On Mon, Jan 29, 2024 at 07:04:38PM +0100, Salvatore Bonaccorso wrote:
> Can you check if this happens as well with 6.7.1-1~exp1 in
> experimental?
Sure. I wil install the experimental kernel and see if it reproduces.
I didn't find an easy way to reproduce it, but, I can install
On Mon, Sep 18, 2023 at 06:07:54PM +0100, William de Abreu Pinho wrote:
> I am completely new to maintenance and this is my first attempt to submit a
> patch.
>
> Please find attached the proposed changes, I hope these will suffice.
Thanks for the fix. As we had discussed in person, please
Package: pastebinit
Version: 1.6-1
Severity: important
X-Debbugs-Cc: lei...@debian.org
Dear Maintainer,
I am not able to use `pastebinit` because it calls the .split() function
on a None object. Resulting in the following error:
$ pastebinit
Traceback (most recent call last):
On Wed, Nov 02, 2022 at 05:45:26PM -0300, Marcos Talau wrote:
> Control: tags 999145 + patch
> Control: tags 999145 + pending
>
>
> Dear maintainer,
>
> I've prepared an NMU for cappuccino (versioned as 0.5.1-10.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay
Package: bpftrace
Version: 0.16.0-1
Severity: normal
X-Debbugs-Cc: lei...@debian.org
Dear Maintainer,
bpftrace is segfault on everycommand when running on 6.0 kernel:
$ sudo gdb /usr/bin/bpftrace
(gdb) r -l
Starting program: /usr/bin/bpftrace -l
[Thread
Package was finally uploaded to debian, and it is showing up in the
ftpmaster NEW queue now
https://ftp-master.debian.org/new.html
The next step is waiting for the ftpmaster to review the package for
final inclusion in the debian archive.
Then, If everything is OK, I _think_ I will need to
Thanks for packaging this tool Michel. I gave it a try and this tool is
quite useful.
I've looked at the packaging and script, and they are sane. I will be
sponsoring this package.
Oh sorry about it, I will have it fixed soon.
HI Jeremy,
On 11/27/18 10:46 AM, Jeremy Bicha wrote:
> Would you be ok with me NMUing these changes?
Sure, please go ahead and NMU, as you have been doing already.
Thanks for the support here.
Breno
On Fri, 31 Aug 2018 11:46:03 -0300 Rafael Vargas wrote:
> Package: fortunes-br
> Version: 20160820
> Severity: minor
>
> Dear Maintainer,
>
> Throughout the entire fortune file, several phrases uses some accents
> (mainly the tilde) but don't use the other accents needed to be
> grammatically
On Fri, 04 May 2018 23:22:15 +0300 Sergei Golovan wrote:
> I would like to upload the tclreadline package to stretch. The package
> currently in stable misses a shared library for the ppc64el architecture,
> as indicated in [1]. I'm attaching the package diff for review. It's
>
Hi Sergei,
On Wed, May 02, 2018 at 06:25:55PM +, Sergei Golovan wrote:
> Hi Bruno,
>
> If you have access to the ppc64el hardware, could you test the fix (I've
> attached a diff, which is to be applied to the 2.1.0-15 sources)? If it's
> okay, I'll ask the release team about a stable update.
Source: tclreadline
Version: 2.1.0-15
Severity: critical
Tags: patch
Dear maintainer,
I just found that this package is not generating the shared object for
ppc64el platform, as showed below:
dpkg -c tcl-tclreadline_2.1.0-15_ppc64el.deb | grep lib/powerpc64le-linux-gnu
drwxr-xr-x root/root
Hello David,
In fact, I was not able to reproduce this bug on my machine, even on the same
version you reported the problem:
# /usr/sbin/nvme list --output-format=json
# echo $?
0
#/usr/sbin/nvme --version
nvme version 1.0
# ndctl dpkg -l | grep nvme-cli
ii nvme-cli
Hi David,
On Tue, 27 Mar 2018 15:30:07 +0200 David Guyot
wrote:
> While conducting trials using the nvme command, I noticed that the list
> argument produces SIGSEGV when used with --output-format=json, but not
> with --output-format=normal nor if this
Hi,
On 02/23/2018 03:52 PM, Aurelien Jarno wrote:
> DSA has installed the latest security kernel (4.9.82-1+deb9u2) on the
> Debian POWER8 machines running ppc64el. While they boot correctly, then
> programs segfault randomly (apt, sbuild, systemd, etc...). Passing
> no_rfi_flush to the command
-0500
@@ -1,3 +1,10 @@
+cpufrequtils (008-1.1) UNRELEASED; urgency=medium
+
+ * Remove the package binary package for Power architecture, since Power CPU
+family uses linux-cpupower to handle the machine Power management unit.
+
+ -- Breno Leitao <lei...@debian.org> Thu, 08 Feb 2018 07
) UNRELEASED; urgency=medium
+
+ * Fixed FTBFS on ppc64el (Closes: 881772).
+
+ -- Breno Leitao <lei...@debian.org> Tue, 05 Dec 2017 06:46:16 -0500
+
ruby2.5 (2.5.0~preview1-1) unstable; urgency=medium
[ Antonio Terceiro ]
diff --git a/debian/patches/0006-Fix-FTBFS-on-ppc64el.patch
b/debian/p
Good new on this bug.
Yesterday I fixed this problem and created an PR[1] for the Ruby project.
Today the PR was finally accepted by the Ruby maintainer and now we have this
problem
finally fixed uptream.
The fix on upstream branch is commit-id f79cce41695b3a3f84d88afd1b586680f29 [2]
I will
Some additional info to this bug.
I found that Ruby was not finding the proper top of the stack to do the math
and check how big the stack is.
I just fixed it and create the following Pull request:
https://github.com/ruby/ruby/pull/1767/commits/ff74937bcd50127e1e6b4879fa3c76d83efa5e65
This
This is the minimum testcase that reproduces the problem:
-- lambda.rb --
max = 20
rec = lambda{|n|
if n > 0
rec[n-1]
end
}
#rec[max]
Fiber.new{
rec[max]
}.resume
That you should call with:
# ./miniruby tool/runruby.rb lambda.rb
Some further findings:
* The
patch fixes the issue.
commit aa11d386528bbeb0f138962b3073b01319e85678
Author: Breno Leitao <lei...@debian.org)
Date: Mon Nov 27 10:47:00 2017 -0500
stack: align to 64kb
This is a workaround for ppc64el which uses 64kb page size. This align
the stack to the page size. It
Hi Terceiro,
On 11/15/2017 02:32 PM, Antonio Terceiro wrote:
> Hi,
>
> On Tue, Nov 14, 2017 at 06:16:22PM -0500, Aaron M. Ucko wrote:
>> Source: ruby2.5
>> Version: 2.5.0~preview1-1
>> Severity: important
>> Tags: upstream
>> Justification: fails to build from source
>> User:
Hi Dan,
> Hi Breno,
>
> That link has gone dead, can you repost the package?
The package is now on the NEW queue.
https://ftp-master.debian.org/new/ndctl_58.2-1.html
Are we able to get it from there?
Let me know if not, and I can re-upload to mentors.
. Closes: #878071.
+
+ -- Breno Leitao <lei...@debian.org> Mon, 09 Oct 2017 08:37:50 -0400
+
glibc (2.24-17) unstable; urgency=medium
[ Samuel Thibault ]
diff -Nru glibc-2.24/debian/sysdeps/ppc64el.mk
glibc-2.24/debian/sysdeps/ppc64el.mk
--- glibc-2.24/debian/sysdeps/ppc64el.mk
Package: glibc-source
Version: 2.24-18
Severity: normal
Tags: patch
Dear glibc maintainers,
I think it is a good idea to disable lock elision on glibc for ppc64el
on 'sid' for now. The motivation for this change is basically two:
1) There are some Hardware Transactional Memory[1] changes on
Hello Gabriel,
On Tue, Sep 26, 2017 at 09:05:58PM +0200, Lukas Schwaighofer wrote:
> Hi Gabriel,
>
> it seems you are getting the knack of it quickly :) . I don't have
> any additional feedback. I hope you're able to find a sponsor soon.
I am just doing a final review for the sponsor, and I
Hi Gabriel,
On 09/26/2017 04:05 PM, Lukas Schwaighofer wrote:
Hi Gabriel,
it seems you are getting the knack of it quickly :) . I don't have
any additional feedback. I hope you're able to find a sponsor soon.
I also re-reviewed the package, and it seems OK for me, although I must
admit I
On Sat, 9 Sep 2017 20:20:03 -0300 Roberto Oliveira
> > In that case please override this warning and write a comment describing
> > the reason.
> Fixed.
>
> > libopagent1 should be Section: libs.
> Fixed.
Thanks Roberto.
wRar, do you still any concern about this package?
Although lack of recent updates, we are still working on this problem.
Barry (on CC) is allocated to work on this issue and should have updates soon.
Operf was part of Debian once and then it got removed.
Are you planning to be the maintainer for this package?
Hello Hon,
I reviewed the package, and after the fixes we discussed and the legal
conversation[1], I think this package is ready to go to the NEW queue.
Thanks for your contribution to Debian.
[1] https://lists.debian.org/debian-legal/2017/07/msg00022.html
signature.asc
Description: PGP
Some new discover I did today:
1) On function do_random(), the 'values' pointer is being corrupted after the
rand() syscall - In the failure case. If I remove the rand() function, I do
not see corruption.
2) If I get the original 'values' pointer, save it and check it later, it is
corrupted
hi Ryan,
On 07/11/2017 02:58 AM, Ryan Tandy wrote:
> Today I built Linux 4.12 from upstream source and the test program still
> crashes. I was looking at your fixes to initialize load_{fp,tm,vec} as well
> as someone else fixing the CONFIG_ALIVEC typo but none of those have helped.
Right, I
hi Ryan,
On Sun, Jul 09, 2017 at 08:56:59AM -0700, Ryan Tandy wrote:
> There seems to be a regression on powerpc64 (both endians) that can corrupt
> the vector-scalar registers (VSRs) in a threaded program.
>
> I believe the bad commit is this one:
>
> 4.9.0:
>
Hey Adrian,
On Thu, Jul 06, 2017 at 10:44:21PM +0200, John Paul Adrian Glaubitz wrote:
> Hi Breno!
>
> On 07/06/2017 09:31 PM, Breno Leitao wrote:
> > I think I found the real case of the problem here. There is an array
> > being allocated, and initialized until 'i'.
&
Ryan,
> Nice. I was able to reproduce it and debug it further. The problem seems
> to be related to a invalid branch/jump, the the next address is not
> memory mapped, thus the segfault. The new address is completely random,
> and definitely is wrong.
I think I found the real case of the
Hi Ryan,
On Mon, Jul 03, 2017 at 03:39:35PM -0700, Ryan Tandy wrote:
> Hi debian-powerpc,
>
> Would a ppc64(el) porter be able to help me look at #866122? I have
> requested a porterbox account but it's not gone through yet, and I am unable
> to reproduce the issue at all in a qemu VM.
You can
On Sat, Apr 15, 2017 at 10:00:06AM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the sysstat package:
Thank you!
There is an upstream fix for this problem, targeting both gcc trunk and GCC-6:
On GCC-6 branch it is id 246509
r246509 | meissner | 2017-03-27 16:35:35 -0300 (Mon, 27 Mar 2017) | 42 lines
[gcc]
2017-03-27 Michael Meissner
Hello doko,
I tried to reproduce this problem, but, I just see a warning other than
an error:
I am building the package on 'unstable' using debuild:
cc -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D__CHECK_ENDIAN__ -g -O2
-fdebug-prefix-map=/home/breno/source/nvme-cli-1.1=.
Control: tags -1 patch
An update on this bug. Rich was able to create a patch that fixes this problem.
http://www.openwall.com/lists/musl/2017/03/08/2
Can we cherry pick it once it gets accept upstream?
diff --git a/arch/powerpc64/reloc.h b/arch/powerpc64/reloc.h
index e1bad00..faf70ac 100644
Package: musl
Version: 1.1.16-2
Severity: normal
Tags: upstream
Musl package on Debian on ppc64le is broken.
When running any software with it, it segfaults. Doing a little bit of
debugging I found that libc.so is broken.
I got the upstream code, and found that the problme is also
reproducible.
Hi Adam,
On Fri, Mar 03, 2017 at 05:41:51PM +, Adam D. Barratt wrote:
> On 2017-03-03 17:29, Breno Leitao wrote:
> >Package jsvc (commons-daemon) contains a patch enabling ppc64el on
> >version 1.0.15-6 (currently on Jessie), but it does not work. A new
> >patch requi
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
Dear Release team,
Package jsvc (commons-daemon) contains a patch enabling ppc64el on
version 1.0.15-6 (currently on Jessie), but it does not work. A new
patch required to add
Hi Aaron,
On Fri, 17 Feb 2017 09:48:32 -0500 "Aaron M. Ucko" wrote:
> For the record, the (immediate) problem is that the gzseek64 and
> gzoffset64 wrappers in software.c specify the wrong return type
> (z_off_t rather than the correct z_off64_t, which is equivalent only
> on
-02 07:51:51.0
-0500
@@ -1,3 +1,9 @@
+commons-daemon (1.0.15-7.1) unstable; urgency=medium
+
+ * Fixes "Cannot find any VM in Java Home" on ppc64el (Closes: #856560)
+
+ -- Breno Leitao <lei...@debian.org> Thu, 02 Mar 2017 07:51:51 -0500
+
commons-daemon (1.0.15-7) u
Package: jsvc
Version: 1.0.15-7
Severity: serious
Tags: patch
Hello, package jsvc does not work on ppc64el right now.
On ppc64 and ppc64le archs jsvc looks for jvm.cfg and JVM shared objects
in the wrong path. Be it used with IBM Java or OpenJDK (where the
problem was first encountered), there
> I can work on it if Nish is not planning to submit his package to Debian.
I just created the package and it is at mentors.
https://mentors.debian.net/package/ndctl
Any review is appreciated. If no problems are found, I am willing to upload it.
Hi Martin,
On Thu, 09 Feb 2017 17:34:33 + Martin Pitt wrote:
> Source: systemd
> Source-Version: 232-16
How will it show up in Stretch?
Are you going to move systemd to 232-16 or backport the patch to stretch 232-15?
Thank you,
Breno
Package: wnpp
Severity: wishlist
Owner: Breno Leitao <lei...@debian.org>
* Package name: ndctl
Version : v55
Upstream Author : Dan Williams
* URL : https://github.com/pmem/ndctl
* License : GPL
Programming Lang: C
Description : ndctl is a u
Hi Dan,
On 02/07/2017 05:03 PM, Dan Williams wrote:
> On Tue, Feb 7, 2017 at 10:55 AM, Breno Leitao <bren...@br.ibm.com> wrote:
>> Is there anyone working on packaging ndctl? If not, I have interest in
>> working on it.
>>
>
> No, I don't think there is.
>
&g
Is there anyone working on packaging ndctl? If not, I have interest in
working on it.
Hi Fernando,
On Tue, 31 Jan 2017 22:44:49 -0200 Fernando Seiti Furusato
wrote:
> I fixed some problems with the package, that is why I reopened this RFS.
This packages sounds in a good shape for me. If no one has objection to it, I
would like to sponsor it to be
Source: bpfcc
Version: 0.2.0
Severity: normal
Currently bpfcc does not build on ppc64el (and aaarch64) due to missing
luajit package.
The luajit upstream situation for the new architecture is not clear
, so, Debian have a luajit package in the experimental archive that
contains the ppc64el patch
-0500
+++ musl-1.1.16/debian/changelog 2017-01-17 11:45:02.0 -0500
@@ -1,3 +1,10 @@
+musl (1.1.16-1.1) UNRELEASED; urgency=medium
+
+ * Enable musl to build on ppc64el. In order to do it, using type "long
+double" as "double".
+
+ -- Breno Leitao <lei...@debia
Hi Adrian,
On 01/04/2017 08:50 AM, John Paul Adrian Glaubitz wrote:
> Hi!
>
> The current version 7.4.4-3 of libatomic-ops builds fine on all architectures
> [1].
> Can we close this or am I missing something?
I understand that they are building because the tests are being bypassed as
an
Hello Faidon,
On 12/17/2016 10:54 PM, Faidon Liambotis wrote:
> severity 824573 wishlist
> thanks
>
> Hi Breno,
>
> On Tue, May 17, 2016 at 01:12:12PM -0400, Breno Leitao wrote:
>> HHVM is being ported to ppc64el arch[1], and at the moment, 100% of the 1041
>>
Hi Ghis,
On 12/14/2016 09:30 AM, Ghislain Vaillant wrote:
> Thanks for your contribution. Let me know if a long-term solution comes up
> later.
Sure. I closed the bug on the changelog, but, you can keep it open to track
the final and long term solution.
cy=medium
+
+ * Avoid running tests with long double on ppc64el due to failing tests
+(Closes: #844403)
+ * Add build-dependency for latex.
+
+ -- Breno Leitao <lei...@debian.org> Fri, 09 Dec 2016 16:12:51 -0500
+
nfft (3.3.2-1) unstable; urgency=medium
* New upstream version 3.3.2
Hello Lucio,
Thanks for submitting the package to Debian, but I still see major lintian
errors on the package you submit.
Please address, at least, error and warnings lintian erros. These are
important before asking for sponsorship.
Closing the pedantic bugs is a plus. :-)
Also, it seems to be
Hello Ghislain,
On 12/09/2016 07:01 AM, Ghislain Vaillant wrote:
> I might eventually just bypass testing for ppc64el to let the package
> transition to testing, unless you think you are gonna have a fix ready very
> soon. With the transition window extended to 10 days and the soft-freeze
>
Hi Lucio,
Thanks for contributing to Debian.
Unfortunately I was not able to build this package, since it is failing when
building:
Makefile:129: recipe for target 'de_DE.gmo' failed
make[4]: *** [de_DE.gmo] Error 1
make[4]: *** Waiting for unfinished jobs
rm -f fr_FR.gmo &&
Hello Lucio,
Thanks for contributing to Debian. I found some issues with this package:
1) There are some lintian errors. Please fix them.
2) The package is not able to be rebuild, i.e, the clean process does not
seem to be clear.
These are the problems I am facing when I run two times a
Hello Lucio,
Thanks for contributing to Debian. I just run lintian on this package, and it
seems to contain one error and one warning:
E: ginger-base source: missing-build-dependency-for-dh-addon python2 =>
python:any | python-all:any | python-dev:any | python-all-dev:any
W: ginger-base
We just created a pull request to have this fixed upstream.
https://github.com/pydata/numexpr/pull/235
Should we create a Debian patch also?
g 2016-11-28 15:12:29.0 -0500
@@ -1,3 +1,9 @@
+yadifa (2.2.2-1.1) UNRELEASED; urgency=medium
+
+ * Avoid compiling with O3 on ppc64el due to a known bug
+
+ -- Breno Leitao <breno.lei...@gmail.com> Mon, 28 Nov 2016 15:12:29 -0500
+
yadifa (2.2.2-1) unstable; urgency=medium
* Ne
On 11/27/2016 07:16 PM, Ghislain Vaillant wrote:
> On Thu, 24 Nov 2016 18:49:29 -0200 Breno Leitao <bren...@br.ibm.com> wrote:
>> I am looking at this issue, and the first test set is checkall.
>>
>> If I run it inside dpkg-buildpackage, it fails as in the log, but, if
I am looking at this issue, and the first test set is checkall.
If I run it inside dpkg-buildpackage, it fails as in the log, but, if I run
it isolated, I see no errors, as showed:
$ ./checkall 2>&1 | grep -i fail
$
Looking all tests I see "-> OK". Anyway, I am continue to debug what is the
On 11/20/2016 07:41 AM, Adrian Bunk wrote:
>
> Lots of failures like:
>
Yes. I just tried it here, and more than 40 tests failed.
It is usually off by 1, and I am wondering if we are being bite by a similar
issue I found on OpenJDK, where there are math inconsistency when using
optimization
Hello Martín,
On 11/15/2016 10:21 AM, Martín Ferrari wrote:
> Hi Breno,
>
> Thanks for the patch!
>
> I was going to merge all this and reupload after merging the new
> upstream release, but I have noticed these patches are already in upstream.
>
> So, does it make sense to merge this instead
I just tested haskell-zeromq4-haskell build with a patched GHC and it
worked fine, so, I understand also that the problem is fixed.
I just installed the packages also, and they seem to be working properly:
dpkg -l | grep zeromq
ii libghc-zeromq4-haskell-dev 0.6.5-5
reassign ghc
After some further debug, I found this is, in fact, a ghc bug and it was
fixed in version 8.0.2, as showed in:
https://ghc.haskell.org/trac/ghc/ticket/12621
Source: haskell-zeromq4-haskell
Version: 0.6.5
Severity: serious
Justification: fails to build from source (but built successfully in the past)
The package haskell-zeromq4-haskell is failing to build on ppc64el port
due to the following error:
[1 of 6] Compiling System.ZMQ4.Internal.Base (
Is anyone looking/debugging this issue?
-gopsutil (2.1-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Breno Leitao ]
+ * Fix FTBFS and add support for ppc64el. (Closes: #820466)
+
+ -- Fernando Seiti Furusato <ferse...@linux.vnet.ibm.com> Thu, 03 Nov 2016
10:57:27 -0200
+
golang-github-shirou-gopsutil (2.1-2) un
Package: sysstat
Version: 11.4.1-1
Severity: normal
Tags: patch
Currently sysstat does not parse /proc/cpuinfo properly on ppc64el
platform, showing:
$ sar -m CPU 1 10
Linux 4.7.0-1-powerpc64le (testing) 11/01/2016 _ppc64le_
(8 CPU)
Hello Andreas,
On Tue, 25 Oct 2016 13:25:18 +0200 Andreas Henriksson wrote:
> As already mentioned the offending ppc64el binaries was removed.
I just fixed created a debdiff to fix golang-github-shirou-gopsutil.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820466
I hope
08:25:56.0 -0400
@@ -1,3 +1,9 @@
+golang-github-shirou-gopsutil (2.1-3) UNRELEASED; urgency=medium
+
+ * Fix FTBFS and add support for ppc64el. (Closes: #820466)
+
+ -- Breno Leitao <breno.lei...@gmail.com> Wed, 26 Oct 2016 08:25:56 -0400
+
golang-github-shirou-gopsutil (2.1-2) un
Thanks Andreas,
I am preparing a new version for cappuccino to solve this issue.
Closing this bug, since gnome-menus works fine on ppc64el.
Thanks!
/debian/changelog
+++ tablix2-0.3.5/debian/changelog
@@ -1,3 +1,10 @@
+tablix2 (0.3.5-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS on ppc64el and arm64. (Closes: #756442)
+
+ -- Breno Leitao <lei...@debian.org> Mon, 05 Sep 2016 15:48:40 -0400
+
tablix2 (0.3.5-3) un
/changelog 2016-09-02 14:08:34.0 -0400
@@ -1,3 +1,9 @@
+skiboot (5.2.4-2.1) UNRELEASED; urgency=medium
+
+ * Build and distribute external binaries. (Closes: #836405)
+
+ -- Breno Leitao <lei...@debian.org> Fri, 02 Sep 2016 14:08:34 -0400
+
skiboot (5.2.4-2) unstable; urgency=
Source: skiboot
Version: 5.2.4-2
Severity: important
Hello maintainer,
There are some external binaries that are not being built today, and we
would like to build them, as make them available. They are:
* getscom
* pflash
* putscom
I also undertstand that it should be included in
Hello Fernando,
On Tue, Aug 23, 2016 at 04:20:47PM -0400, Fernando Seiti Furusato wrote:
> Changes since the last upload:
>
> * QA upload.
>
> [ Aurelien Jarno ]
> * debian/rules: added dh_autotools-dev_updateconfig and
> dh_autotools-dev_restoreconfig to fix FTBFS on new
Package: steghide
Version: 0.5.1-10
Severity: important
Currently this package does not build on a clean environemnt because it
depends on libtool binary, but does not mark libtool-bin as Build-dependent.
This causes the following FTBFS:
libtool --mode=link g++ -O2 -Wall -o steghide Arg.o
Package: cappuccino
Version: 0.5.1-2.3
Severity: normal
Currently cappuccino does not run properly on a default Debian system
because it expects that polygen (which is a game) is on the PATH, which
is not true.
In that way, the software complains as following:
sh: 1: polygen: not found
764494
Regards,
Breno Leitao
signature.asc
Description: PGP signature
+ (double checked that it didn't change when compiling with GCC5 and
+ GCC6 with this fix). (Closes: #811789)
+
+ -- Breno Leitao <bren...@br.ibm.com> Sun, 17 Jul 2016 18:02:37 -0400
+
zvbi (0.2.35-10) unstable; urgency=medium
* Migrations:
diff -Nru zvbi-0.2.35/debian/p
/changelog 2012-05-13 10:38:30.0 -0400
+++ critterding-1.0-beta12.1/debian/changelog 2016-07-17 17:11:02.0 -0400
@@ -1,3 +1,10 @@
+critterding (1.0-beta12.1-1.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fixing FTBFS on GCC 6. (Closes: 811621)
+
+ -- Breno Leitao <b
-beta12.1/debian/changelog 2016-07-17 17:11:02.0
-0400
@@ -1,3 +1,10 @@
+critterding (1.0-beta12.1-1.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fixing FTBFS on GCC 6. (Closes: 811621)
+
+ -- Breno Leitao <bren...@br.ibm.com> Sun, 17 Jul 2016 16:46:12 -0400
+
critterdin
n 32 bits system (Thanks Steve
Langasek) (Closes: #830521)
Regards,
Breno Leitao
signature.asc
Description: PGP signature
I am looking at this problem, and I understand that the following patch fixes
this problem:
--- critterding-1.0-beta12.1.orig/src/brainz/brainz.cpp
+++ critterding-1.0-beta12.1/src/brainz/brainz.cpp
@@ -137,7 +137,7 @@ Brainz::Brainz()
// clear Motor Outputs
> Please consider
> applying this patch in Debian as well, and forward upstream as necessary.
Just got the patch accepted by upstream maintainer also.
https://github.com/linux-nvme/nvme-cli/commit/90f00efdd89866b5f4f389c0b0a7ca4305c76303
The other two off-the-tree patches were also accepted
Hello Steve,
On 07/08/2016 06:49 PM, Steve Langasek wrote:
> I've applied the attached patch in Ubuntu to address this. Please consider
> applying this patch in Debian as well, and forward upstream as necessary.
Thanks for fixing it. I just created a new package version with this fix.
The new
* New upstream release
-- Breno Leitao <bren...@br.ibm.com> Sun, 03 Jul 2016 07:12:26 -0400
Regards,
Breno Leitao
I would like to ask the same thing, since this there are some patches that
improves ppc64el arch.
These are the important patches that made 2.18 version, and are important for
ppc64el:
* 2ede65360abc62cb0cef72d67fa456d69d5516f4
* 954c051dbb8580b8b22f2fb32dbefd724fe491a2
*
Ben,
On Tue, 26 May 2015 01:58:09 +0100 Ben Hutchings wrote:
Thanks for restoring support for 32-bit code generation. I recognise
it's not something you really want to support, so I'm leaving the kernel
bug open but changing the title/severity accordingly.
This was
On Sun, 12 Jun 2016 23:58:57 +0200 Jordi Mallach wrote:
> Upstream is aware of this build failure, and porter help would be welcome.
Right. I will add it to my queue. since it is !ppc64el and the package is more
focused on desktop (instead of server), it will have a low
Hello Paul,
On 06/08/2016 11:29 PM, Paul Wise wrote:
> n Thu, Jun 9, 2016 at 4:52 AM, Breno Leitao wrote:
>
>> Description : A hardware accelerated version of zLib using PCIe with
>> FPGA
> ...
>> This package dependes on a specific PCIe3 FPGA Accelerator
1 - 100 of 474 matches
Mail list logo