Re: mipsel -m64 testing
+++ Michael R. Crusoe [2015-05-27 20:19 +]: > Hello, > > With regards to the FTBFS below, is Debian mipsel always 64 bit, always 32 > bit, > or a mix? mipsel (and mips) are 32-bit ABIs. mips64el (and mips64) are the debian names for the 64-bit ABIs. > How would I test that? dpkg-architecture -amipsel -qDEB_HOST_ARCH_BITS > From: Andreas Tille > > Hi Michael, > > On Wed, May 27, 2015 at 01:37:30PM +, Michael R. Crusoe wrote: > > I interpret '-m64' as a signal that the developer only supports 64 bit > > OSes/hardware. From what I can find, mipsel can be 32 or 64bit. So I would > > suggest removing mipsel from the supported architecture series. 'gcc -m64' (on mipsel) is multilib speak for gcc-mips64el-linux-gnuabi64 Debian should be fixing up these multilib shortcuts because they are not consistent between architectures. '-m64' means different things on different arches. Using an explicit GNU triplet in toolchain invocations will always work both natively and for crossing. See https://wiki.debian.org/ToolChain/Cross#Multiarch_vs_Multilib > > Does that make sense? > > Not really since it also fails on arm64 with the same error. adding -m64 on arm64 to a gcc invocation will result in an error because it is meaningless. In general we should (IMHO) simply not be using -m32 or -m64 in debian builds. Not sure if I have understood you properly there? Maybe there is some other reason for the build failure. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2015052734.ge24...@halon.org.uk
mipsel -m64 testing
Hello, With regards to the FTBFS below, is Debian mipsel always 64 bit, always 32 bit, or a mix? How would I test that? Thanks! -- Forwarded message - From: Andreas Tille Date: Wed, May 27, 2015, 10:09 Subject: Re: [nore...@buildd.debian.org: failed mipsel build of parafly 0.0.2013.01.21-1] To: Michael R. Crusoe Cc: Debian Med Packaging Team Hi Michael, On Wed, May 27, 2015 at 01:37:30PM +, Michael R. Crusoe wrote: > I interpret '-m64' as a signal that the developer only supports 64 bit > OSes/hardware. From what I can find, mipsel can be 32 or 64bit. So I would > suggest removing mipsel from the supported architecture series. > > Does that make sense? Not really since it also fails on arm64 with the same error. I have learned that there are upstream authors out there who are adding options according "good feeling" (no idea whether parafly authors belong to this group). I'd recommend asking on debian-mentors@lists.debian.org since I'm not an expert in this myself. Kind regards Andreas. > On Wed, May 27, 2015 at 8:36 AM Andreas Tille wrote: > > > Hi Michael, > > > > perhaps simply droping the option -m64 would solve this (same for > > arm64). I vaguely remember that it is redundant for all architectures > > but please double check this. > > > > Kind regards > > > > Andreas. > > > > - Forwarded message from Debian buildds > > - > > > > Date: Wed, 27 May 2015 09:45:01 + > > From: Debian buildds > > To: para...@packages.qa.debian.org > > Subject: failed mipsel build of parafly 0.0.2013.01.21-1 > > > > * Source package: parafly > > * Version: 0.0.2013.01.21-1 > > * Architecture: mipsel > > * State: failed > > * Suite: sid > > * Builder: mayer.debian.org > > * Build log: > > https://buildd.debian.org/fetch.cgi?pkg=parafly&arch=mipsel&ver=0.0.2013.01.21-1&stamp=1432719507&file=log > > > > Please note that these notifications do not necessarily mean bug reports > > in your package but could also be caused by other packages, temporary > > uninstallabilities and arch-specific breakages. A look at the build log > > despite this disclaimer would be appreciated however. > > > > > > > > > > - End forwarded message - > > > > -- > > http://fam-tille.de > > -- http://fam-tille.de
Bug#786974: marked as done (RFS: owslib/0.8.13-1)
Your message dated Wed, 27 May 2015 21:30:23 +0200 with message-id <55661b4f.4080...@xs4all.nl> and subject line RFS: owslib/0.8.13-1 [uploaded] has caused the Debian Bug report #786974, regarding RFS: owslib/0.8.13-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 786974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal X-Debbugs-CC: pkg-grass-de...@lists.alioth.debian.org Dear mentors, I am looking for a sponsor for my package "owslib" Package name: owslib Version : 0.8.13-1 Upstream Author : Tom Kralidis URL : http://geopython.github.com/OWSLib/ License : BSD-3-Clause Section : python It builds those binary packages: python-owslib - Client library for Open Geospatial (OGC) web services To access further information about this package, please visit the following URL: http://mentors.debian.net/package/owslib Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/o/owslib/owslib_0.8.13-1.dsc More information about OWSLib can be obtained from http://geopython.github.com/OWSLib/. Changes since the last upload: * Move to unstable Regards, Johan Van de Wauw --- End Message --- --- Begin Message --- Hi Johan, Thanks for your work on this package too. On 05/27/2015 12:23 PM, Johan Van de Wauw wrote: > I am looking for a sponsor for my package "owslib" I've sponsored the upload. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1--- End Message ---
Bug#786968: marked as done (RFS: python-snuggs/1.3.1-1 [ITP])
Your message dated Wed, 27 May 2015 20:37:47 +0200 with message-id <55660efb.6020...@xs4all.nl> and subject line RFS: python-snuggs/1.3.1-1 [ITP] [uploaded] has caused the Debian Bug report #786968, regarding RFS: python-snuggs/1.3.1-1 [ITP] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 786968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: pkg-grass-de...@lists.alioth.debian.org Dear mentors, I am looking for a sponsor for my package "python-snuggs" Package name: python-snuggs Version : 1.3.1-1 Upstream Author : Sean Gillies URL : https://github.com/mapbox/snuggs License : BSD-3 Section : python It builds those binary packages: python-snuggs - S-expressions for numpy - Python 2 version python3-snuggs - S-expressions for numpy - Python 3 version To access further information about this package, please visit the following URL: http://mentors.debian.net/package/python-snuggs Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/python-snuggs/python-snuggs_1.3.1-1.dsc More information about Snuggs can be obtained from https://github.com/mapbox/snuggs. Changes since the last upload: * Initial upload (closes: #783712) Regards, Johan Van de Wauw --- End Message --- --- Begin Message --- Hi Johan, Thanks for your work on this package. On 05/27/2015 11:47 AM, Johan Van de Wauw wrote: > I am looking for a sponsor for my package "python-snuggs" There was a small issue with the control file which contained a trailing space after a dot. I fixed it for your and uploaded the results. Since the package will have to pass the NEW queue, I'm closing the RFS manually. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1--- End Message ---
Re: How to create a metapackage
Hi, On Thu, May 21, 2015 at 11:34:48PM +0200, Santiago Vila wrote: > On Wed, May 20, 2015 at 10:34:05PM +0200, Andreas Tille wrote: > > There are several discussions on Debian mailing lists all with the > > conclusion that Depends are wrong for metapackages. Please use > > Recommends. > > Well, the very first thing I do on a new Debian system is this: > > echo 'APT::Install-Recommends "0";' > /etc/apt/apt.conf.d/75recommends > > i.e. tell apt-get to ignore recommends. > > In this case a metapackage using recommends does not seem very useful, > I guess. You name it. In *this* case. You should expect that things are working differently if you derive from the default, right? Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150527151735.ga21...@an3as.eu
Bug#786974: RFS: owslib/0.8.13-1
Package: sponsorship-requests Severity: normal X-Debbugs-CC: pkg-grass-de...@lists.alioth.debian.org Dear mentors, I am looking for a sponsor for my package "owslib" Package name: owslib Version : 0.8.13-1 Upstream Author : Tom Kralidis URL : http://geopython.github.com/OWSLib/ License : BSD-3-Clause Section : python It builds those binary packages: python-owslib - Client library for Open Geospatial (OGC) web services To access further information about this package, please visit the following URL: http://mentors.debian.net/package/owslib Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/o/owslib/owslib_0.8.13-1.dsc More information about OWSLib can be obtained from http://geopython.github.com/OWSLib/. Changes since the last upload: * Move to unstable Regards, Johan Van de Wauw -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAJOp35=q7+pvaz-rkcrq2hgabyw9ezuwwkqnq12d+6fktxe...@mail.gmail.com
Bug#785426: RFS: cv/0.6-1 [ITP] -- cv - Coreutils (progress) Viewer)
On Wed, 2015-05-27 at 09:27 +0200, Xfennec wrote: > Is such a name is > available within Debian ? The good news is, the name "progress" as an executable is available in Debian. $ apt-file search progress | grep /bin debconf: /usr/bin/debconf-apt-progress fastdnaml: /usr/lib/fastdnaml/bin/dnaml_progress goto-fai-progress: /usr/bin/fai-progress kdesdk-scripts: /usr/bin/build-progress.sh pcl-tools: /usr/bin/pcl_progressive_morphological_filter videotrans: /usr/bin/movie-progress and there's no sbin named progress, as expected. So may I use *progress* as cv's *package name* and *excutable name* ? -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1432721780.3365.4.ca...@gmail.com
Bug#786968: RFS: python-snuggs/1.3.1-1 [ITP]
Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: pkg-grass-de...@lists.alioth.debian.org Dear mentors, I am looking for a sponsor for my package "python-snuggs" Package name: python-snuggs Version : 1.3.1-1 Upstream Author : Sean Gillies URL : https://github.com/mapbox/snuggs License : BSD-3 Section : python It builds those binary packages: python-snuggs - S-expressions for numpy - Python 2 version python3-snuggs - S-expressions for numpy - Python 3 version To access further information about this package, please visit the following URL: http://mentors.debian.net/package/python-snuggs Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/python-snuggs/python-snuggs_1.3.1-1.dsc More information about Snuggs can be obtained from https://github.com/mapbox/snuggs. Changes since the last upload: * Initial upload (closes: #783712) Regards, Johan Van de Wauw -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAJOp35nELjyr9EPKSwrqsfkoRVX3sGm1LV1ZzGQbDDg=adf...@mail.gmail.com
Bug#785426: RFS: cv/0.6-1 [ITP] -- cv - Coreutils (progress) Viewer)
> FWIW I think adding postfix for "cv" is much easier to accept > for Xfennec. The more I think about it, the more I like the command name "progress" for its simplicity, instead of tweaking the original name too much and making it impossible to remember for the users. Is such a name is available within Debian ? -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150527092736.27bff...@cqfd-corp.org
