Bug#701962: Updates and packaging repository.
Hi: Meanwhile, I've set up a repository with latest packaging stuff [0] I hope to be able to upload a debian package at mentors.debian.net Regards, [0] http://trismegisto.no-ip.org/hg/libsodium-debian -- Raúl Sánchez Siles ->Proud Debian user<- Linux registered user #416098 signature.asc Description: This is a digitally signed message part.
Processed: block 691978 with 473213
Processing commands for cont...@bugs.debian.org: > block 691978 with 473213 Bug #691978 [wnpp] RFP: bigbluebutton -- Open Source Web Conferencing 691978 was not blocked by any bugs. 691978 was not blocking any bugs. Added blocking bug(s) of 691978: 473213 > thanks Stopping processing here. Please contact me if you need assistance. -- 691978: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691978 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.13850312842817.transcr...@bugs.debian.org
Bug#728797: ITP: python-mne -- Python modules for MEG and EEG data analysis
Hi Alexandre, On Thu, Nov 21, 2013 at 05:40:44PM +0100, Alexandre Gramfort wrote: > > enough. > > gramfort@tsilinuxd74> git import-orig --pristine-tar > ../mne-python_0.7rc1.orig.tar.gz In my first mail about the RC candidate I suggested the version mne-python_0.7~rc1.orig.tar.gz (please mind the '~'). I'm not sure whether git supports this character in its tags but please note that this is important for the following reason: $ if dpkg --compare-versions 0.7~rc1 gt 0.6 ; then echo "0.7~rc1 is greater than 0.6"; fi 0.7~rc1 is greater than 0.6 $ if dpkg --compare-versions 0.7~rc1 gt 0.7 ; then echo "0.7~rc1 is greater than 0.7"; else echo "FAILURE: 0.7~rc1 is NOT GREATER than 0.7"; fi FAILURE: 0.7~rc1 is NOT GREATER than 0.7 $ if dpkg --compare-versions 0.7rc1 gt 0.7 ; then echo "0.7rc1 is greater than 0.7"; else echo "FAILURE: 0.7rc1 is NOT GREATER than 0.7"; fi 0.7rc1 is greater than 0.7 So we need to make sure that dpkg considers your release candidate a smaller version than the final release and thus we need to use 0.7~rc1 ... at least for the Debian packaging. This could be ironed out in d/watch by using dversionmangle - but as long as there is no final upload and we are targeting at 0.7 for the first upload anyway there is no point in beeing to picky. Just to let you know why I'm using 0.7~rc1 below! > ~/work/src/debian/mne-python > What is the upstream version? [0.7rc1] > gbp:info: Importing '../mne-python_0.7rc1.orig.tar.gz' to branch 'upstream'... > gbp:info: Source package is mne-python > gbp:info: Upstream version is 0.7rc1 > gbp:error: Couldn't commit to 'pristine-tar' with upstream 'upstream': > Execution failed: [Errno 2] No such file or directory > gbp:error: Import of ../mne-python_0.7rc1.orig.tar.gz failed Hmmm, besides the fact that I did renamed the tarball to mne-python_0.7~rc1.orig.tar.gz this worked for me. Did you verified that the file you try to import really exists? > what should be my upstream repo? The tarball simply needs to exist - no real magic otherwise. Worked for me like a charm. > I just used: > > gbp-clone ssh://git.debian.org/git/debian-med/mne-python.git > > should : > > ssh://git.debian.org/git/debian-med/mne-python.git > > be my upstream and master? If you used gbp-clone above you should get (master) $ git branch * master pristine-tar upstream This is the usual git-buildpackage layout we are using in Debian Med team. > >> > When trying this I realised that for running the tests the Build-Depends > >> > python-coverage was missing. > >> > >> I added now : > >> > >> python-coverage > > > > I thought I would have commited this to the repository I was talking > > about (git://git.debian.org/git/debian-med/mne-python.git). > > does it mean I need to have a debian branch on github that is > the master on debian.org? As I tried to make clear in our initial conversation the repository on git.debian.org and your upstream repository on github are not really interconnected via Git. We simply import some tarball by fully ignoring that it is originated from some Git repository. It is simply a tarball and we are (as a consequence) ignoring all the history inbetween the released tarballs. As I told you there are pros and cons of this method but this generic way has proven to work nicely in the past. In short: If I'm talking about "the" Git repository I always mean ssh://git.debian.org/git/debian-med/mne-python.git > send me a private message to find a way to chat if it's easier/faster. If needed you can reach me via jabber at til...@gmail.com . Another chance would be IRC at OFTC channel #debian-med - but I have no access to IRC on business hours and you need to ping me in advance if you want to IRC with me. In any case I have imported 0.7~rc1 and pushed the changes. Please pull and have a look. I tried to be verbose in commit logs. In any case you should enhance the long description. A minimum text would be what you injected in the ITP bug #728797 - a bit more would be nice. You get this kind of information when you call lintian -i -I __.changes Feel free to continue bothering us with questions if something remains unclear. Kind regards Andreas. -- http://fam-tille.de -- 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/20131121220639.gn7...@an3as.eu
Bug#730128: ITP: libwebsitesnapshot-qt -- A library for taking website snapshots.
Package: wnpp Severity: wishlist Owner: Alex Solanos * Package name: libwebsitesnapshot-qt Version : 1.03 Upstream Author : Alex Solanos * URL : https://launchpad.net/libwebsitesnapshot * License : LGPL 2.1 Programming Lang: C++ Description : A library for taking website snapshots. -- 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/20131121190629.2361.63516.reportbug@MaD-pc
Bug#705826: marked as done (O: libconstantine-java -- platform constants for Java)
Your message dated Thu, 21 Nov 2013 15:19:02 + with message-id and subject line Bug#705826: fixed in libconstantine-java 0.7-5 has caused the Debian Bug report #705826, regarding O: libconstantine-java -- platform constants for Java 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.) -- 705826: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: normal I hereby orphan the libconstantine-java package. This package provides Java values for common platform C constants like those of files errno.h or sys/socket.h. . The upstream version of this package is now also known as jnr-constants. -- Nicolas Duboc signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: libconstantine-java Source-Version: 0.7-5 We believe that the bug you reported is fixed in the latest version of libconstantine-java, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 705...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated libconstantine-java package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 21 Nov 2013 14:35:16 +0100 Source: libconstantine-java Binary: libconstantine-java libconstantine-java-doc Architecture: source all Version: 0.7-5 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers Changed-By: Sylvestre Ledru Description: libconstantine-java - platform constants for Java libconstantine-java-doc - Java Constantine library API documentation Closes: 698487 705826 Changes: libconstantine-java (0.7-5) unstable; urgency=low . * Adopt the package under the pkg-java umbrella (Closes: #705826) * Standards-Version updated to 3.9.5 * Import in the pkg-java VCS * Switch to dpkg-source 3.0 (quilt) format * add OSGi metadata to constantine.jar manifest Thanks to Jakub Adam (Closes: #698487) Checksums-Sha1: c5dbbbe5c385ad9747c8c4e60723c355c5a3e4ec 1490 libconstantine-java_0.7-5.dsc 9275c416c6d872de842a610322bbef692a69f6c6 3362 libconstantine-java_0.7-5.debian.tar.gz 737b3009d6172941e8042d8688fcfa4652330ded 231444 libconstantine-java_0.7-5_all.deb 69c997a0ca8f193cb62341505b7de129112f6201 143046 libconstantine-java-doc_0.7-5_all.deb Checksums-Sha256: 8208ab4d46da738a67be1caef76e78ec2af38f912a354c98c0f071ac7317c907 1490 libconstantine-java_0.7-5.dsc e697ae0066364a39ec7d039354270468fe5f7159e84a0f330c0dceead1e4dece 3362 libconstantine-java_0.7-5.debian.tar.gz c3072e625e195bb2507c61b4b8d1107da8fc52a35235b9bcaf6235897c95c861 231444 libconstantine-java_0.7-5_all.deb 5535400727cc6755d026d68a4410f477a1f2b6236b2264e85195a7a579ad2daa 143046 libconstantine-java-doc_0.7-5_all.deb Files: 535282fa5b84cf17c444782ca6b10e2f 1490 java optional libconstantine-java_0.7-5.dsc 0c6649beb1646e621f643dea8f933ca3 3362 java optional libconstantine-java_0.7-5.debian.tar.gz 3ecaedabfe03288001a542c237acdfd0 231444 java optional libconstantine-java_0.7-5_all.deb 636fcc1e46836fcbe1c1c0cc3eb94c3f 143046 doc optional libconstantine-java-doc_0.7-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iEYEARECAAYFAlKOEIUACgkQiOXXM92JlhBorACfWdcljVaNQAkilucO3tOoejIL Q+MAn3HlsJMdqN8ag8qJdc2B1xD9WsiF =YX4T -END PGP SIGNATURE End Message ---
Bug#728797: ITP: python-mne -- Python modules for MEG and EEG data analysis
Hi Alexandre, On Wed, Nov 20, 2013 at 11:20:10PM +0100, Alexandre Gramfort wrote: > are the services back online? Yep - since yesterday evening. That's a good timing. ;-) > we were thinking about releasing next tuesday and were hoping > to have proper debian packaging then. > thanks again for all your help. You might like to try: gbp-clone ssh://git.debian.org/git/debian-med/mne-python.git to check out what I injected into the Debian Med git. Please be not astonished about the fact that I was using version 0.6. It is simply what uscan --verbose --report was resulting - so I downloaded this for the moment and did git import-orig --pristine-tar mne-python-0.6.tar.gz When trying this I realised that for running the tests the Build-Depends python-coverage was missing. You might not have noticed this since your debian/gbp.conf enforced the usage of debuild instead of using pdebuild. However, the tests are failing (or rather seem to end up in an infinite loop - I interupted after about 1h) anyway and so I disabled them for the moment. I assume this could change with version 0.7 anyway. In any case I would like you to consider the lintian warnings W: python-mne: script-with-language-extension usr/bin/mne_browse_raw.py W: python-mne: script-with-language-extension usr/bin/mne_bti2fiff.py W: python-mne: script-with-language-extension usr/bin/mne_clean_eog_ecg.py W: python-mne: script-with-language-extension usr/bin/mne_compute_proj_ecg.py W: python-mne: script-with-language-extension usr/bin/mne_compute_proj_eog.py W: python-mne: script-with-language-extension usr/bin/mne_flash_bem_model.py W: python-mne: script-with-language-extension usr/bin/mne_kit2fiff.py W: python-mne: script-with-language-extension usr/bin/mne_maxfilter.py W: python-mne: script-with-language-extension usr/bin/mne_surf2bem.py W: python-mne: binary-without-manpage usr/bin/mne_browse_raw.py W: python-mne: binary-without-manpage usr/bin/mne_bti2fiff.py W: python-mne: binary-without-manpage usr/bin/mne_clean_eog_ecg.py W: python-mne: binary-without-manpage usr/bin/mne_compute_proj_ecg.py W: python-mne: binary-without-manpage usr/bin/mne_compute_proj_eog.py W: python-mne: binary-without-manpage usr/bin/mne_flash_bem_model.py W: python-mne: binary-without-manpage usr/bin/mne_kit2fiff.py W: python-mne: binary-without-manpage usr/bin/mne_maxfilter.py W: python-mne: binary-without-manpage usr/bin/mne_surf2bem.py If you have questions why files in /usr/bin should not have a language extension I could provide links who explain this in detail. Since you are upstream I would advise to change this in general to make sure users will not start writing code containing the extension and need to adapt this later once you might consider droping it. What you should do next: Please create some kind of release candidate tag 0.7~rc1 and do uscan --verbose --force-download which should result in something like mne-python_0.7~rc1.orig.tar.gz. Then do git import-orig --pristine-tar mne-python_0.7~rc1.orig.tar.gz to import this source. The next step would be dch -i and adjust the version of the changelog entry to 0.7~rc1 (we might drop my 0.6 version later since it was never released anyway). Now you can do git-buildpackage --git-ignore-new (perhaps also check with droping the comments I injected in the tests). Once you might face any stumbling stone you might `git push` and just ask here for further help. We might iterate that way until you tag 0.7 and we will work on the final release. From my point of view it looks promising for some timely upload to the Debian New queue. Hope this helps Andreas. > On Tue, Nov 12, 2013 at 10:24 PM, Alexandre Gramfort > wrote: > > hi Andreas, > > > > let me know when things are back up. > > > > best, > > Alex > > > > > > On Mon, Nov 11, 2013 at 10:13 AM, Andreas Tille wrote: > >> Hi, > >> > >> currently git.alioth.org and svn.alioth.org are not available - an event > >> that happenes as rarely as one time per five years or so according to my > >> subjective measure. I'll keep you informed once this is settled. > >> > >> Kind regards > >> > >> Andreas. > >> > >> On Fri, Nov 08, 2013 at 04:23:58PM +0100, Alexandre Gramfort wrote: > >>> hi Andreas, > >>> > >>> Yaroslav just told me to try to have mne-python packaged by debian med > >>> so it seems we need to finalize it together. > >>> > >>> Tell me what I can do to help > >>> > >>> Best, > >>> Alex > >>> > >>> > >>> On Thu, Nov 7, 2013 at 4:13 PM, Andreas Tille wrote: > >>> > On Thu, Nov 07, 2013 at 03:36:45PM +0100, Alexandre Gramfort wrote: > >>> >> hi, > >>> >> > >>> >> I can connect with ssh > >>> > > >>> > :-) > >>> > > >>> > Waiting for an answer from Yaroslav now... > >>> > > >>> > Thanks for your engagement > >>> > > >>> > Andreas. > >>> > > >>> > -- > >>> > http://fam-tille.de > >>> > >> > >> -- > >> http://fam-tille.de > -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-wnpp-req
Bug#701962: Updates and packaging repository.
On Thu, 21 Nov 2013, Ra?l S?nchez Siles wrote: Meanwhile, I've set up a repository with latest packaging stuff [0] Hi Raul, I was working on this too but it looks like you're further along than me so I'll defer to you. A couple things though... First, the -dev package can't be Multi-Arch: same because of a couple of header files in libsodium that can potentially differ based on architecture: https://github.com/jedisct1/libsodium/blob/0.4.5/src/libsodium/include/sodium/crypto_stream_salsa20.h.in https://github.com/jedisct1/libsodium/blob/0.4.5/src/libsodium/include/sodium/crypto_scalarmult_curve25519.h.in I think co-installable -dev packages are very nice though, so I was planning to ask upstream if they could refactor those header files to not be different on different architectures. Second, don't forget to install the pkgconfig files (usr/lib/*/pkgconfig/*) in the -dev package. Regards, Andrew -- 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/alpine.deb.2.02.1311210823470.25...@tintin.research.viasinc.com
Bug#728797: ITP: python-mne -- Python modules for MEG and EEG data analysis
>> uscan --verbose --force-download >> git import-orig --pristine-tar mne-python-0.7rc1.tar.gz >> >> but it does not seem to work. It refuses to find the tar.gz > > You need to call this when beeing inside the Git repository dir but > usually the tarball is somewhere else (after using uscan it should be > here: ../mne-python-0.7rc1.tar.gz). Sorry for beeing not precise > enough. gramfort@tsilinuxd74> git import-orig --pristine-tar ../mne-python_0.7rc1.orig.tar.gz ~/work/src/debian/mne-python What is the upstream version? [0.7rc1] gbp:info: Importing '../mne-python_0.7rc1.orig.tar.gz' to branch 'upstream'... gbp:info: Source package is mne-python gbp:info: Upstream version is 0.7rc1 gbp:error: Couldn't commit to 'pristine-tar' with upstream 'upstream': Execution failed: [Errno 2] No such file or directory gbp:error: Import of ../mne-python_0.7rc1.orig.tar.gz failed what should be my upstream repo? I just used: gbp-clone ssh://git.debian.org/git/debian-med/mne-python.git should : ssh://git.debian.org/git/debian-med/mne-python.git be my upstream and master? >> > When trying this I realised that for running the tests the Build-Depends >> > python-coverage was missing. >> >> I added now : >> >> python-coverage > > I thought I would have commited this to the repository I was talking > about (git://git.debian.org/git/debian-med/mne-python.git). does it mean I need to have a debian branch on github that is the master on debian.org? send me a private message to find a way to chat if it's easier/faster. Alex >> let me know what's next besides what's below > > Hope the hint above might lead your further. Please push once this is > done. In case of further trouble I'd try the import-orig at my side. > > Kind regards > >Andreas. > > -- > http://fam-tille.de -- 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/cadeotzpcyloiqwt1mqx-ezkta1ltumoei5d29alphj59zqq...@mail.gmail.com
Bug#728797: ITP: python-mne -- Python modules for MEG and EEG data analysis
hi Andreas, > Yep - since yesterday evening. That's a good timing. ;-) good > You might like to try: > >gbp-clone ssh://git.debian.org/git/debian-med/mne-python.git > > to check out what I injected into the Debian Med git. Please be > not astonished about the fact that I was using version 0.6. It is > simply what > >uscan --verbose --report I now created the v0.7rc1 tag and updated the debian branch. The lintian warnings you mentioned have been fixed with Yaroslav's guidance a few weeks ago now. > was resulting - so I downloaded this for the moment and did > >git import-orig --pristine-tar mne-python-0.6.tar.gz I tried : uscan --verbose --force-download git import-orig --pristine-tar mne-python-0.7rc1.tar.gz but it does not seem to work. It refuses to find the tar.gz > When trying this I realised that for running the tests the Build-Depends > python-coverage was missing. I added now : python-coverage let me know what's next besides what's below thanks for your help Alex > to import this source. The next step would be > >dch -i > > and adjust the version of the changelog entry to 0.7~rc1 (we might drop > my 0.6 version later since it was never released anyway). Now you can > do > >git-buildpackage --git-ignore-new > > (perhaps also check with droping the comments I injected in the tests). > > Once you might face any stumbling stone you might `git push` and just > ask here for further help. We might iterate that way until you tag > 0.7 and we will work on the final release. From my point of view it > looks promising for some timely upload to the Debian New queue. -- 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/cadeotzohcznum0olka60f8scjwnjacvc6s8j8b7snmsqrss...@mail.gmail.com
Processed (with 1 errors): ITP: pd-iemlib -- collection of general purpose objects and filters for Pure Data
Processing commands for cont...@bugs.debian.org: > retitle 603183 ITP: pd-iemlib -- collection of general purpose objects Bug #603183 [wnpp] RFP: pd-iemlib -- collection of general purpose objects and filters for Pure Data Changed Bug title to 'ITP: pd-iemlib -- collection of general purpose objects' from 'RFP: pd-iemlib -- collection of general purpose objects and filters for Pure Data' > and filters for Pure Data Unknown command or malformed arguments to command. > owner 603183 ! Bug #603183 [wnpp] ITP: pd-iemlib -- collection of general purpose objects Owner recorded as IOhannes m zmoelnig . > thanks. Stopping processing here. Please contact me if you need assistance. -- 603183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603183 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.138505236817049.transcr...@bugs.debian.org
Bug#730120: ITP: volatility-profiles -- Linux profiles to Volatility
Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho * Package name: volatility-profiles Version : 20131121 Upstream Author : Joao Eriberto Mota Filho * URL : Linux profiles to Volatility * License : GPL-3.0+ Description : Linux profiles to Volatility This package provides some profiles to be used with Volatility to analyse Linux memory dumps. . The Volatility Framework is a completely open collection of tools for the extraction of digital artifacts from volatile memory (RAM) samples. It is useful in forensics analysis. PS: this package will be under Debian Forensics Team. -- 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/20131121163020.29833.38328.report...@libra.gabcmt.eb.mil.br
Bug#730129: ITP: ebur128-loudness-tools -- implementation of the EBU R128 loudness standard
Package: wnpp Severity: wishlist Owner: Andrew Kelley * Package name: ebur128-loudness-tools Version : 0.0.0 Upstream Author : Jan Kokemüller * URL : https://github.com/jiixyj/libebur128/ * License : MIT Programming Lang: C Description : implementation of the EBU R128 loudness standard Implements M, S and I modes Implements loudness range measurement (EBU - TECH 3342) True peak scanning Supports all samplerates by recalculation of the filter coefficients ReplayGain compatible tagging support for MP3, OGG, Musepack, FLAC.
Bug#724280: ITP: rtax -- Rapid and accurate taxonomic classification of short paired-end sequence reads from the 16S ribosomal RNA gene
Hi Simon, I have not seen the package in NEW any more and also I can not find a package with this name inside the pool. So it seems it has not passed ftpmasters check. Do you have some VCS with the packaging (or preferably might like to use Debian Med VCS)? Kind regards Andreas. On Sun, Sep 29, 2013 at 08:37:40PM +0200, Andreas Tille wrote: > Hi Simon, > > On Sun, Sep 29, 2013 at 09:18:58AM +0200, Simon Kainz wrote: > > Thank you very much. My package is already in the NEW queue, > > Fine. > > > and after quickly inspecting the Debian Med Policy, i suspect i have to > > change some entries in the control file (at least) to make it compliant to > > the Debian Med Policy. So should I just reupload the package after applying > > my changes or should i wait for FTPMasters to either accept or reject the > > package. I just want to keep the work needed for the FTPMasters as small as > > possible, so maybe someone might give ma a hint as how to handle this. > > It's perfectly OK to wait for ftpmaster response and leave the package > in new as is. I have added rtax to the Debian Med bio task as you can > see on the according tasks page.[1] > > > Concerning packaging: For packaging itself, i think i don't need help- i > > already did some packaging work (for some local packages used ad work) and > > i have a very competent sponsor which helped me to create my packages. > > We do absolutely not want to disrupt your workflow / relation to your > sponsor. It is just an offer since in some cases it has turned out to > be hard to find a sponsor. > > > I will try to get my work into alioth/debian-med. > > That would be great and hopefully helpfull also for your work. > > > I will contact debian-med when I am getting stuck, so be prepared for some > > questions :-) > > That's what we are keen on. :-) > > Kind regards > > Andreas. > > [1] http://debian-med.alioth.debian.org/tasks/bio#rtax > > > > Am 28.09.2013 um 21:51 schrieb Andreas Tille : > > > > > > Hi Simon, > > > > > > this package is a perfect target for Debian Med but I noticed you are > > > not yet a member of the Alioth team. Since I'm currently on vaccation > > > and not frequently online I just added skainz-guest to the Debian Med > > > team simply assuming you might consider using Debian Med VCS as > > > described in our team policy[1]. I hope you agree with this and please > > > let us know if you need any help with the packaging. > > > > > > Kind regards > > > > > > Andreas. > > > > > > [1] http://debian-med.alioth.debian.org/docs/policy.html > > > > > >> On Mon, Sep 23, 2013 at 11:56:03AM +0200, Simon Kainz wrote: > > >> Package: wnpp > > >> Severity: wishlist > > >> Owner: Simon Kainz > > >> > > >> * Package name: rtax > > >> Version : 0.983 > > >> Upstream Author : David A. W. Soergel > > >> * URL : David A. W. Soergel > > >> * License : BSD > > >> Programming Lang: Perl > > >> Description : Rapid and accurate taxonomic classification of short > > >> paired-end sequence reads from the 16S ribosomal RNA gene > > >> > > >> Short-read technologies for microbial community profiling are > > >> increasingly > > >> popular, yet previous techniques for assigning taxonomy to paired-end > > >> reads > > >> perform poorly. RTAX provides rapid taxonomic assignments of paired-end > > >> reads > > >> using a consensus algorithm. > > >> > > >> This tool is an optional dependency for qiime(which is already packaged) > > >> and it > > >> would be great to have it > > >> packaged for Debian. > > >> > > >> Regards, > > >> > > >> Simon > > >> > > >> > > >> -- > > >> To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org > > >> with a subject of "unsubscribe". Trouble? Contact > > >> listmas...@lists.debian.org > > >> Archive: > > >> http://lists.debian.org/20130923095603.26061.18627.report...@zidpc9027.tu-graz.ac.at > > > > > > -- > > > http://fam-tille.de > > > > -- > http://fam-tille.de > > > -- > To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/20130929183740.ga12...@an3as.eu > > -- http://fam-tille.de -- 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/20131121161937.gj7...@an3as.eu
Bug#730132: ITP: flask-sqlalchemy -- Adds SQLAlchemy support to your Flask application
Package: wnpp Severity: wishlist Owner: Thomas Bechtold * Package name: flask-sqlalchemy Version : 1.0 Upstream Author : Armin Ronacher * URL : https://pypi.python.org/pypi/Flask-SQLAlchemy * License : BSD Programming Lang: Python Description : Adds SQLAlchemy support to your Flask application Flask is a micro web framework for Python based on Werkzeug, Jinja 2 and good intentions. .. This package adds SQLAlchemy support to Flask. -- 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/20131121202043.7497.29377.reportbug@steinpilz
Bug#701962: Updates and packaging repository.
On Thu, 21 Nov 2013 08:44:57 -0800 (PST) Andrew Ayer wrote: > I think co-installable -dev packages are very nice though, so I was > planning to ask upstream if they could refactor those header files to > not be different on different architectures. I have created a libsodium issue about this: https://github.com/jedisct1/libsodium/issues/102 I'll report back what I hear. Regards, Andrew -- 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/20131121090443.7bb5b351.a...@andrewayer.name
Bug#705825: marked as done (ITA: jython -- Python seamlessly integrated with Java)
Your message dated Thu, 21 Nov 2013 16:18:38 + with message-id and subject line Bug#705825: fixed in jython 2.5.3-1 has caused the Debian Bug report #705825, regarding ITA: jython -- Python seamlessly integrated with Java 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.) -- 705825: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: normal I hereby orphan the jython package. Jython is an implementation of the high-level, dynamic, object-oriented language Python seamlessly integrated with the Java platform. The predecessor to Jython, JPython, is certified as 100% Pure Java. . Jython is complementary to Java and allows the two languages to be freely mixed. It is especially suited for embedded scripting, interactive experimentation and rapid application development, and it can interact with Java packages or with running Java applications. -- Nicolas Duboc signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: jython Source-Version: 2.5.3-1 We believe that the bug you reported is fixed in the latest version of jython, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 705...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated jython package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 21 Nov 2013 14:25:27 +0100 Source: jython Binary: jython jython-doc Architecture: source all Version: 2.5.3-1 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers Changed-By: Sylvestre Ledru Description: jython - Python seamlessly integrated with Java jython-doc - Jython documentation including API docs Closes: 676831 690116 705146 705825 Changes: jython (2.5.3-1) unstable; urgency=low . * New upstream release (Closes: #690116) * Adopt the package under the pkg-java umbrella (Closes: #705825) * Standards-Version updated to 3.9.5 * Import in the pkg-java VCS * Switch to dpkg-source 3.0 (quilt) format * jython should work unde virtualenv (Closes: #705146) Thanks to Arthur Noel for the patch * Update of the description (Closes: #676831) Checksums-Sha1: 48eece4c8bf61d82015c6be7fadab300ef754628 1563 jython_2.5.3-1.dsc fb2329935da29375f6c58e80c361a22fef1ce694 5731140 jython_2.5.3.orig.tar.bz2 8f2bb601866a67ef1632c38b372751aa341a5acd 17611 jython_2.5.3-1.debian.tar.gz 25318458e744ef548ad23e810815fece46c0628a 6908170 jython_2.5.3-1_all.deb 3c789bf2ce00854e8d35d1541069ea852006bfb1 580666 jython-doc_2.5.3-1_all.deb Checksums-Sha256: b8aebcd02335bb6f9cced0b729f82ed1a14fe7846cd0f171df4e8f92c52d0f94 1563 jython_2.5.3-1.dsc f65ba40098f9312ed487219e64c4ea01fecad927411b1a72dc1d8cadf0ddc947 5731140 jython_2.5.3.orig.tar.bz2 61907aaff21a84d1a01935ab66df12db882344770eaabe0d87e24a4684064eb0 17611 jython_2.5.3-1.debian.tar.gz 0f5b915d72202319ea70eea2fac88d0f7d829cc6b6594359828757d1b244d186 6908170 jython_2.5.3-1_all.deb 2170badb1ffdf4141b3d49c2e08074ff8bac948286f7c1505dc1cea272ed84ce 580666 jython-doc_2.5.3-1_all.deb Files: 74971485adff684ac00f98085d7ca7b5 1563 python optional jython_2.5.3-1.dsc 2e4210614f20aa3cbcef9031601679b7 5731140 python optional jython_2.5.3.orig.tar.bz2 c6d292143c0dc35026349205ababd7a9 17611 python optional jython_2.5.3-1.debian.tar.gz 0b5e88add03f414dca9f426078646b3a 6908170 python optional jython_2.5.3-1_all.deb 1fe596e5ed0505edd0ffcd9eb04109b7 580666 doc optional jython-doc_2.5.3-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iEYEARECAAYFAlKOMWoACgkQiOXXM92JlhC2bwCgzEjPsqa9MHtkxqB7zOkZifB7 skYAoO6wme/LSKc8V66kGut1ox5s+s6h =KWZX -END PGP SIGNATURE End Message ---
Bug#728797: ITP: python-mne -- Python modules for MEG and EEG data analysis
Hi Alexandre, On Thu, Nov 21, 2013 at 04:29:10PM +0100, Alexandre Gramfort wrote: > > to check out what I injected into the Debian Med git. Please be > > not astonished about the fact that I was using version 0.6. It is > > simply what > > > >uscan --verbose --report > > I now created the v0.7rc1 tag and updated the debian branch. > The lintian warnings you mentioned have been fixed with Yaroslav's > guidance a few weeks ago now. Great! > > was resulting - so I downloaded this for the moment and did > > > >git import-orig --pristine-tar mne-python-0.6.tar.gz > > I tried : > > uscan --verbose --force-download > git import-orig --pristine-tar mne-python-0.7rc1.tar.gz > > but it does not seem to work. It refuses to find the tar.gz You need to call this when beeing inside the Git repository dir but usually the tarball is somewhere else (after using uscan it should be here: ../mne-python-0.7rc1.tar.gz). Sorry for beeing not precise enough. > > When trying this I realised that for running the tests the Build-Depends > > python-coverage was missing. > > I added now : > > python-coverage I thought I would have commited this to the repository I was talking about (git://git.debian.org/git/debian-med/mne-python.git). > let me know what's next besides what's below Hope the hint above might lead your further. Please push once this is done. In case of further trouble I'd try the import-orig at my side. Kind regards Andreas. -- http://fam-tille.de -- 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/20131121160756.gi7...@an3as.eu
Bug#700630: Transfer Offer... You can contact me on my private email: (mrjerrynatai2...@yahoo.com.hk)
-- I look forward to hearing from you
Bug#729441: marked as done (ITA: newlib -- Newlib is a C library intended for use on embedded systems)
Your message dated Fri, 22 Nov 2013 05:00:11 + with message-id and subject line Bug#729441: fixed in newlib 2.0.0-1 has caused the Debian Bug report #729441, regarding ITA: newlib -- Newlib is a C library intended for use on embedded systems 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.) -- 729441: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Agustin Henze X-Debbugs-CC: debian-de...@lists.debian.org, debian-cr...@lists.debian.org Hi all, I'm adopting this package and I'll upload the new upstream release (2.0.0) with big changes in the packaging. The main change is that it'll only generate 2 binaries. * libnewlib-dev: This package contains the newlib headers. * libnewlib-arm-none-eabi: This package contains the newlib library compiled for Cortex-A*, Cortex-R4/R5/R7 and Cortex-M0/M0+/M3/M4 targets. That's because I use and can test daily those targets. If someone can help for still maintain the old binaries packages (libnewlib0, newlib-spu, newlib-m68hc1x, newlib-source) is welcome. I'll working in collab-maint[0] when alioth back online again. [0] git://anonscm.debian.org/collab-maint/newlib.git -- TiN signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: newlib Source-Version: 2.0.0-1 We believe that the bug you reported is fixed in the latest version of newlib, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 729...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Agustin Henze (supplier of updated newlib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Nov 2013 08:13:24 -0300 Source: newlib Binary: libnewlib-dev libnewlib-doc libnewlib-arm-none-eabi Architecture: source all Version: 2.0.0-1 Distribution: unstable Urgency: low Maintainer: Agustin Henze Changed-By: Agustin Henze Description: libnewlib-arm-none-eabi - C library and math library compiled for bare metal using Cortex A libnewlib-dev - C library and math library intended for use on embedded systems libnewlib-doc - C library and math library intended for use on embedded systems ( Closes: 729441 Changes: newlib (2.0.0-1) unstable; urgency=low . * New upstream release. * New maintainer (Closes: #729441). * Packages removed (libnewlib0, newlib-spu, newlib-m68hc1x, newlib-source) * New package libnewlib-arm-none-eabi * debian/rules rewrited Checksums-Sha1: 7513a3be6a8f9252cb73c8f08515fa56ddeb8de5 2017 newlib_2.0.0-1.dsc ea6b5727162453284791869e905f39fb8fab8d3f 15868470 newlib_2.0.0.orig.tar.gz 11fe95be7506437204532512ca11e92a8fcbb5cd 12989 newlib_2.0.0-1.debian.tar.gz 4930fc4629893874f17903b0fb763ce7edc0f4e3 212070 libnewlib-dev_2.0.0-1_all.deb 3eaf641ad82f87220501b6db2173228aa542fbbe 284226 libnewlib-doc_2.0.0-1_all.deb 95742c33b9cadcaa7de89f1ecac2594b63cc5d2b 6006840 libnewlib-arm-none-eabi_2.0.0-1_all.deb Checksums-Sha256: 82c60e2c5ddeb75fed921cd2dcc0a3cec2855149c7ac9158871f66f7d079650c 2017 newlib_2.0.0-1.dsc 49c29e9129325e7c3b221aa829743ddcd796d024440e47c80fc0d6769af72d8a 15868470 newlib_2.0.0.orig.tar.gz f6a448db136168215faffbd1c8bf59fc1544da938bdb4d8a927a7200634d020c 12989 newlib_2.0.0-1.debian.tar.gz d2d74fd32cb7eec5fc8e340c551ab56b813f91752550342c3da4c209774da955 212070 libnewlib-dev_2.0.0-1_all.deb 3692e4aacdefb7e4cb5f4acbfd06586e232426c4f0499d5470625dbed3658698 284226 libnewlib-doc_2.0.0-1_all.deb e32875a47d6f787febc57593985ce6f6b104e001f66e972cfdd6f065fc6e7480 6006840 libnewlib-arm-none-eabi_2.0.0-1_all.deb Files: a53cf07fa2223145690288e0af98429c 2017 devel extra newlib_2.0.0-1.dsc e3e936235e56d6a28afb2a7f98b1a635 15868470 devel extra newlib_2.0.0.orig.tar.gz c07f651d043df68a3960690dc77e00c5 12989 devel extra newlib_2.0.0-1.debian.tar.gz d3168da8f96a4f4817e141fa15b46f52 212070 libdevel extra libnewlib-dev_2.0.0-1_all.deb 1622adba0303248c9043afaa08a74f63 284226 doc extra libnewlib-doc_2.0.0-1_all.deb e0025a5a5ea5dc3cc23361a612e4157a 6006840 libs extra libnewlib-arm-none-eabi_2.0.0-1_all.deb -
