Re: Uploaded package is not showing up in mentors

On 06/10/15 20:48, Petr Vorel wrote: > Hi there, > > I'm another one who experienced the problem of not being able to upload > package to > mentors.debian.net. I tried several times, wait few days... > > Build and sign package and upload it with > dput mentors

Bug#790412: RFS: circus/0.12.0-1

On 10/07/2015 08:13 PM, Andrey Rahmatullin wrote: > On Tue, Oct 06, 2015 at 03:32:35PM +0200, David Douard wrote: >> Hi Andrey >> >> I've just uploaded a new version of the package (circus_0.12.1+dfsg-1). >> As you can see, I've renamed it to add a +dfsg suffix as you requested. > I: circus

Bug#801295: RFS: tightvnc/1.3.9-6.6

Package: sponsorship-requests Version: any Hi, I've prepared a debdiff adding ppc64el support to tightvnc. The patch has been tested, and is already shipping in Ubuntu. As the package is up for adoption, a Debian developer is needed to do the NMU upload. For the history and the debdiff, see:

Bug#801295: RFS: tightvnc/1.3.9-6.6

Control: retitle -1 RFS: tightvnc/1.3.9-6.6 [NMU]

Re: Java problem when upgrading pixelmed

On 2015-10-08 13:28, Emmanuel Bourg wrote: It looks like you need the new standard Java API for JSON processing (JSR 353) [1], we haven't packaged it yet, but josm has a local copy (if you search for 'package javax.json' on http://source.debian.net you can quickly find the package containing

Re: Java problem when upgrading pixelmed

On Tue, Oct 06, 2015 at 10:36:56PM +0200, Emmanuel Bourg wrote: > Le 06/10/2015 22:28, Andreas Tille a écrit : > > > export JAVAVERSIONTARGETJARFILE=/usr/lib/jvm/default-java/jre/lib/rt.jar; > > javac -O -target 1.7 -source 1.7 -bootclasspath ${JAVAVERSIONTARGETJARFILE} > > -encoding "UTF8"

Re: Java problem when upgrading pixelmed

Le 08/10/2015 13:03, Andreas Tille a écrit : > I think you've won your bet ;-) *cheers* > The makefiles are refering to > >lib/additional/javax.json-api-1.0.jar > > and it seems none of the json java classes are fitting this. > > I remember times when the jar contents were listed in: >

Re: Java problem when upgrading pixelmed

Hi, On Thu, Oct 08, 2015 at 01:40:58PM +0200, Bas Couwenberg wrote: > On 2015-10-08 13:28, Emmanuel Bourg wrote: > >It looks like you need the new standard Java API for JSON processing > >(JSR 353) [1], we haven't packaged it yet, but josm has a local copy (if > >you search for 'package

Bug#785932: marked as done (RFS: sockjs-twisted/1.2.2-1 [ITP] -- Simple library for adding SockJS support to a twisted application)

Your message dated Thu, 08 Oct 2015 16:32:44 + with message-id and subject line closing RFS: sockjs-twisted/1.2.2-1 [ITP] -- Simple library for adding SockJS support to a twisted application has caused the Debian Bug report #785932, regarding RFS:

dev-pkg-without-shlib-symlink lintian warning for libtool library using -release & -version-info

To deal with the external usage of liblwgeom built from the postgis sources, the upstream developers now use the -release libtool option along with -version-info to better support installation of multiple postgis versions. The -release option was added to support the multiple version use case on

Re: Java problem when upgrading pixelmed

Le 08/10/2015 13:40, Bas Couwenberg a écrit : > Due to the difficulties getting JCS [0] and its dependencies [1] > packaged, I've not been able to update to any of the newer JOSM upstream > releases making the josm package increasingly irrelevant. And if I > remain unable to get JCS packaged,

Re: Uploaded package is not showing up in mentors

Hi Petr, > >Still not sure about it. please read: https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-changelog Actually it depends, an NMU is a "one shot" upload, where you fix a particular bug but you express not much interest in maintaining the package (e.g. an NMU can

Re: Java problem when upgrading pixelmed

Hi Emmanuel, On 09-10-15 00:05, Emmanuel Bourg wrote: > Le 08/10/2015 13:40, Bas Couwenberg a écrit : > >> Due to the difficulties getting JCS [0] and its dependencies [1] >> packaged, I've not been able to update to any of the newer JOSM upstream >> releases making the josm package increasingly

Re: Java problem when upgrading pixelmed

On 09-10-15 00:58, Emmanuel Bourg wrote: > Le 08/10/2015 13:40, Bas Couwenberg a écrit : > >> Due to the difficulties getting JCS [0] and its dependencies [1] >> packaged, I've not been able to update to any of the newer JOSM upstream >> releases making the josm package increasingly irrelevant.

Re: Java problem when upgrading pixelmed

Le 08/10/2015 13:40, Bas Couwenberg a écrit : > Due to the difficulties getting JCS [0] and its dependencies [1] > packaged, I've not been able to update to any of the newer JOSM upstream > releases making the josm package increasingly irrelevant. And if I > remain unable to get JCS packaged,

Re: Uploaded package is not showing up in mentors

Hi Danny, thank you a lot for your tips :-). > your package name contains "amd64", suggesting you tried to upload a > binary. Mentors is source-based, so it may have been silently rejected. > Please try building with > debuild -S Again unsuccessful upload, but this time at least source package

Re: Uploaded package is not showing up in mentors

Hi Danny, > Again unsuccessful upload, but this time at least source package upload :-). > I haven't received any mail from mentors.debian.net. I'm sorry, I wasn't right - I was successful this time. > I renamed package to freerdp_1.1.0~git20140921.1.440916e+dfsg1-5.1 (rom >

Bug#801213: RFS: python-privacyidea/2.7-1 [ITP]

I'm going to review this. Please expect the results, soon. Best, Daniel Stender -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/