Package: sponsorship-requests
Severity: normal
Dear Maintainer,
I am looking for a sponsor for my package "fatx":
Package name: fatx
Version : 1.11-1
Upstream Author : Christophe Duverger
URL : http://sourceforge.net/projects/fatx
License : GPL v3
Section
control: tags -1 moreinfo
>I am looking for a sponsor for my package "fatx":
>http://sourceforge.net/projects/fatx
there is no source of a debian directory to look at.
we need the source, not the binary, and please upload it
on mentors.debian.net (where you can find a lot of documentation and
Hi,
I've uploaded it with dput on mentors.debian.net.
Regards,
CD
- Mail original -
De: "Gianfranco Costamagna"
À: "Christophe Duverger" , 830...@bugs.debian.org
Envoyé: Mardi 12 Juillet 2016 10:15:15
Objet: Re: Bug#830845: RFS: fatx/1.11-1 [ITP] -- Complete XBOX filesystem
support
c
Hi,
>I've uploaded it with dput on mentors.debian.net.
and it got rejected it seems
Hi,
in my last commit I tried to build cufflinks[1] against libboost 1.60
but failed. Since the failure does not seem to related to libboost I
wonder whether somebody might be able to understand and fix this issue:
...
In file included from /usr/include/eigen3/Eigen/Core:297:0,
> >In my view evil-paredit-el is ready to be uploaded, bar `dch -r`.
Sorry, was out-of-networking. Done 'debchange -r' and pushed as 8d9c4d3.
--
Accept: text/plain, text/x-diff
Accept-Language: eo,en,ru
X-Web-Site: sinsekvu.github.io
Your message dated Tue, 12 Jul 2016 10:29:33 + (UTC)
with message-id <1681591465.2516746.1468319373770.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#829208: RFS: evil-paredit-el/0.0.2-1 ITP
has caused the Debian Bug report #829208,
regarding RFS: evil-paredit-el/0.0.2-1 ITP
to be mark
Your message dated Tue, 12 Jul 2016 10:35:47 + (UTC)
with message-id <505318512.2547142.1468319747396.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#830827: RFS: wvstreams/4.6.1-9 [QA, RC]
has caused the Debian Bug report #830827,
regarding RFS: wvstreams/4.6.1-9 [QA, RC]
to be marked
* Andreas Tille , 2016-07-12, 11:12:
In file included from /usr/include/eigen3/Eigen/Core:297:0,
from /usr/include/eigen3/Eigen/Dense:1,
from abundances.h:21,
from abundances.cpp:16:
/usr/include/eigen3/Eigen/src/Core/DenseCoeffsBase.h: In instantia
Hi
>Ok - TL;DR; from stuff I was discussing with Paul Wise. Budgie-Desktop is
>definitely not Debian deb-helper friendly. With a standard v9 debhelper -
>even with a >override_autoreconf, override_autoreconfigure etc, it appears
>from first glance that the compilation works. However on insta
Hi,
>
>Aren't there different rationales for source and binary package names?
>This is what I have been thinking:
>
>- source package name should be upstream's name, because it's the
> *source*
>- binary package name is whatever makes most sense for someone typing
> apt-get
Indeed, I didn't lo
Hi Jakub,
On Tue, Jul 12, 2016 at 01:10:44PM +0200, Jakub Wilk wrote:
>
> For some reason Eigen thinks that v.colwise().sum() cannot be treated as a
> one-dimensional vector, which smells like a bug in Eigen. Changing the last
> line to
>
> m = v.colwise().sum()(0, 0);
>
> seems to do the
Yes, my public key is not found.
On which keyserver I have to upload it ?
I have sent it to p80.pool.sks-keyservers.net and keys.gnupg.net according to
"https://wiki.debian.org/Keysigning#Step_7:_Send_your_signed_key_to_the_server";
Regards,
CD
- Mail original -
De: "Gianfranco Costam
>AI have sent it to p80.pool.sks-keyservers.net and keys.gnupg.net according to
>"https://wiki.debian.org/Keysigning#Step_7:_Send_your_signed_key_to_the_server";
nope, you have to add it to your account IIRC
mentors.debian.org, login and add it.
G.
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "python-qtawesome"
* Package name: python-qtawesome
Version : 0.3.3-3
Upstream Author : The Spyder Development Team
* URL : https://github.com/spyder-ide/qtaweso
Thank's.
I've uploaded my public key on mentors.debian.net
dput refuses to re-upload my package (says that it's already done), so how can
I tell the system to reload my package ?
Regards,
CD
- Mail original -
De: "Gianfranco Costamagna"
À: "christophe duverger"
Cc: 830...@bugs.debian.
"dput -f"
Il Martedì 12 Luglio 2016 14:51, "christophe.duver...@free.fr"
ha scritto:
Thank's.
I've uploaded my public key on mentors.debian.net
dput refuses to re-upload my package (says that it's already done), so how can
I tell the system to reload my package ?
Regards,
CD
- Mail or
Your message dated Tue, 12 Jul 2016 12:56:56 + (UTC)
with message-id <1089617967.2696349.1468328216336.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#830870: RFS: python-qtawesome/0.3.3-3 [RC]
has caused the Debian Bug report #830870,
regarding RFS: python-qtawesome/0.3.3-3 [RC]
to be
It looks like my last email was not forwarded to the debian-mentors
mailing list. Since I am still looking for a sponsor, here it is:
Hi Jakub,
thanks for the review!
On Sat, Jul 09, 2016 at 08:33:21PM +0200, Jakub Wil
To access further information about this package, please visit the following
URL:
https://mentors.debian.net/package/fatx
Regards,
Christophe Duverger
- Mail original -
De: "Christophe Duverger"
À: "Debian Bug Tracking System"
Envoyé: Mardi 12 Juillet 2016 10:08:28
Objet: Bug#830845
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "pam-u2f"
* Package name: pam-u2f
Version : 1.0.4-0.1
Upstream Author : Yubico AG
* URL : https://developers.yubico.com/pam-u2f/
* License : BSD
Sect
Hi (please cc the bug)
>I removed it, but does it do any harm?
no, I guess not
>Might have something to do with -fPIE vs. -fPIC, but one would have to
>investigate further to be sure. This is definitely not a regression,
>though, since the z3 version currently in the archive has no hardening
>f
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "libu2f-server"
* Package name: libu2f-server
Version : 1.0.1-1.3
Upstream Author : [fill in name and email of upstream]
* URL : [fill in URL of upstreams web si
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "kismon"
* Package name: kismon
Version : 0.8.1-1
Upstream Author : Patrick Salecker
* URL : https://www.salecker.org/software/kismon.html
* License
Any reason why your .orig.tar is different than the one uscan downloads?
$ md5sum z3_4.4.1.orig.tar.gz*
94e21f86056f986c320653912be53f8a z3_4.4.1.orig.tar.gz
4336a9df24f090e711c6d42fd4e2b1fc z3_4.4.1.orig.tar.gz.github
* Fabian Wolff , 2016-07-10, 00:56:
* Install shared libraries into new li
Package: sponsorship-requests
Severity: normal
Dear mentors, Gianfranco,
I am looking for a sponsor for the package "skiboot". This is a packaging
update :
skiboot (5.2.4-1) unstable; urgency=medium
* New upstream release
* Disabled PIE build as this makes opal-prd segfault and there is
Hi people,
I am doing a QA (do not need a sponsor) and
packaging a more recent version of the app.
This new version has support for python3, as
said in setup.py, so I created debian/*.install
files and edited debian/control and debian/rules.
cat debian/rules:
#!/usr/bin/make -f
%:
dh $
Hello!
Some time ago I made gdbm_1.12-3 into experimental, and since it is
incompatible with
gdbm-1.8 (new soname, separated compat library) I rebuilt all reverse
depedencies.
Here is my report:
FAIL camldbm_1.0-2.dsc | PATCH
FAIL courier_0.73.1-1.6.dsc
FAIL freeradius_
Hi Herbert,
On 12 July 2016 at 16:46, Herbert Fortes wrote:
> This new version has support for python3, as
> said in setup.py, so I created debian/*.install
> files and edited debian/control and debian/rules.
What are the contents of "debian/*.install" files?
I have packaged a Python library wh
Your message dated Wed, 13 Jul 2016 04:26:41 +
with message-id
and subject line closing RFS: skiboot/5.2.4-1 update
has caused the Debian Bug report #830885,
regarding RFS: skiboot/5.2.4-1 update
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Wed, 13 Jul 2016 04:26:41 +
with message-id
and subject line closing RFS: setcolortemperature/1.3-1 ITP
has caused the Debian Bug report #829151,
regarding RFS: setcolortemperature/1.3-1 ITP
to be marked as done.
This means that you claim that the problem has been dealt wit
It looks as MBF, but I would like someone more experienced to give advice.
The transitions policy is here:
https://wiki.debian.org/Teams/ReleaseTeam/Transitions
We do not have automation
to rebuild packages and file FTBFS bugs, do we?
Automated whole-archive rebuilds have been done (see e.g.
32 matches
Mail list logo
