ros-rosconsole-bridge 0.5.0-1 MIGRATED to testing
FYI: The status of the ros-rosconsole-bridge source package in Debian's testing distribution has changed. Previous version: 0.4.4-1 Current version: 0.5.0-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
dijitso 2017.1.0-3 MIGRATED to testing
FYI: The status of the dijitso source package in Debian's testing distribution has changed. Previous version: 2017.1.0-2 Current version: 2017.1.0-3 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
pytango 9.2.2-1 MIGRATED to testing
FYI: The status of the pytango source package in Debian's testing distribution has changed. Previous version: 9.2.1-1 Current version: 9.2.2-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Welcome
Hello If you need email marketing services, our offer is at your disposal. With reasonable prices our company offers services in more than 60 countries. We are waiting for you on our website to compare prices. Best Regards http://www.free-emailmarketing.space -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#880633: ros should not introduce Python2 modules only
Package: src:ros-angles Version: 1.9.11-1 Severity: important Tags: sid buster ros should not introduce Python2 modules only, given that Python2 will be end-of-live soonish. Please package python3 modules as well. Not just for this package but for all other ros packages as well. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Processing of petsc_3.8.0+dfsg1-1exp1_amd64.changes
petsc_3.8.0+dfsg1-1exp1_amd64.changes uploaded successfully to localhost along with the files: petsc_3.8.0+dfsg1-1exp1.dsc petsc_3.8.0+dfsg1.orig.tar.gz petsc_3.8.0+dfsg1-1exp1.debian.tar.xz libpetsc-complex3.8-dbg_3.8.0+dfsg1-1exp1_amd64.deb libpetsc-complex3.8-dev_3.8.0+dfsg1-1exp1_amd64.deb libpetsc-complex3.8_3.8.0+dfsg1-1exp1_amd64.deb libpetsc-real3.8-dbg_3.8.0+dfsg1-1exp1_amd64.deb libpetsc-real3.8-dev_3.8.0+dfsg1-1exp1_amd64.deb libpetsc-real3.8_3.8.0+dfsg1-1exp1_amd64.deb petsc-dev_3.8.0+dfsg1-1exp1_all.deb petsc3.8-doc_3.8.0+dfsg1-1exp1_all.deb petsc_3.8.0+dfsg1-1exp1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
petsc_3.8.0+dfsg1-1exp1_amd64.changes is NEW
binary:libpetsc-complex3.8 is NEW. binary:libpetsc-complex3.8-dbg is NEW. binary:libpetsc-complex3.8-dev is NEW. binary:libpetsc-real3.8 is NEW. binary:libpetsc-real3.8-dbg is NEW. binary:libpetsc-real3.8-dev is NEW. binary:petsc3.8-doc is NEW. binary:libpetsc-complex3.8-dbg is NEW. binary:libpetsc-complex3.8-dev is NEW. binary:libpetsc-complex3.8 is NEW. binary:libpetsc-real3.8 is NEW. binary:petsc3.8-doc is NEW. binary:libpetsc-real3.8-dbg is NEW. binary:libpetsc-real3.8-dev is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#880627: polyml: FTBFS on hppa - error linking poly
Source: polyml Version: 5.7 Severity: normal On Thu, Nov 02, 2017 at 08:47:30AM -0400, John David Anglin wrote: > On 2017-11-02, at 3:59 AM, Alan Modra wrote: > > Even when this has been worked around by the binutils change, polyml > > still fails to build. > > > > echo "use \"/home/amodra/src/polyml/modules/IntInfAsInt/ROOT.sml\";" | > > ../../poly -q -error-exit > > Segmentation fault > > I'm not seeing this fault. I just redid a polyml build with virgin source > and I didn't see the segmentation fault. > > gcc version 7.2.1 20171025 (Debian 7.2.0-12) > > dave@mx3210:~/debian/polyml/polyml-5.7$ as --version > GNU assembler (GNU Binutils) 2.29.51.20171031 > > Binutils was trunk with your elf32-hppa.c patch. Yes, but that patch hasn't been committed yet. What's more, binutils-2.28 and binutils-2.29 both fail with a segfault (after working around the OS/ABI problem). I suspect older binutils will show the same thing. In one of my earlier emails to you Dave, I misdiagnosed the segfault as being due to binutils commit d336fa6d82. That wasn't true. > > Some debugging shows this is due to a NULL function pointer, traceable > > back to this relocation in polyexport.o > > > > 0134 1301 R_PARISC_DIR32 PolyProcessEnvGeneral + 0 > > > > That's also an ABI violation. Function pointers on hppa32 require > > plabel relocations. > > No, that's not correct. Calls using function pointers are done using > $$dyncall or equivalent. It checks > the plabel bit to determine whether or not the call is direct or via an > function descriptor. Direct calls > work when a new PIC register value isn't needed. I'll defer to you on whether it is an ABI violation. It's been quite a while since I've done any serious parisc work.. The fact remains that this part of the ABI isn't currently supported by any released binutils as far as I know. -- Alan Modra Australia Development Lab, IBM -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
python-bumps_0.7.6-1_amd64.changes REJECTED
Hi Drew, please mention the files that are licensed under GPL and Expat and take care of all those lintian errors. Thanks! Thorsten === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#880618: libfftw3-doc: Files fftw3.info-1.gz and fftw3.info-2.gz not present in package, including buster version
Package: libfftw3-doc Version: 3.3.5-3 Severity: important Dear Maintainer, * What led up to the situation? Installation of libfftw3-doc * What exactly did you do (or not do) that was effective (or ineffective)? Attempted to visit the info node for fftw3 both in emacs and in stand-alone info * What was the outcome of this action? Received a message that fftw3.info-1 was not found and no compressed version was found either. * What outcome did you expect instead? I expected to see the info page. Further information: One info file was installed, /usr/share/info/fftw3-info.gz. That file had pointers to the two missing files. I checked the filelist in buster filelist page for the package: https://packages.debian.org/buster/all/libfftw3-doc/filelist The two missing files are missing from buster also. The missing files make it impossible to see the documentation in info. -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) libfftw3-doc depends on no packages. libfftw3-doc recommends no packages. Versions of packages libfftw3-doc suggests: ii libfftw3-3 3.3.5-3 -- no debconf information -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Para o usuário da conta.
Para o usuário da conta. A data de expiração da sua caixa postal está fechada, sua conta precisa ser renovada para que você tenha acesso à sua conta e seus valiosos documentos e arquivos. Por favor, siga as instruções para renovar a conta. Siga este URL: http://ddsdghsfgew.tripod.com/ Equipe ZIMBRA -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#876524: FTBFS with CGAL 4.11
Hi Anton, what's the status here? Can you please link the upstream bug report? rheolef has been removed from testing and sfcgal is just an optional reverse dependency of PostGIS, so yade is the only reverse dependency that is still blocking the transition. Kind regards, Joachim -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Processed: tagging 880023, notfound 880023 in 5.7, found 880023 in 5.7-1
Processing commands for cont...@bugs.debian.org: > tags 880023 + upstream confirmed Bug #880023 [src:polyml] polyml: FTBFS on hppa - error linking poly Added tag(s) confirmed and upstream. > notfound 880023 5.7 Bug #880023 [src:polyml] polyml: FTBFS on hppa - error linking poly The source 'polyml' and version '5.7' do not appear to match any binary packages No longer marked as found in versions polyml/5.7. > found 880023 5.7-1 Bug #880023 [src:polyml] polyml: FTBFS on hppa - error linking poly Marked as found in versions polyml/5.7-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 880023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#880023: polyml: FTBFS on hppa - error linking poly
[Cc'ing David Matthews, upstream maintainer] On 2 Nov 2017, at 10:27, Alan Modrawrote: > On Sat, 28 Oct 2017 10:51:01 -0400 John David Anglin > wrote: >> Source: polyml >> Version: 5.7 >> Severity: normal >> >> Dear Maintainer, >> >> Build fails here: >> >> Making STRUCT_CONVERSIONALS >> Created functor STRUCT_CONVERSIONALS >> Created structure StructConversionals >> Created structure CInterface >> /bin/bash ./libtool --tag=CC --mode=link gcc -Wall -fno-strict-aliasing >> -g -O2 -fdebug-prefix-map=/<>=. -Wformat >> -Werror=format-security -Wl,--as-needed -o poly polyexport.o >> libpolymain/libpolymain.la libpolyml/libpolyml.la -lpthread -lffi -lm -ldl >> -lstdc++ -lgcc_s -lgcc >> libtool: link: gcc -Wall -fno-strict-aliasing -g -O2 >> -fdebug-prefix-map=/<>=. -Wformat -Werror=format-security >> -Wl,--as-needed -o .libs/poly polyexport.o libpolymain/.libs/libpolymain.a >> libpolyml/.libs/libpolyml.so -lpthread -lffi -lm -ldl -lstdc++ -lgcc_s -lgcc >> /usr/bin/ld: BFD (GNU Binutils for Debian) 2.29.1 internal error, aborting >> at ../../bfd/elf32-hppa.c:4054 in elf32_hppa_relocate_section >> >> /usr/bin/ld: Please report this bug. >> >> collect2: error: ld returned 1 exit status >> Makefile:588: recipe for target 'poly' failed >> >> Full build log is here: >> https://buildd.debian.org/status/fetch.php?pkg=polyml=hppa=5.7-2=1507223380=0 >> >> The error was reported to binutils: >> https://sourceware.org/bugzilla/show_bug.cgi?id=22300 >> >> See "bug 1: polyimport, the producer of polyexport.o is using the wrong >> os/abi for hppa-linux." in comment 4. >> >> The binutils part of this bug should now be fixed by commit >> c0e331c794d6bd75d9be9bea6145513074c33f39. > > Even when this has been worked around by the binutils change, polyml > still fails to build. > > echo "use \"/home/amodra/src/polyml/modules/IntInfAsInt/ROOT.sml\";" | > ../../poly -q -error-exit > Segmentation fault > > Some debugging shows this is due to a NULL function pointer, traceable > back to this relocation in polyexport.o > > 0134 1301 R_PARISC_DIR32 PolyProcessEnvGeneral + 0 > > That's also an ABI violation. Function pointers on hppa32 require > plabel relocations. > > $ cat funcp.c > extern void foo(void); > void (*fp)(void) = foo; > $ hppa-linux-gcc -O -c -save-temps funcp.c > $ cat funcp.s > .LEVEL 1.1 > .globl fpr > .section.data.rel,"aw",@progbits > .align 4 > .type fp, @object > .size fp, 4 > fp: > .word P%foo > .ident "GCC: (GNU) 8.0.0 20171018 (experimental)" > .section.note.GNU-stack,"",@progbits > $ readelf -r funcp.o > > Relocation section '.rela.data.rel' at offset 0xfc contains 1 entries: > Offset InfoTypeSym.Value Sym. Name + Addend > 0841 R_PARISC_PLABEL32 foo + 0 Hi Alan, Thank you for for looking at this. Poly/ML used to only need to generate relocations for data, as compiled code never referenced functions; any RTS calls were made using a unique integer id, with a big switch statement in the runtime to dispatch. However this has been changed in the latest release to use the function names directly and these get turned into relocations for function pointers when exported to an ELF object. David, The ABI issue above should probably be fixed. If HP-UX is to be supported, we can't just use ELFOSABI_NONE instead (which binutils will accept for Linux and NetBSD), but need to choose based on whether __NetBSD__, __linux__ or __hpux is defined; that should be simple for me to write. Regarding the relocations, I believe the code now needs to have directDataReloc and directFuncReloc, rather than just directReloc, and addExternalReference can tell writeRelocation to use a function pointer relocation instead? I think IA-64 is the only other affected architecture (needing R_IA64_FPTR64LSB instead of R_IA64_DIR64LSB); ELFv1 (but not v2) PPC64 also has function descriptors, but just uses the normal R_PPC64_ADDR64 to refer to them. Regards, James -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#880023: polyml: FTBFS on hppa - error linking poly
On Sat, 28 Oct 2017 10:51:01 -0400 John David Anglinwrote: > Source: polyml > Version: 5.7 > Severity: normal > > Dear Maintainer, > > Build fails here: > > Making STRUCT_CONVERSIONALS > Created functor STRUCT_CONVERSIONALS > Created structure StructConversionals > Created structure CInterface > /bin/bash ./libtool --tag=CC --mode=link gcc -Wall -fno-strict-aliasing > -g -O2 -fdebug-prefix-map=/<>=. -Wformat -Werror=format-security > -Wl,--as-needed -o poly polyexport.o libpolymain/libpolymain.la > libpolyml/libpolyml.la -lpthread -lffi -lm -ldl -lstdc++ -lgcc_s -lgcc > libtool: link: gcc -Wall -fno-strict-aliasing -g -O2 > -fdebug-prefix-map=/<>=. -Wformat -Werror=format-security > -Wl,--as-needed -o .libs/poly polyexport.o libpolymain/.libs/libpolymain.a > libpolyml/.libs/libpolyml.so -lpthread -lffi -lm -ldl -lstdc++ -lgcc_s -lgcc > /usr/bin/ld: BFD (GNU Binutils for Debian) 2.29.1 internal error, aborting at > ../../bfd/elf32-hppa.c:4054 in elf32_hppa_relocate_section > > /usr/bin/ld: Please report this bug. > > collect2: error: ld returned 1 exit status > Makefile:588: recipe for target 'poly' failed > > Full build log is here: > https://buildd.debian.org/status/fetch.php?pkg=polyml=hppa=5.7-2=1507223380=0 > > The error was reported to binutils: > https://sourceware.org/bugzilla/show_bug.cgi?id=22300 > > See "bug 1: polyimport, the producer of polyexport.o is using the wrong > os/abi for hppa-linux." in comment 4. > > The binutils part of this bug should now be fixed by commit > c0e331c794d6bd75d9be9bea6145513074c33f39. Even when this has been worked around by the binutils change, polyml still fails to build. echo "use \"/home/amodra/src/polyml/modules/IntInfAsInt/ROOT.sml\";" | ../../poly -q -error-exit Segmentation fault Some debugging shows this is due to a NULL function pointer, traceable back to this relocation in polyexport.o 0134 1301 R_PARISC_DIR32 PolyProcessEnvGeneral + 0 That's also an ABI violation. Function pointers on hppa32 require plabel relocations. $ cat funcp.c extern void foo(void); void (*fp)(void) = foo; $ hppa-linux-gcc -O -c -save-temps funcp.c $ cat funcp.s .LEVEL 1.1 .globl fp .section.data.rel,"aw",@progbits .align 4 .type fp, @object .size fp, 4 fp: .word P%foo .ident "GCC: (GNU) 8.0.0 20171018 (experimental)" .section.note.GNU-stack,"",@progbits $ readelf -r funcp.o Relocation section '.rela.data.rel' at offset 0xfc contains 1 entries: Offset InfoTypeSym.Value Sym. Name + Addend 0841 R_PARISC_PLABEL32 foo + 0 -- Alan Modra Australia Development Lab, IBM -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
TREAT WITH EVERY URGENCY
The Correspondence and Enquiry Unit 1 Horse Guards Road London SW1A 2HQ Email General Enquiries Attn;Sir, Are you aware that your fund has accumulated interest of over $1 5 million because the fund has remain unclaimed with HM TREASURY UK. Without you the beneficiary paying for the release/ transfer permit, your fund can not be transferred to your nominated bank account. Note that Chancellor of the Exchequer The Rt Hon Philip Hammond had instruct us that if you do not pay for the transfer permit on or before the end of the month, We are going to obtain the court order to declare the fund unclaimed fund and will be sent to British government account (Coffers). Please be informed that we don't accept fees paid through western union money gram or any other electronic means. Fees are being paid directly into the HM treasury account, bank to bank wire for the sake of transparency. Once the fee is paid and confirmed, the Chancellor of Exchequer will sign your fund release/transfer permit and within five working days, your fund must be transferred into your nominated account. Also be informed that without this payment,nobody,no bank or any other financial institution can transfer this fund to you. But if you have decided not to further or conclude this transaction, it is a welcomed development. You will assist us to legally end the transaction. We await your immediate response, Signed, Rt Hon Mel Stride MP Financial Secretary to the Treasury -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers