Hi Dear,

Hi Dear, how are you today I hope that everything is OK with you as it is my great pleasure to contact you in having communication with you starting from today, i was just going through the Internet search when i found your email address, I want to make a very new and special friend, so i

debian-science-maintainers@lists.alioth.debian.org - Tienes una factura sin pagar!

Tienes una factura sin pagar Generado el: 12/12/2017 Factura #3389790 Descarga la factura con el enlace

Bug#884256: pysph: please make the build reproducible

Source: pysph Version: 0~20160514.git91867dc-4 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: kernel X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Hi, Whilst working on the Reproducible Builds effort [0], we noticed that pysph could not be

Bug#883987: rheolef: FTBFS error: partial specialization ... after instantiation ...

Hi Graham, > Would you please quote the bug number? I failed to find your bug report. Here is the bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884185 Hummm... I just realize now that I have do a mistake and assign this bug to libcgal-dev instead of libboost-dev package

Bug#883987: rheolef: FTBFS error: partial specialization ... after instantiation ...

On 2017-12-12 20:26, Graham Inggs wrote: > Would you please quote the bug number? I failed to find your bug report. > > I think the thing to do here is reassign this bug to src:boost1.62 and > mark that it affects src:rheolef. just saw these (against cgal) in my buster RC udd query: #884184

Bug#883987: rheolef: FTBFS error: partial specialization ... after instantiation ...

Hi Pierre (cc-ing Andreas in case he is not subscribed) On 12 December 2017 at 15:13, Pierre Saramito wrote: > Hi Andreas, > > This problem do neither comes from Rheolef-6.7 nor from CGAL-4.11: > it comes from Boost-1.62 combined with g++ 7.2 in Debian sid and testing.

ignition-cmake_0.2.0-1_amd64.changes is NEW

binary:libignition-cmake-dev is NEW. binary:libignition-cmake-dev is NEW. source:ignition-cmake 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

arpack++_2.3-8_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Dec 2017 19:42:46 +0100 Source: arpack++ Binary: libarpack++2-dev libarpack++2c2a Architecture: source Version: 2.3-8 Distribution: unstable Urgency: medium Maintainer: Debian Science Team

Processing of arpack++_2.3-8_source.changes

arpack++_2.3-8_source.changes uploaded successfully to localhost along with the files: arpack++_2.3-8.dsc arpack++_2.3-8.debian.tar.xz arpack++_2.3-8_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- debian-science-maintainers mailing list

Processing of ignition-cmake_0.2.0-1_amd64.changes

ignition-cmake_0.2.0-1_amd64.changes uploaded successfully to localhost along with the files: ignition-cmake_0.2.0-1.dsc ignition-cmake_0.2.0.orig.tar.bz2 ignition-cmake_0.2.0-1.debian.tar.xz ignition-cmake_0.2.0-1_amd64.buildinfo libignition-cmake-dev_0.2.0-1_amd64.deb Greetings,

Re: ngspice: Remove build dependency on elyxer to allow for the elyxer removal from Debian

Hi Gudjon, On Mon, Dec 11, 2017 at 06:58:10AM +0100, Gudjon I. Gudjonsson wrote: > I'm terribly sorry for having missed the bug. > There is a new version in SVN (27) that is not fully prepared but will > be in the next few days. If somebody is willing to sponsor it I will be > very happy. > >

Bug#883987: rheolef: FTBFS error: partial specialization ... after instantiation ...

Hi Andreas, This problem do neither comes from Rheolef-6.7 nor from CGAL-4.11: it comes from Boost-1.62 combined with g++ 7.2 in Debian sid and testing. The bug has already be identified in the upstream version of Boost : https://svn.boost.org/trac10/ticket/12534 and it is now fixed in the

Business Discussion Request

Good day, Thank you for taking the time. I am Angela Liu, I got your contact via Linkedin. Would it be convenient for you to be available for a proposition discussion? I look forward to hearing from you at your convenience. -- Best Regards, Ms Angela Liu Head of Operations Standard

My dear greetings to you,

My dear greetings to you,   I crave your indulgence at this mail coming from somebody you have not known before. I decided to do this after praying over the situation. You should please consider the transaction on its content and not the fact that you have not known me before. I need not dwell