date:20140609

Bug#729132: patch: FTBFS due to ed check, with solution

2014-06-09 Thread GCS

On Mon, Jun 9, 2014 at 3:23 PM, Thorsten Glaser t...@mirbsd.de wrote:
 László Böszörményi dixit:
 Tested it on four machines: 2x Sid/amd64, Jessie/amd64 and kFreeBSD/i386 .

 This is very… limited ;)
 But have some variations. Package list of Sid and Jessie,
architectures of amd64 and i386, Linux and kFreeBSD toolchain.

Please prove somehow this FTBFS first that set it to severity serious.

 While this is indeed not “serious” – FTBFS on debian-ports.org archi-
 tectures aren’t – it is a valid problem, for which I provided a valid
 fix (just run it through uniq). Please apply that fix.
 OK, my next upload will contain that fix. Still, do you know what's
cause this on those architectures?

Thanks,
Laszlo/GCS


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#751032: Please enable -fstack-protector on arm64 now that toolchain supports it

2014-06-09 Thread Adam Conrad

On Mon, Jun 09, 2014 at 08:17:21PM +0200, Guillem Jover wrote:
  -if ($cpu =~ /^(ia64|alpha|mips|mipsel|hppa|arm64)$/ or $arch eq 'arm') 
  {
  -   # Stack protector disabled on ia64, alpha, arm64, mips, mipsel, hppa.
  +if ($cpu =~ /^(ia64|alpha|mips|mipsel|hppa)$/ or $arch eq 'arm') {
  +   # Stack protector disabled on ia64, alpha, mips, mipsel, hppa.
 
 Thanks, applied locally, will be included in 1.17.11, which I think
 I'll be releasing earlier than anticipated.

Awesome, thanks.  I noticed after sending it that my patch was against
1.17.9, and that regex changed in 1.17.10, but I assume you sorted that
out when it failed to apply cleanly. :P

... Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#750953: flash-kernel: Add support for SolidRun Cubox-i Dual/Quad.

2014-06-09 Thread Ian Campbell

On Mon, 2014-06-09 at 09:36 -0700, Vagrant Cascadian wrote:
 On Mon, Jun 09, 2014 at 08:39:24AM +0100, Ian Campbell wrote:
  On Sun, 2014-06-08 at 14:27 -0700, Vagrant Cascadian wrote:
   It works with the default u-boot environment in the u-boot package in 
   Jessie.
   It requires /etc/default/flash-kernel to define root= in 
   LINUX_KERNEL_CMDLINE,
  
  Are you sure about
  that? /usr/share/initramfs-tools/hooks/flash_kernel_set_root should be
  setting a fallback root in the initrd, so if the command line doesn't
  have root= I think things should still work.
 
 As long as / is defined in /etc/fstab...

Ah yes, true.

   It only supports booting off of mmc, though in theory booting off of eSATA
   might be possible.
  
  When that comes homefully we can upgrade in a backwards compatible way.
  I suppose/home it might be as simple as:
  if test -z ${device} ; then
  setenv device mmc
  fi
  instead of the unconditional setenv. That assumes that the uboot env
  would then set $device to scsi, but that seems pretty conventional
  nowadays.
 
 Need to quote the tested variable:
 
 if test -z ${device} ; then
   setenv device mmc
 fi
 
 Sounds good to me, though ${partition} would need to have an appropriate value
 set in this case as well, as it currently uses ${mmcdev}:${mmcpart}. Not sure
 how complicated it's worth making it...

I think it is OK as it was, I just wanted to check we weren't painting
ourselves into a corner wrt future changes, I think I'm convinced we are
not.

 Also looks like Bootloader-Sets-Incorrect-Root: no can be dropped entirely.

Yes.

Do you have push rights to this repo or would you like me to pickup the
patch?

Ian.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#711833: [supp...@mentors.debian.net: postr uploaded to mentors.debian.net]

2014-06-09 Thread Yoann Gauthier

Hello,

I fixed the desktop-entry-lacks-keywords-entry as asked.
Find attached the patch. I used quilt to create my patch :
04-fix_desktop_keywords.patch and then git format to create patch file.

Regards,

PS : have access (push request) to your repository will be easier for me.

Yoann

2014-06-03 22:50 GMT+02:00 Alexander Alemayhu alexan...@bitraf.no:

On Tue, Jun 03, 2014 at 11:45:27AM +0200, Yoann Gauthier wrote:
Hi Alexander,

What are the next tasks I can do to help for the packaging ?

You could look at the desktop-entry-lacks-keywords-entry[0] lintian tag
and try
to fix it. I was planning on fixing it but wanted to prioritize the
autotools
warnings. Hopefully we can get some advice from David.

It looks like you would need to create a debian patch file to modify
data/postr.desktop.in.in. If you are unfamiliar with quilt, take a look
at this
introduction[1].

PS: Remember to fetch the latest changes, before making new changes. It
might
help in avoiding merge conflicts.

PPS: desktop-entry-lacks-keywords-entry only occurs when using `lintian
-EvIL
+pedantic` on my machine.

[0]:
http://lintian.debian.org/tags/desktop-entry-lacks-keywords-entry.html
[1]:

http://raphaelhertzog.com/2012/08/08/how-to-use-quilt-to-manage-patches-in-debian-packages/

Regards,

Yoann

2014-06-02 21:26 GMT+02:00 Alexander Alemayhu alexan...@bitraf.no:

On Mon, Jun 02, 2014 at 10:30:40AM +0200, Yoann Gauthier wrote:
Hi,

For man page license, I propose to distribute it under GNU GLP (v3).
Do
you
agree ?

I am no license expert, but I think it is okay assuming you mean GNU
GPL.

Okay for the maintener part, I will set the maintainer to Python
Applications Packaging Team.

Regards,

Yoann

2014-06-01 18:26 GMT+02:00 Alexander Alemayhu alexan...@bitraf.no:

On Sun, Jun 01, 2014 at 03:50:27PM +0200, Yoann Gauthier wrote:
Le 31 mai 2014 20:00, Alexander Alemayhu alexan...@bitraf.no
a
écrit :

On Sat, May 31, 2014 at 03:29:16PM +0200, Yoann Gauthier wrote:
Hello,

Hei,

I wrote the man page (attachment). I have no access to the
repository
today, I will upload the page to repository tomorrow.

Nice. I decided to use github as the Vcs-* since collab-maint
seems to
be
for
people packing together with DDs. Maybe we should ask for
access
and
push
our
changes there?

I don't understand Vcs, what is it ?

A akronym for Version Control System[0].

I think you have a typo 'MAINTENERS' should be 'MAINTAINERS'.
It
could
be
a
good idea to ask for others to review the man page. Which
license
do
you
want
to distribute the man page with? we have to mention the
license in
debian/copyright.

Agree for the typo, this evening I will read again the man page
and
add
more information maybe. Okay for the license, i will think.

In order to stay consistent with the debian/control file we should
set
the
maintainer to Python Applications Packaging Team
python-apps-t...@lists.alioth.debian.org

Regards,

Yoann

[0]: http://en.wikipedia.org/wiki/Version_control

2014-05-30 12:36 GMT+02:00 Yoann Gauthier
yoann.gauthi...@gmail.com
:

Hi Alexander,

Yes, I am going to write the man page. It will be finished
today or
tomorrow.
Okay for the RFS.

Regards,

Yoann

2014-05-30 10:43 GMT+02:00 Alexander Alemayhu
alexan...@bitraf.no
:

Hei Yoann,

below is a message I recived after reuploading to
mentors.debian.net.
The warnings I mentioned earlier are visible in the
package
page.
Are you going to write a man page? I would like to send a
RFS
after
fixing
some more of the warnings to the PAPT list.

- Forwarded message from mentors.debian.net
supp...@mentors.debian.net -

Date: Wed, 28 May 2014 21:33:31 + (UTC)
From: mentors.debian.net supp...@mentors.debian.net
To: alexan...@bitraf.no
Subject: postr uploaded to mentors.debian.net

Hi.

Your upload of the package 'postr' to mentors.debian.net
was
successful. Others can now see it. The URL of your
package is:
http://mentors.debian.net/package/postr

The respective dsc file can be found at:

http://mentors.debian.net/debian/pool/main/p/postr/postr_0.13-1.dsc

If you do not yet have a sponsor for your package you may
want to
go
to

Bug#729132: patch: FTBFS due to ed check, with solution

2014-06-09 Thread Thorsten Glaser

László Böszörményi dixit:

 OK, my next upload will contain that fix. Still, do you know what's
cause this on those architectures?

Yes: difference in compiler optimisations. Basically, you use the
string ed in the source at least two times; with some compiler
versions and architectures, this is optimised into one string in
the executable, with some it isn’t (for example because PC-relative
addressing can only go so far, and the alternative is computationally
more expensive).

bye,
//mirabilos
-- 
„Cool, /usr/share/doc/mksh/examples/uhr.gz ist ja ein Grund,
mksh auf jedem System zu installieren.“
-- XTaran auf der OpenRheinRuhr, ganz begeistert
(EN: “[…]uhr.gz is a reason to install mksh on every system.”)


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#750703: make-kpkg fails completely to build a current kernel image

2014-06-09 Thread Manoj Srivastava

On Fri, Jun 06 2014, Klaus Ethgen wrote:

 For your information, Version 13.007 builds well.

I have looked at the diff between 13.007 and 13.013, and I can't
 see anything that could contribute to this. Most of the changes were
 about adding kernel-common, and adjusting dependencies a bit; and
 nothing that would lead to the errors exhibited.

I am continuing to research this issue.

manoj
-- 
To the systems programmer, users and applications serve only to provide
a test load.
Manoj Srivastava sriva...@acm.org http://www.golden-gryphon.com/  
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C


signature.asc
Description: PGP signature

< 1 2 3 4 >

201 - 300 of 323 matches

Mail list logo