Your message dated Sun, 6 Dec 2015 00:59:28 +0000
with message-id <[email protected]>
and subject line Re: Bug#806773: RFS: normaliz/3.0.0+ds-3 [FTBFS fix]
has caused the Debian Bug report #806773,
regarding RFS: normaliz/3.0.0+ds-3 [FTBFS fix]
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 [email protected]
immediately.)
--
806773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806773
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
Dear Mentors:
I am looking for a sponsor for the package normaliz [1] that
I am maintaining on behalf of the Debian Science-Team.
This version fix the FTBFS issue #806769 that pointed random emitting
of `Bus error' from GOMP on mipsel architectures machines: OpenMP is
now disabled on mipsel architecture machines.
Thanks,
Jerome
[1] https://anonscm.debian.org/cgit/debian-science/packages/normaliz.git
-- System Information:
Debian Release: Jessie*
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.7-ckt11-amd64-mbp62 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
On Sun, Dec 06, 2015 at 01:38:40AM +0100, Jerome BENOIT wrote:
> No reason at all, or clumsyness if any: I post something here:
>
> https://wiki.debian.org/DebianPureBlends/SoB
*shrugs* let me upload it, guess I should edit that table, I'll let you
do it, since I have really no clue about what should be done.
mattia@chase ~/devel/RFS/normaliz % dput normaliz_3.0.0+ds-3_source.changes
Uploading normaliz using ftp to ftp-master (host: ftp.upload.debian.org;
directory: /pub/UploadQueue/)
running allowed-distribution: check whether a local profile permits uploads to
the target distribution
running protected-distribution: warn before uploading to distributions where a
special policy applies
running checksum: verify checksums before uploading
running suite-mismatch: check the target distribution for common errors
running gpg: check GnuPG signatures before the upload
gpg: Signature made Sun 06 Dec 2015 12:44:16 AM UTC using RSA key ID B9444540
Uploading normaliz_3.0.0+ds-3.dsc
Uploading normaliz_3.0.0+ds-3.debian.tar.xz
Uploading normaliz_3.0.0+ds-3_source.changes
mattia@chase ~/devel/RFS/normaliz %
> >> [1] https://anonscm.debian.org/cgit/debian-science/packages/normaliz.git
> >
> > The commits on that repository looks weird: almost like you do the work,
> > build a .dsc, and then import it to the git repo :S
>
> Let say that I am getting more and more familiar with the packaging process
> which is not that complex but ask time to get a good overwhole picture and
> practice.
> May be my habit to use quilt is becoming obsolete.
>
> Having said that, I hope that my packages are not that bad.
The packaging itself looks good, is just the way the git commits are
made that makes me itch :)
BTW, a couple of points about the headers of the patches:
* some patches have 'This is a Debian centric patch.' in the
description. The DEP-3 way to say that is 'Forwarded: not-needed'
* also in the Origin field instead of "the upstream team" it's usually
more useful to put a URL of the commit
and FWIW, I do use raw quilt to handle my patches too :)
I don't really feel confortable with git-based patch management (like
`git-dpm` of `gbp pq`)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
--- End Message ---
