Your message dated Fri, 22 Mar 2013 06:29:33 +
with message-id <20130322062933.gb22...@master.debian.org>
and subject line RFS: spacefm/0.8.7-1 [ITP]
has caused the Debian Bug report #703395,
regarding RFS: spacefm/0.8.7-1 ITP
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 22 Mar 2013 06:27:39 +
with message-id <20130322062739.ga22...@master.debian.org>
and subject line RFS: rrep/1.3.6-1
has caused the Debian Bug report #703624,
regarding RFS: rrep/1.3.6-1
to be marked as done.
This means that you claim that the problem has been dealt wit
On Fri, Mar 22, 2013 at 6:28 AM, Arno Töll wrote:
> yes, the first one is enough though. This is not covered by docs,
> because that's a generic OpenGPG problem not specifically related to
> Debian (Mentors). You need to create a key satisfying the Debian keyring
> maintainers [1]. See any tutoria
On Fri, Mar 22, 2013 at 12:17 AM, Russ Allbery wrote:
> Which is why all shared libraries should use at least trivial symbol
> versioning that assigns all symbols a version that changes with the
> SONAME.
Perhaps a pedantic/info lintian complaint is in order?
--
bye,
pabs
http://wiki.debian.or
(sorry, initially sent this to the wnpp ticket)
Hi,
thanks a lot for packaging friendica! I was eager to try it out, so I got the
source package and built it on a Debian stable box (with some necessary jquery
packages from backports).
Here's some feedback that might be used to improve the pack
Hi Anton,
Thanks for the tip. I already handled a lot of warnings before the
first upload, and I'd like some advice about handling the rest of
them.
Starting from the source package:
- source-contains-prebuilt-binary:
I've read somewhere that this is not a reason for repackaging. What's
the proce
Hi,
On 21.03.2013 21:08, Felix Natter wrote:
> Do I have to follow (some of) these steps?
> http://wiki.debian.org/Keysigning
yes, the first one is enough though. This is not covered by docs,
because that's a generic OpenGPG problem not specifically related to
Debian (Mentors). You need to crea
hi,
I would like to publish a package to d-mentors for sponsorship soon, and
am wondering how to sign the source package for upload. Do I even need
to sign packages as a package maintainer (not DM, not DD)?
intro-maintainers writes this:
"How to upload packages to mentors.debian.net?
You nee
Hi,
please, have a look at the page of your package [1]. There are
a log of warnings, which need to be fixed. The lintian-checker produces
those warnings, if you start it over your .changes-file.
Cheers,
Anton
[1] http://mentors.debian.net/package/libaria
On 03/21/2013 04:34 PM, Srećko Jurić-K
Package: wnpp
Severity: wishlist
Owner: "gustavo panizzo "
Package: wnpp
Severity: wishlist
Owner: "gustavo panizzo "
* Package name: cloudfuse
Version : git20130124.809b07e
Upstream Author : Michael Barton
* URL : https://github.com/redbo/cloudfuse
* License
Your message dated Thu, 21 Mar 2013 16:23:34 +
with message-id
and subject line closing RFS: burp/1.3.26-1
has caused the Debian Bug report #700567,
regarding RFS: burp/1.3.26-1
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
Hi Bart,
Thank you for your reply.
On Thu, Mar 21, 2013 at 7:10 AM, Bart Martens wrote:
> I couldn't resist having a quick look now. :-) I suggest to ask
> debian-release
> for a pre-approval for wheezy with a debdiff including all three changes. So
> I
> suggest to keep the flag "needs spon
Your message dated Thu, 21 Mar 2013 16:23:29 +
with message-id
and subject line closing RFS: tilda/1.1.5-1 [ITA]
has caused the Debian Bug report #702072,
regarding RFS: tilda/1.1.5-1 [ITA]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Andrey Rahmatullin writes:
> If your app is linked against libavcodec53 and against libavdevice53 and
> libavdevice53 is linked against libavcodec54 and libavcodec* doesn't use
> symbol versioning, your app will crash because of symbol conflicts.
Which is why all shared libraries should use at l
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "libaria"
* Package name: libaria
Version : 2.7.5.2-1
Upstream Maintainer : Reed Hedges
* URL : http://robots.mobilerobots.com/wiki/ARIA
* Lice
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rrep"
* Package name: rrep
Version : 1.3.6-1
Upstream Author : Arno Onken
* URL : http://sourceforge.net/projects/rrep/
* License : GPL-3.0+
Section
On 03/18/2013 03:33 AM, Paul Wise wrote:
> On Sun, 2013-03-17 at 17:44 +0100, Arno Onken wrote:
>
>> I improved the watch file so that more extensions are found:
>> http://sf.net/rrep/rrep-(.+)\.(?:zip|tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz)))
>> Were you referring to that?
>
> I was also referring to
Control: retitle -1 RFS: ocamlrss/2.1.0-1 [ITP] -- RSS 2.0 parser and
printer for OCaml
Hi Paul,
> ocamlc:
>
> File "rss_date.ml", line 220, characters 10-280:
> Warning 25: bad style, all clauses in this pattern-matching are guarded.
> similarity-tester:
>
> rss_types.ml consists
Please ignore the mail below, I think I understand that part now.
libavdevice53 itself depends on libavcodec5{3|4} depending on where it
comes from.
Paul
On 21-03-13 08:04, Paul Gevers wrote:
> Hi Andrey,
>
> On 21-03-13 07:46, Andrey Rahmatullin wrote:
>> On Wed, Mar 20, 2013 at 07:17:50PM +01
On Thu, Mar 21, 2013 at 08:04:10AM +0100, Paul Gevers wrote:
> >>> Maybe I've picked the wrong example, the actual problem was with
> >>> libavdevice53, the same soname is used for either 0.8.5-1 and 9.3-1,
> >>> but 9.3-1 links to libavcodec54 while 0.8.5-1 links to libavcodec53, so
> >>> my binar
Hi Andrey,
On 21-03-13 07:46, Andrey Rahmatullin wrote:
> On Wed, Mar 20, 2013 at 07:17:50PM +0100, Paul Gevers wrote:
>>> Maybe I've picked the wrong example, the actual problem was with
>>> libavdevice53, the same soname is used for either 0.8.5-1 and 9.3-1,
>>> but 9.3-1 links to libavcodec54 w
21 matches
Mail list logo
