Processed: block 683969 with 499159
Processing commands for cont...@bugs.debian.org: > block 683969 with 499159 Bug #683969 [curl] curl: Build using --with-libmetalink 683969 was not blocked by any bugs. 683969 was not blocking any bugs. Added blocking bug(s) of 683969: 531095 and 499159 > thanks Stopping processing here. Please contact me if you need assistance. -- 683969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.1344242927388.transcr...@bugs.debian.org
Bug#660141: Update Regarding php-mongo
Hi there, I'm looking to work with php-mongo in Debian - and actually require to build a package ASAP. Is there any progress on either of your packages? If not, I'm happy to look @ sponsoring the upload of these ? Otherwise, I intend to hijack the ITP. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cakdqwudpeh-dy-uxcmtdby2tpobcvz+aa9yxkugi6hn8+xs...@mail.gmail.com
Bug#683746: rspamd packaging
Laszlo, On 08/05/2012 10:46 AM, Laszlo Boszormenyi (GCS) wrote: > On Sat, 2012-08-04 at 23:53 +0400, Vsevolod Stakhov wrote: >> Thanks for taking care of it! I'm using this package for my machines, >> but I'm not very familiar with debian packaging policies unfortunately. > Hmmm, do you really want to learn and package it? Learning is always > good, I don't want to hijack it from you. Well, I've fixed all issues you pointed and committed them to rspamd mercurial repository. I think I'll release 0.5.1 version soon and the package would be for it, not for 0.5.0. >> It's strange as rspamd is built with -fpic -fPIC flags if they are >> supported on the targeted architecture. How can I repeat this bug using >> my debian system? > Sure, I've seen that you use -fpic and -fPIC as well for compilation. > The patch I've sent to you contains everything. Just uncomment the > export DEB_BUILD_MAINT_OPTIONS=hardening=+all > line in debian/rules . I think one of your source files might not be > compiled with the PIC flags and that's the problem. Well, I've tried the same on my ubuntu dev box and cannot repeat this issue. Can you please try it again with modified package? >> Library is only used for rspamd client (rspamc), so maybe it would be >> better to link it statically for debian package? I think a development >> package is only useful when there is any external software that uses the >> normal package's API. > I do agree with your lines. Either make the binary statically linked > and without the header file or consider the package split. Do you intend > to use plug-ins or whatever external to spamc? There's no problem if > nobody else will use the separated library, but it'll be rejected from > the official archives if you keep it as-is. Ok, I've liked rspamc statically with that library and skip installing it during deb build. >> Acknowledged. So on upgrades of this package I should only inlcude lines >> like 'Update to version x.x.x', rigth? > Sure, 'initial release', 'new upstream release', 'fixed compilation on > 64 bit machines' or anything related to the packaging itself is OK. The > code related ones like 'added IPv6 support', 'many bugfixes', 'rework > events system' and 'write plugin for ...' are not. The latter ones can > go to toplevel_dir/ChangeLog with a date and version number added. I've fixed that as well. Thought FreeBSD port system is more tolerative in this aspect affording addition of the upstream changelog to a port's changelog, so why I thought that debian/changelog should be the same. -- Vsevolod Stakhov -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/501fb8ed.8010...@highsecure.ru
Bug#684039: ITP: prime-phylo -- Bayesian estimation of gene trees taking the species tree into account
Package: wnpp Severity: wishlist Owner: Erik Sjölund * Package name : prime-phylo Version : 1.0.3 Upstream Author : Lars Arvestad, Bengt Sennblad and others * URL : http://prime.sbc.su.se * License : GPL-3 Programming Lang: C++ Description: Bayesian estimation of gene trees taking the species tree into account PrIME (Probabilistic Integrated Models of Evolution) is a package supporting inference of evolutionary parameters in a Bayesian framework using MCMC. A distinguishing feature of PrIME is that the species tree is taken into account when analyzing gene trees. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cab+1q0rstmzm29d_igu+pztvbuonxj8+jzbwskp3tnmedsv...@mail.gmail.com
Bug#684053: ITP: lightdm-kde -- a LightDM greeter using KDE libraries
Package: wnpp Severity: wishlist Owner: Ralf Jung * Package name: lightdm-kde Version : 0.2.1 Upstream Author : David Edmundson * URL : https://projects.kde.org/projects/playground/base/lightdm * License : GPL Programming Lang: C++ Description : a LightDM greeter using KDE libraries -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120806144451.22550.24717.reportbug@r-schlepptop
Bug#611660: ITP: tomb -- crypto undertaker
Hi, Any news on this? I see there is a debian/ directory in the upstream repo (btw, a dedicated branch for Debian packaging is a better option). Is peer-review needed? bert. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120806154305.GE27892@localhost
Bug#660141: Update Regarding php-mongo
Hi Martin, On Mon, 2012-08-06 at 13:03 +0100, Martin Meredith wrote: > I'm looking to work with php-mongo in Debian - and actually require to > build a package ASAP. > > Is there any progress on either of your packages? If not, I'm happy > to look @ sponsoring the upload of these ? I've a package, ready to upload[1]. Please check if it meets DFSG and other rules. > Otherwise, I intend to hijack the ITP. Please don't. If the package meets your needs, I'll upload it. Regards, Laszlo/GCS [1] dget -ux http://www.barcikacomp.hu/gcs/php-mongo_1.2.12-1.dsc -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1344277027.7759.202.camel@julia
Bug#611660: tomb vs cryptmount
Hi, Without too much reading, it seems tomb and cryptmount somewhat similar. The latter is already in the archives and stable. What's the most important differences (if any)? Laszlo/GCS -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1344277481.7759.205.camel@julia
Bug#660141: Update Regarding php-mongo
Hi Laszlo - I can't find you in db.debian.org - and from the way you've been talking about this package - I'm presuming you won't actually have rights to upload. Can you please push your package onto mentors.debian.net - it'll help me with doing some basic packaging checks, rather than having to do them all manually. That done - I'll have a look over the package tomorrow. Any questions - feel free to email me back or harass me on IRC (Mez) On Mon, Aug 6, 2012 at 7:17 PM, Laszlo Boszormenyi (GCS) wrote: > Hi Martin, > > On Mon, 2012-08-06 at 13:03 +0100, Martin Meredith wrote: >> I'm looking to work with php-mongo in Debian - and actually require to >> build a package ASAP. >> >> Is there any progress on either of your packages? If not, I'm happy >> to look @ sponsoring the upload of these ? > I've a package, ready to upload[1]. Please check if it meets DFSG and > other rules. > >> Otherwise, I intend to hijack the ITP. > Please don't. If the package meets your needs, I'll upload it. > > Regards, > Laszlo/GCS > [1] dget -ux http://www.barcikacomp.hu/gcs/php-mongo_1.2.12-1.dsc > -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKDqwUe4W2tuYHyfSNyDxvQmDrEn03A+6-=pjdgac252h8m...@mail.gmail.com
Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org: > # Monday 6 August 20:03:11 UTC 2012 > # Tagging as pending bugs that are closed by packages in NEW > # http://ftp-master.debian.org/new.html > # > # Source package in NEW: libdist-checkconflicts-perl > tags 609025 + pending Bug #609025 [wnpp] RFP: libdist-checkconflicts-perl -- Perl module to declare version conflicts Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 609025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13442834015538.transcr...@bugs.debian.org
Processed: severity of 555213 is normal, reassign 555213 to wnpp ..., owner 555213
Processing commands for cont...@bugs.debian.org: > severity 555213 normal Bug #555213 [bmon] bmon: Should this package be orphaned (or removed)? Severity set to 'normal' from 'important' > reassign 555213 wnpp Bug #555213 [bmon] bmon: Should this package be orphaned (or removed)? Bug reassigned from package 'bmon' to 'wnpp'. No longer marked as found in versions bmon/2.0.1-3. Ignoring request to alter fixed versions of bug #555213 to the same values previously set > retitle 555213 ITA: bmon -- portable bandwidth monitor and rate estimator Bug #555213 [wnpp] bmon: Should this package be orphaned (or removed)? Changed Bug title to 'ITA: bmon -- portable bandwidth monitor and rate estimator' from 'bmon: Should this package be orphaned (or removed)?' > owner 555213 ! Bug #555213 [wnpp] ITA: bmon -- portable bandwidth monitor and rate estimator Owner recorded as Philipp Kern . > thanks Stopping processing here. Please contact me if you need assistance. -- 555213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.134428603418160.transcr...@bugs.debian.org
Bug#684093: ITP: libgtk2-appindicator-perl -- Perl bindings for libappindicator
Package: wnpp Severity: wishlist Owner: "Andrew Starr-Bochicchio" * Package name : libgtk2-appindicator-perl Version : 0.14 Upstream Author : Hans Oesterholt URL : https://launchpad.net/libgtk2-appindicator-perl/ License : Artistic, LGPL-2+ Programming Lang: Perl Description : Perl bindings for libappindicator Gtk2::AppIndicator provides an interface to Unity's libappindicator for GTK2 Perl programs. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120806205738.14376.22349.reportbug@localhost6.localdomain6
Bug#595106: Faenza Icon Theme
I have also been looking into polishing the package from the PPA. FWIW, I found the following Google Code site for the Faenza Icon Theme, which holds a download option for "source tarballs" containing the SVGs: http://code.google.com/p/faenza-icon-theme/downloads/list I think ideally debian/rules should really generate the PNGs from the latest faenza-sources_*.tar.gz tarball found there. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1344287247.5358.38.camel@razor
Bug#627362: [jitsi-dev] Re: Git for jitsi, native Debian package?
Hey Micha, On Sun, Aug 5, 2012 at 12:27 PM, Micha Lenk wrote: > Hi Emil, > > by looking for free software alternatives for Skype available on Debian, I got > aware of jitsi, which seems to have an awesome feature set. As it is not > available in the official Debian archive, I looked around and found out about > the recent efforts to package it for Debian (namely Debian bug #627362). > > On Tue, Nov 22, 2011 at 04:58:34PM +0100, Emil Ivov wrote: >> On Tue, Nov 22, 2011 at 4:09 PM, Thomas Koch wrote: >> > In any case, there are some things that Jitsi should/could/must do itself >> > to >> > make a native package for Debian/Fedora/OpenSuse doable. I've opened jira >> > issues for those and linked them from an umbrella issue: >> > >> > http://java.net/jira/browse/JITSI-996 >> >> Ouch ... that's something that we like to avoid [0]. >> >> We only enter issues once we've determined exactly what they are and >> decided that we'll be fixing them at some point. I've closed the >> issues and we'll reopen those that we agree on, if and when we do. >> Right now we are still in the discussion stages of the debian >> packaging. We'd first need to decide exactly what needs to be resolved >> here and how we can do that. >> [...] >> >> > We can continue to discuss the items separately in those issues. > > Okay, so, let's list all the issues that Thomas reported already, here again. > For one to make them more visible, and also to get a consensus about the > status > of these issues. Thanks for bringing them up! > Not using an issue tracker will of course make it harder to > keep track of the actual conclusions. But as you wanted to have it this way, > of course I expect that you will then give your opinion on them one by one, > more with regards to content than with regards the way we report issues. We will of course open issues for those that we accept as such but that can't happen until we've discussed them. We realize this is frustrating but the alternative of simply dumping them in our tracker would lead to ... well ... nothing. We may change our issue tracking policy in the future, but right now, this is the only one we can afford. Again, apologies for any inconvenience this may have caused, and many thanks for bringing them here! Now before, I continue, I've already mentioned in a couple of threads that we are currently working on a debian tarball. This does imply a lot of work since we need to come up with the generating scripts, determine what libraries we can use as debian dependencies, implement support for such dependencies (they won't work out of the box for OSGi), retrieve the source code for the rest of the libs we use, upload them to our libsrc, and make sure that they are properly build by the Jitsi build process. Hopefully, we would have all this by the end of the summer, early autumn. Again, it is a lot of effort, but we realize how important it would be for the project to get into Debian. Another debian developer, Raphael Hertzog (CCed), will be guiding us through the process and helping us where necessary. Of course we'd be more than happy to also have you on board. > - > > JITSI-995 document (or manage) native dependencies (by Thomas Koch) > > There's no central location where one can see which C libraries of what > version, origin and license Jitsi uses, which of them are patched, in what > way > and for what reason. This is exactly what the libsrc directory is for. We are still working on filling it up and we should be done by the time we finish our debian source tarball. Also note that all the patches we have used to patch native libs are currently in src/native > I'm not a C developer so I don't know if there's something like Maven/Ivy > for > C that manages dependencies? > > - > > JITSI-994 Use Ivy or Maven to manage java dependencies (by Thomas Koch) > > It is hard for a distro (Debian/Fedora/Suse) packager to find out which java > dependencies Jitsi has. A pom.xml or ivy.xml would make things much easier > and then the dependencies could also be removed from SVN. Same as above: our libsrc should resolve this. > - > > JITSI-993 get rid of json.org java dependency (by Thomas Koch) > > The json.org java library is non-free according to Debian and maybe also > other distros. It kind of appears so indeed. Although the thread below does also show rough consensus on the fact that it is unlikely for the statement to be a problem in a court of law. Still we do understand precautionary measures. > As long as jitsi depends on json.org it can not enter the > Debian archive. Right. Luckily, json.org is used for a particularly non-centric feature in Jitsi (creating ippi.com accounts). We'll have a quick look for alternatives and use one if it
Bug#660141: Update Regarding php-mongo
Hi Martin, On Mon, 2012-08-06 at 19:38 +0100, Martin Meredith wrote: > Hi Laszlo - I can't find you in db.debian.org Please don't make me unknown to Debian. I'm a DD[1] since 2005-01-19, also an application manager[2]. When I search about myself[3] and type 'gcs' as login, I can find myself. Have some packages[4] in the archive. If you check the signatures on my GnuPG keys (ie A51A4FDD and BBAA47C9), you can see that I know other DDs in person like Steve Langasek, Stefano Zacchiroli, Tom Marble, Bdale Garbee or Enrico Zini. Also some RedHat employees, but that's the other side. > and from the way > you've been talking about this package - I'm presuming you won't > actually have rights to upload. Quoting myself: "If the package meets your needs, I'll upload it.". Where do you read that I don't have rights to upload? > Can you please push your package onto mentors.debian.net - it'll help > me with doing some basic packaging checks, rather than having to do > them all manually. That sound strange for me. Never trust an external source in things that you can check yourself. A pbuilder chroot can make sure that build-dependencies are correct, you can check d/*, etc. Please upload the package to mentors by yourself if you still want to go that way. I didn't want to be harsh, sorry if this mail sounds like that. Regards, Laszlo/GCS [1] https://nm.debian.org/public/person/gcs [2] https://nm.debian.org/public/managers [3] https://db.debian.org/ [4] http://qa.debian.org/developer.php?login=g...@debian.hu signature.asc Description: This is a digitally signed message part
Bug#684098: ITP: libinline-java-perl -- write Perl classes in Java
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard * Package name: libinline-java-perl Version : 0.53 Upstream Author : Patrick LeBoutillier * URL : http://search.cpan.org/dist/Inline-Java/ * License : Artistic or GPL-1+ Programming Lang: Perl Description : write Perl classes in Java Inline::Java lets you write Perl classes in Java. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120806221100.15160.24375.report...@auryn.jones.dk
Bug#683791: ITP: calypso -- CalDAV and CardDav server
Joseph Nahmias writes: > Package: wnpp > Severity: wishlist > Owner: Joseph Nahmias > > * Package name: calypso > Version : 0.5 > Upstream Author : Keith Packard > * URL : http://keithp.com/blogs/calypso/ > * License : GPL3+ > Programming Lang: Python > Description : CalDAV and CardDav server > > The Calypso Project is a CalDAV calendar server. It aims to be a light > solution, easy to use, easy to install, easy to configure. As a > consequence, it requires few software dependances and is pre-configured > to work out-of-the-box. If you put packaging bits together, I can integrate them into the calypso repository and just upload each time I do a release. Would save you time, and I already do this for a couple of other packages. -- keith.pack...@intel.com pgp4OnIb7EvyB.pgp Description: PGP signature
Processed: igtf-policy-bundle: block ITP 666229 by RFS 684102
Processing commands for cont...@bugs.debian.org: > block 666229 by 684102 Bug #666229 [wnpp] ITP: igtf-policy-bundle -- IGTF profiles for Authority Root Certificates 666229 was not blocked by any bugs. 666229 was not blocking any bugs. Added blocking bug(s) of 666229: 684102 > stop Stopping processing here. Please contact me if you need assistance. -- 666229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.134431321219551.transcr...@bugs.debian.org
