Your message dated Thu, 15 Sep 2016 22:17:36 +0200
with message-id <849c1682-2989-91c9-51dd-26545be60...@debian.org>
and subject line Re: Bug#807432: RFS: python-jellyfish/0.5.1-1 [ITP]
has caused the Debian Bug report #807432,
regarding RFS: python-jellyfish/0.5.3-1 [ITP]
to be marked as done.
On Thursday, September 15, 2016 13:22:33 Jens Reyer wrote:
> On 15.09.2016 09:21, Shawn Sörbom wrote:
> > Hi
> > I have run into a few projects lately that don't include .desktop files
> > but
> > should. my usual approach to handle this is to write a patch with quilt
> > that writes a .desktop
Hello Boyuan,
On Wed, Sep 14, 2016 at 12:23:48PM +0800, Boyuan Yang wrote:
> Yes, they are up-to-date now. The package on debian-mentors is also
> updated.
Thanks. I'll get to this by Saturday at the latest.
--
Sean Whitton
signature.asc
Description: PGP signature
Hello Gianfranco,
>
> a ping when the other package is renamed and in testing even better.
>
I'm finally making effective the ping, as the long-standing naming
conflict has been solved on the latest "jellyfish" version (2.2.6-1) [1]
(which entered testing on 2016-09-06) by the renaming of its
Your message dated Thu, 15 Sep 2016 12:36:57 + (UTC)
with message-id <456593048.2899577.1473943017...@mail.yahoo.com>
and subject line Re: Bug#837912: RFS: engauge-digitizer/9.3-1
has caused the Debian Bug report #837912,
regarding RFS: engauge-digitizer/9.3-1
to be marked as done.
This means
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "engauge-digitizer"
* Package name: engauge-digitizer
Version : 9.3-1
Upstream Author : Mark Mitchell
* URL :
On 15.09.2016 09:21, Shawn Sörbom wrote:
> Hi
> I have run into a few projects lately that don't include .desktop files but
> should. my usual approach to handle this is to write a patch with quilt that
> writes a .desktop file to the project's root directory, then add a
> corresponding line to
Your message dated Thu, 15 Sep 2016 10:25:11 + (UTC)
with message-id <974971560.2734914.1473935111...@mail.yahoo.com>
and subject line Re: Bug#837899: RFS: dh-runit/1.6.2
has caused the Debian Bug report #837899,
regarding RFS: dh-runit/1.6.2
to be marked as done.
This means that you claim
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "dh-runit"
* Package name: dh-runit
Version : 1.6.2
Upstream Author : Dmitry Bogatov
* Url :
Forgot lintian
9)
I: libcgicc source: binary-control-field-duplicates-source field "section" in
package libcgicc5
I: libcgicc source: quilt-patch-missing-description
0002-Non-empty-html-index.patch
I: libcgicc source: quilt-patch-missing-description
003-no-old-style-config.patch
W: libcgicc5:
control: owner -1 !
control: tags -1 moreinfo
Hi,> * Non-maintainer upload.
changes are huge, but being half mia, and on lowNMU threshold...
(and too many bugs here, so lets do it)
> * New upstream release (closes: #833081, #811988, #798624, #645616).> *
> Updated to Standards-Version
Your message dated Thu, 15 Sep 2016 09:18:00 + (UTC)
with message-id <101469747.2616801.1473931080...@mail.yahoo.com>
and subject line Re: Bug#837887: RFS: xautolock/2.2-5.1 [NMU] [RC]
has caused the Debian Bug report #837887,
regarding RFS: xautolock/2.2-5.1 [NMU] [RC]
to be marked as done.
Your message dated Thu, 15 Sep 2016 09:16:43 + (UTC)
with message-id <1921559557.2635699.1473931003...@mail.yahoo.com>
and subject line Re: Bug#837886: RFS: lua-torch-trepl/0~20160613-g06128f9-1
[ITP]
has caused the Debian Bug report #837886,
regarding RFS:
Hi Ghislain,
>> your way is the best one if you also add a patch to automatically install
>> the file
>> inside the upstream build system.
>It would be better to send upstream a patch to include the .desktop
>file in their source tree and install it using their build system. If
>they
On 09/15/2016 10:02 AM, Ghislain Vaillant wrote:
> On 15/09/16 08:53, Gianfranco Costamagna wrote:
>>> I know this approach
>>> works, but is it the "right" way? Does it matter?
>>
>> your way is the best one if you also add a patch to automatically
>> install the file
>> inside the upstream
On Thu, Sep 15, 2016 at 3:21 PM, Shawn Sörbom wrote:
> I have run into a few projects lately that don't include .desktop files but
> should. my usual approach to handle this is to write a patch with quilt that
> writes a .desktop file to the project's root directory, then add a
> corresponding
On 15/09/16 08:53, Gianfranco Costamagna wrote:
Hi,
I know this approach
works, but is it the "right" way? Does it matter?
your way is the best one if you also add a patch to automatically install the
file
inside the upstream build system.
Otherwise you can avoid a patch and add the
Hi,
>I know this approach
>works, but is it the "right" way? Does it matter?
your way is the best one if you also add a patch to automatically install the
file
inside the upstream build system.
Otherwise you can avoid a patch and add the desktop file inside the debian
directory,
and ask
Package: sponsorship-requests
Severity: wishlist
Debomatic-amd64: passing
http://debomatic-amd64.debian.net/distribution#experimental/lua-torch-trepl/0~20160613-g06128f9-1/buildlog
Dear mentors,
I am looking for a sponsor for my package "lua-torch-trepl"
* Package name:
Package: sponsorship-requests
Severity: important
I'm looking for a sponsor for my NMU on xautolock
It closes an RC bug, I've validated that the the fix
doesn't break my machines.
The debdiff is attached
The package can be downloaded from -mentors
Hi
I have run into a few projects lately that don't include .desktop files but
should. my usual approach to handle this is to write a patch with quilt that
writes a .desktop file to the project's root directory, then add a
corresponding line to the debian/[package].install file. I know this
Sean Whitton wrote on Wed, Sep 14, 2016 at 07:40:00 -0700:
> On Wed, Sep 14, 2016 at 07:17:10AM -0700, Sean Whitton wrote:
> > I think that the current stable sbuild is meant to be able to build
> > for unstable (pretty common use case), so if you can reproduce it, a
> > stable update might be in
22 matches
Mail list logo