Bug#815213: ITP: puppet-module-sbitio-monit -- Puppet module for Monit
Package: wnpp Severity: wishlist Owner: Thomas Goirand * Package name: puppet-module-sbitio-monit Version : 1.0.0 Upstream Author : Jonathan Araña Cruz * URL : https://github.com/sbitio/puppet-monit * License : Mit Programming Lang: Ruby, Puppet Description : Puppet module for Monit Puppet lets you centrally manage every important aspect of your system using a cross-platform specification language that manages all the separate elements normally aggregated in different files, like users, cron jobs, and hosts, along with obviously discrete elements like packages, services, and files. . Performs installation and configuration of Monit service, along with fine grained definition of checks. . All check types provided by Monit are supported. Namely: directory, fifo, file, filesystem, host, process, program, and system. . In adition to primitive types, a compound check type is provided: service. It is a set of primitives to check a service's init script, binary and process. . service check type can work with sysv, systemd or upstart. In 0.3.x series it defaults to sysv for compatibility reasons. From 1.0.x onwards it defaults to the init system that each supported OS configures by default. The init type to use can be also set per service. See below for details.
Bug#814296: marked as done (ITP: puppet-module-jbussdieker-monit -- Puppet module for installing configuring and running processes using monit)
Your message dated Sat, 20 Feb 2016 14:21:55 +0800 with message-id <56c80603.8030...@debian.org> and subject line Not possible to package has caused the Debian Bug report #814296, regarding ITP: puppet-module-jbussdieker-monit -- Puppet module for installing configuring and running processes using monit 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 now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 814296: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814296 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Thomas Goirand * Package name: puppet-module-jbussdieker-monit Version : 1.5.0 Upstream Author : Joshua B. Bussdieker * URL : https://github.com/jbussdieker/puppet-monit * License : Unkown yet (currently clarifying with upstream) Programming Lang: Ruby, Puppet Description : Puppet module for installing configuring and running processes using monit Puppet lets you centrally manage every important aspect of your system using a cross-platform specification language that manages all the separate elements normally aggregated in different files, like users, cron jobs, and hosts, along with obviously discrete elements like packages, services, and files. . This module manages installing, configuring and running processes using monit. --- End Message --- --- Begin Message --- There's no clear license defined by upstream, and attempting to fix the situation by contacting the author didn't work. Therefore, it can't be packaged. Closing this bug. Cheers, Thomas Goirand (zigo)--- End Message ---
Processed: fcitx-imlist: block ITP 815165 by RFS 815177
Processing commands for cont...@bugs.debian.org: > block 815165 by 815177 Bug #815165 [wnpp] ITP: fcitx-imlist -- Command-line utility to switch list of Fcitx IM 815165 was not blocked by any bugs. 815165 was not blocking any bugs. Added blocking bug(s) of 815165: 815177 > stop Stopping processing here. Please contact me if you need assistance. -- 815165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#660304: uploaded
Hi, Daniel. On Fri, Feb 19, 2016 at 7:18 AM, Daniel Pocock wrote: > I've made an upload of this package today. > > It is in the debian-science repository. Thanks a lot for the upload and the update, Daniel! Not only for r-can-tm but also for all the other r-cran-* packages that I just saw on the NEW queue of ftpmaster! Thanks once again, -- Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
Bug#813562: Test suite failure
Thanks for your help. Output order is due to multiprocessing. That nailed it. tesseract 3.04.01 changed its output when asked to determine page orientation. It's an improved, but it breaks parsing. I will throw together a patch to make the appropriate distinctions. $ tess-3.04.01 -psm 0 tests/resources/linn-west.jpg stdout Page number: 0 Orientation in degrees: 270 Rotate: 90 Orientation confidence: 29.34 Script: Latin Script confidence: 45.33 $ tess-3.04.00 -psm 0 tests/resources/linn-west.jpg stdout Orientation: 3 Orientation in degrees: 90 Orientation confidence: 29.34 Script: 1 Script confidence: 45.33 On Fri, Feb 19, 2016 at 16:28 Sean Whitton wrote: > Hello, > > On Fri, Feb 19, 2016 at 10:45:51PM +, James R Barlow wrote: > > In any case, could you try running this: > > ocrmypdf --rotate-pages tests/resources/cardinal.pdf out.pdf > > > > In cardinal.pdf the same page is rotated in each cardinal direction. > out.pdf > > should have all pages facing up. Is this the case? The output will also > give > > information on rotation status: > > INFO - 1: page is facing ⇧, confidence 18.69 > > INFO - 3: page is facing ⇩, confidence 21.86 - correcting rotation > > INFO - 4: page is facing ⇦, confidence 20.71 - correcting rotation > > INFO - 2: page is facing ⇨, confidence 21.63 - correcting rotation > > INFO - 3: rotating image layer 180 degrees > > INFO - 2: rotating image layer 90 degrees > > INFO - 4: rotating image layer 270 degrees > > No, it gets it wrong. Result attached, and the output: > > , > | root@artemis:/build/ocrmypdf-4.0.1# ocrmypdf --rotate-pages > tests/resources/cardinal.pdf out.pdf > | INFO -1: page is facing ⇧, confidence 18.69 > | INFO -2: page is facing ⇦, confidence 21.63 - correcting rotation > | INFO -3: page is facing ⇩, confidence 21.86 - correcting rotation > | INFO -4: page is facing ⇨, confidence 20.71 - correcting rotation > | INFO -2: rotating image layer 270 degrees > | INFO -3: rotating image layer 180 degrees > | INFO -4: rotating image layer 90 degrees > ` > > (note that the order it processes the pages in is different to your > example) > > > It would also help to try in python3: > > > > >>> import ocrmypdf.leptonica as lp > > >>> lp.getLeptonicaVersion() > > > > ...to see if there's anything unusual about how debian sid is reporting > the > > leptonica version. > > , > | root@artemis:/build/ocrmypdf-4.0.1# cd /usr/lib/python3/dist-packages > | root@artemis:/usr/lib/python3/dist-packages# python3 > | Python 3.5.1+ (default, Jan 13 2016, 15:09:18) > | [GCC 5.3.1 20160101] on linux > | Type "help", "copyright", "credits" or "license" for more information. > | >>> import ocrmypdf.leptonica as lp > | >>> lp.getLeptonicaVersion() > | 'leptonica-1.73' > ` > > -- > Sean Whitton >
Bug#801253: how to handle not much used feature which depends on a deprecated technology
Hi, thanks toogley for trying to tackle this issue. Paul Wise wrote: > On Sat, Feb 20, 2016 at 3:28 AM, toogley wrote: > > what do you think about that? Am i missing sth? > > I would go with 1) or 3) add support for systemd-logind and whatever > other options there are for people who don't like systemd (ConsoleKit2 > etc) and send that to upstream. Indeed, thanks Paul for that comment. wicd seems the most popular alternative to NetworkManager for those who dislike NetworkManager's hard dependency on libpam-systemd and hence systemd. So to add an exclusive hard dependency on anything systemd-ish would probably annoy a not so small part of wicd's user base in Debian and should be avoided. Making use of systemd features if systemd is installed, is though welcome. This means that according configuration files should be shipped, but wicd should not solely rely on them -- as it seems to have happened with consolekit in the past. Regards, Axel -- ,''`. | Axel Beckert , http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#815199: ITP: acme-tiny -- letsencrypt tiny python client
Package: wnpp Severity: wishlist Owner: "Jeremías Casteglione" * Package name: acme-tiny Version : 20151229 Upstream Author : Daniel Roesler * URL : https://github.com/diafygi/acme-tiny * License : MIT Programming Lang: Python Description : letsencrypt tiny python client acme-tiny is a tiny script to issue and renew TLS certs from Let's Encrypt This is a tiny, auditable script that you can throw on your server to issue and renew Let's Encrypt certificates. Since it has to be run on your server and have access to your private Let's Encrypt account key, I tried to make it as tiny as possible (currently less than 200 lines). The only prerequisites are python and openssl. You have to deal yourself wiht the openssl stuff, and with webserver configuration and such. But it doesn't require more dependencies than openssl and it just works, no need for sudo nor being root to run it either. I'm using it for my personal TLS stuff. I'm not a DD nor a DM either, so an sponsor will be needed.
Bug#801253: how to handle not much used feature which depends on a deprecated technology
On Sat, Feb 20, 2016 at 3:28 AM, toogley wrote: > what do you think about that? Am i missing sth? I would go with 1) or 3) add support for systemd-logind and whatever other options there are for people who don't like systemd (ConsoleKit2 etc) and send that to upstream. -- bye, pabs https://wiki.debian.org/PaulWise
Bug#813562: Test suite failure
I ran into a similar failure because leptonica 1.71 has an integer overflow bug in the function pixCorrelationBinary which I use only in the test suite to check if some output PDFs visually resemble an expected reference PDF. I rewrote that function in Python for the older versions. The relevant code is ocrmypdf.leptonica.Pix.correlation_binary. I added a test that only exercises pixCorrelationBinary (test_monochrome_correlation), and this one passed. I checked that the tests can pass in the Docker version (they are slightly broken for an unrelated reason), which is debian stretch which has leptonica 1.73 (good version) and the same set of libraries as yours. The one difference is tesseract 3.04.01 vs .00, but I compiled the tesseract 3.04.01 and found that made no difference. In any case, could you try running this: ocrmypdf --rotate-pages tests/resources/cardinal.pdf out.pdf In cardinal.pdf the same page is rotated in each cardinal direction. out.pdf should have all pages facing up. Is this the case? The output will also give information on rotation status: INFO - 1: page is facing ⇧, confidence 18.69 INFO - 3: page is facing ⇩, confidence 21.86 - correcting rotation INFO - 4: page is facing ⇦, confidence 20.71 - correcting rotation INFO - 2: page is facing ⇨, confidence 21.63 - correcting rotation INFO - 3: rotating image layer 180 degrees INFO - 2: rotating image layer 90 degrees INFO - 4: rotating image layer 270 degrees That would help establish whether something is actually wrong or the test case is somehow at fault. It would also help to try in python3: >>> import ocrmypdf.leptonica as lp >>> lp.getLeptonicaVersion() ...to see if there's anything unusual about how debian sid is reporting the leptonica version. On Fri, 19 Feb 2016 at 12:04 Sean Whitton wrote: > Hello, > > On Fri, Feb 19, 2016 at 07:11:32AM +, James R Barlow wrote: > > What version of leptonica is installed? > > tesseract --version will report this. > > From within my Sid chroot: > > root@artemis:/build/ocrmypdf-4.0.1# tesseract --version > tesseract 3.04.01 > leptonica-1.73 > libgif 5.1.2 : libjpeg 6b (libjpeg-turbo 1.4.2) : libpng 1.2.54 : > libtiff 4.0.6 : zlib 1.2.8 : libwebp 0.4.4 : libopenjp2 2.1.0 > > > Also what's the file name for liblept? > > The Debian liblept package provides: > > /usr/lib/liblept.so.5 > /usr/lib/liblept.so.5.0.0 > > -- > Sean Whitton >
Bug#332498: RFH: openssl -- Secure Socket Layer (SSL) binary and related cryptographic tools
On Thu, Feb 18, 2016 at 04:19:27PM +0100, William Bonnet wrote: > Hi Kurt > > I am really interested in helping on this package. > > Do you still need some help ? If yes please let me know. It is about > one year without comments on this bug. Maybe you have found some > people ? But it is still open :) > > You can get in touch with me either through the BT, or directly by > email or irc _william_. So we can define how to help I'm always looking for help, in any way you want to help. You can also talk to me on IRC with the nick Q_. Kurt
Bug#815196: ITP: awlsim -- S7 compatible soft-PLC
Package: wnpp Severity: wishlist Owner: "Michael Büsch" * Package name: awlsim Version : 0.44? Upstream Author : Michael Buesch * URL : http://bues.ch/h/awlsim * License : GPLv2+ Programming Lang: Python Description : S7 compatible soft-PLC Awlsim is a soft-PLC (see https://en.wikipedia.org/wiki/Programmable_logic_controller) that can execute STEP7 (see German https://de.wikipedia.org/wiki/STEP_7) compatible AWL/STL code. I plan to maintain the Debian package by myself. The upstream repository, also maintained by me, already contains some basic Debian packaging scripts. (see http://bues.ch/gitweb?p=awlsim.git;a=tree)
Bug#813562: Test suite failure
Hello, On Fri, Feb 19, 2016 at 07:11:32AM +, James R Barlow wrote: > What version of leptonica is installed? > tesseract --version will report this. From within my Sid chroot: root@artemis:/build/ocrmypdf-4.0.1# tesseract --version tesseract 3.04.01 leptonica-1.73 libgif 5.1.2 : libjpeg 6b (libjpeg-turbo 1.4.2) : libpng 1.2.54 : libtiff 4.0.6 : zlib 1.2.8 : libwebp 0.4.4 : libopenjp2 2.1.0 > Also what's the file name for liblept? The Debian liblept package provides: /usr/lib/liblept.so.5 /usr/lib/liblept.so.5.0.0 -- Sean Whitton signature.asc Description: PGP signature
Bug#801253: how to handle not much used feature which depends on a deprecated technology
Hey. i want to fix this https://lintian.debian.org/tags/dbus-policy-at-console.html report in the wicd package. the concerning lines in the wicd source dir are (https://anonscm.debian.org/cgit/collab-maint/wicd.git/tree/other/wicd.conf) -- -- the situation is this: the above feature is depending on consolekit, which is not actively maintained. Consolekit was, according to the git history of d/control never a dependency of wicd (at least in debian). I don't have much evidence on this, but i doubt this feature was much consciously used. I mean, neither the manpages of wicd, nor anything else than the actual code are mentioning this feature. At least i didn't found anything else. And generally, that block is not very "beautiful" in my eyes, beacause it changes the behavior of wicd in relation of consolekit - without notifying the user about that. So basically, i think i have 2 options: 1) remove that block in debian completely and ask upstream to do the same. 2) because of the lintian warning and the obsolescence of consolekit, converting that part to systemd-logind and send that to upstream. what do you think about that? Am i missing sth?
Bug#753012: ITP: vagrant-libvirt -- Vagrant provider for libvirt
Hi, Antonio Terceiro wrote (19 Feb 2016 12:48:29 GMT) : > On Wed, Feb 17, 2016 at 07:18:58PM +0100, intrigeri wrote: >> It would be awesome if this could be uploaded within the next few >> weeks or months [...] > by all means, please go ahead. Woohoo, this is encouraging, thanks :) I can certainly do the initial upload. But I can't reasonably commit to maintain these two packages on the long term; besides, not being a Ruby guy, I'm concerned that just staying on top of current pkg-ruby-extras best practices would add some overhead on my side that I'd rather skip. So I'd rather not be listed in the Uploaders field. What I can do, though, is use the packages daily, on my personal systems (sid) and on the Tails infrastructure (generally Debian stable), file as good bug reports as I can, and send you folks pull requests whenever I can do that without leaving my comfort zone too much. So, who wants to be commit to maintain the package (== be listed in the Uploaders field)? Antonio and/or Miguel? Anyone else? Another option (that I like less, but well) could be that I try to maintain the package as long as it's easy, and I shout and ask for help whenever it gets harder / more Ruby -specific. > when you have code to create the boxes, would you please add them to > http://anonscm.debian.org/cgit/cloud/debian-vm-templates.git/ ? > (feel free to send me patches if you don't want to go through the hoops to > obtaining write access etc) I'll check with anonym how we do boxes, and we'll see if/how it applies to Debian cloud images. > or does it use the virtualbox boxes the way they are? I think we can either trivially convert a VirtualBox box with qemu-img, or build a dedicated one e.g. with vmdebootstrap. Cheers! -- intrigeri
Processed: ITP: r-cran-glmnet - Lasso and Elastic-Net Regularized Generalized Linear Models
Processing commands for cont...@bugs.debian.org: > owner 815128 Daniel Pocock Bug #815128 [wnpp] ITP: r-cran-glmnet - Lasso and Elastic-Net Regularized Generalized Linear Models Owner recorded as Daniel Pocock . > stop Stopping processing here. Please contact me if you need assistance. -- 815128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: ITP: r-cran-nlp - Natural Language Processing Infrastructure
Processing commands for cont...@bugs.debian.org: > owner 815129 Daniel Pocock Bug #815129 [wnpp] ITP: r-cran-nlp - Natural Language Processing Infrastructure Owner recorded as Daniel Pocock . > stop Stopping processing here. Please contact me if you need assistance. -- 815129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: ITP: r-cran-lubridate - Make Dealing with Dates a Little Easier
Processing commands for cont...@bugs.debian.org: > owner 815130 Daniel Pocock Bug #815130 [wnpp] ITP: r-cran-lubridate - Make Dealing with Dates a Little Easier Owner recorded as Daniel Pocock . > stop Stopping processing here. Please contact me if you need assistance. -- 815130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: ITP: r-cran-arm
Processing commands for cont...@bugs.debian.org: > owner 815127 Daniel Pocock Bug #815127 [wnpp] ITP: r-cran-arm Owner recorded as Daniel Pocock . > stop Stopping processing here. Please contact me if you need assistance. -- 815127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#815165: ITP: fcitx-imlist -- Command-line utility to switch list of Fcitx IM
Package: wnpp Severity: wishlist Owner: HAYASHI Kentaro X-Debbugs-CC: debian-de...@lists.debian.org, debian-de...@lists.debian.or.jp Package name: fcitx-imlist Version: 0.5.0 Upstream Author: HAYASHI Kentaro URL: https://github.com/kenhys/fcitx-imlist License: GPL-2+ Description: Command-line utility to switch list of Fcitx IM fcitx-imlist is a small program to show or change input method list. . This software is useful for the people who switch keyboard layout frequently - sometimes use equipped keyboard of mobile PC, sometimes use different layout of external keyboard with that PC. -- HAYASHI Kentaro -- HAYASHI Kentaro
Bug#800771: ITP: telegram-purple -- Adds support for Telegram to libpurple
Since there's somewhere a guideline saying that we should sometimes post updates: In the RFS thread it seemed to me that "dh get-orig-tar" is highly desirable. This delays it a bit. Also, worked on 1.3.0 (far from ready, improved build system) and 1.2.5 (released). - Translation is coming along nicely, but we still desparately need Russion and Brazilian translators: https://www.transifex.com/telegram-purple-developers/telegram-purple/ For 1.3.0, this will go horribly bad, and we will have to reduce the number of translations. Sorry, but if nobody updates translations we have to remove them. This is NOT a call for help, just a "report". Cheers, Ben Wiederhake
Bug#753012: ITP: vagrant-libvirt -- Vagrant provider for libvirt
On Wed, Feb 17, 2016 at 07:18:58PM +0100, intrigeri wrote: > Hi Miguel, Antonio and others, > > Miguel Landaeta wrote (14 Aug 2015 20:10:32 GMT) : > > On Thu, Aug 13, 2015 at 03:52:11PM +0200, intrigeri wrote: > >> It would not be reasonable of me to add these packages to my plate, > >> but perhaps the pkg-ruby-extras team could? > > > Awesome, if nobody beats me to it I could take a look at them and > > upload them soon. > > Excellent! > > I wanted to move this forward a bit, so I've merged Antonio's previous > work into mine (we had Git history without any common ancestor), and > then updated both packages to the latest upstream release. > > The current state of my work can be found there: > > https://git-tails.immerda.ch/intrigeri/ruby-fog-libvirt/ > https://git-tails.immerda.ch/intrigeri/vagrant-libvirt/ > > The resulting binary packages have seen a bit of manual testing, > conducted by my Tails team-mate anonym (Cc'ed). I assume he'll be > happy to go on testing preliminary packages if needed :) > > It would be awesome if this could be uploaded within the next few > weeks or months (we'll likely need this for working on making Tails > builds reproducible soonish, and in any case getting rid of our > dependency on VirtualBox would make the life of some of our developers > easier). by all means, please go ahead. when you have code to create the boxes, would you please add them to http://anonscm.debian.org/cgit/cloud/debian-vm-templates.git/ ? (feel free to send me patches if you don't want to go through the hoops to obtaining write access etc) or does it use the virtualbox boxes the way they are? > Antonio: for vagrant-libvirt, it seems that you haven't pushed your > upstream and pristine-tar branches, nor the upstream/0.0.31 tag, while > you pushed the corresponding changes in the master branch. And for > ruby-fog-libvirt, it seems that you haven't pushed the upstream/0.0.2 > tag. Can you please push the missing bits? Thanks in advance! argh, sorry about that. just did it. signature.asc Description: PGP signature
Bug#799281: [Mailman-Developers] Let's try to package mailman3 in Debian!
Le lundi 14 décembre 2015 à 17:01:57+0100, Pierre-Elliott Bécue a écrit : > Le lundi 23 novembre 2015 à 02:56:27+0100, Pierre-Elliott Bécue a écrit : > > Le vendredi 11 septembre 2015 à 00:49:44+0200, Pierre-Elliott Bécue a écrit > > : > > > [packaging mailman3] > > > > Hey, > > > > Here is an update. > > > > For now on, I focused on mailman3-core package in order to get good > > practices working. > > > > One can find my work here : https://github.com/P-EB/mailman3-core > > > > I'm working on having working systemd/sysv services and after that it'll be > > a good idea to try installing the package and see how it goes. > > > > I also have to design a good config file for debian, (see > > debian/contrib/mailman.cfg in master branch). Any suggestion is welcome! > > > > Cheers > > Small bump here, I'd appreciate if somebody finds the time to tell me two > things: > > * Is my config file enough for a start ? > * Is my systemd service good to have mailman started properly ? > > I'd rather be sure it's okay before writing a sysv service. > > You can find contrib files in debian/contrib. Hello! Before requesting for sponsorship, and packaging officially the other components of mailman3, I'd like some "testers" for the core package I built, in order to be sure that it works, and that I will not introduce some stupid caveats on the packaging of the other components. .deb can be found here: http://peb.pimeys.fr/mailman/mailman3-core/ git repo can be found there: https://gitlab.pimeys.fr/PEB/mailman3-core and there: https://github.com/P-EB/mailman3-core Any volunteer welcome! Please, I need your help, I cannot review my work alone! :) -- PEB
Bug#712159: non-free upload
It appears these license terms are suitable for the non-free section though, so I've uploaded the package there. I would discourage people from using this for any new projects. It is used in the examples in the O'Reilly book Machine Learning for Hackers so it is useful to make it available for people trying to follow those examples.
Processed: title
Processing commands for cont...@bugs.debian.org: > retitle 660304 ITP: r-cran-tm -- GNU R package for text mining Bug #660304 [wnpp] RFP: r-cran-tm -- GNU R package for text mining applications Changed Bug title to 'ITP: r-cran-tm -- GNU R package for text mining' from 'RFP: r-cran-tm -- GNU R package for text mining applications' > End of message, stopping processing here. Please contact me if you need assistance. -- 660304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): changes
Processing commands for cont...@bugs.debian.org: > unarchive 712159 Bug #712159 {Done: pa...@sifflez.org} [wnpp] ITP: r-cran-rjsonio -- GNU R package "RJSONIO: Serialize R objects to JSON" Unarchived Bug 712159 > reopen 712159 Bug #712159 {Done: pa...@sifflez.org} [wnpp] ITP: r-cran-rjsonio -- GNU R package "RJSONIO: Serialize R objects to JSON" Bug reopened Ignoring request to alter fixed versions of bug #712159 to the same values previously set > owner 712159 dan...@pocock.pro Bug #712159 [wnpp] ITP: r-cran-rjsonio -- GNU R package "RJSONIO: Serialize R objects to JSON" Owner changed from Pablo Oliveira to dan...@pocock.pro. > title 660304 ITP: r-cran-tm -- GNU R package for text mining Unknown command or malformed arguments to command. > owner 660304 dan...@pocock.pro Bug #660304 [wnpp] RFP: r-cran-tm -- GNU R package for text mining applications Owner recorded as dan...@pocock.pro. > End of message, stopping processing here. Please contact me if you need assistance. -- 660304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660304 712159: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712159 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#814352: ITP: veracrypt -- Cross-platform on-the-fly encryption
Hi Francesco, On Do 18 Feb 2016 23:36:48 CET, Francesco Poli wrote: On Thu, 18 Feb 2016 05:02:37 + Mike Gabriel wrote: On Mi 17 Feb 2016 21:49:54 CET, Francesco Poli wrote: [...] > Please send the updated debian/copyright file... > Oh, I must have forgotten to attach that file. Here it comes. Well, the so-called VeraCrypt License is just the TrueCrypt License version 3.0 + the Apache License version 2.0. Since both licenses apply, the situation is not really different from the one we have discussed in the previous messages of this thread... Bye. Thanks for your time and expertise on this again. I really appreciate having such a skilled licensing export on the Debian project. Let's see how the ftpmasters decide on my veracrypt upload, then. Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%40das-netzwerkteam.de pgp2nu0eWU4Jv.pgp Description: Digitale PGP-Signatur