Bug#749815: Package updated
Hmm, I am getting unsure - it seems like they don't want you to create an alioth project if you are only maintaining one package - see https://wiki.debian.org/Alioth/PackagingProject and https://wiki.debian.org/Alioth/FAQ#Will_you_accept_my_project_.3F https://wiki.debian.org/Alioth/FAQ#Do_I_need_an_Alioth_project_.3F - I have asked on the alioth IRC-channel, let's see what they say. I read the IRC answer and set the maintainer to l10 team, seems appropriate. BTW upstream changed the name in 1.6.9-oss, while I imported it as 1.6.9, do you think we should change the name accordingly (I mean debian/changelog)? Yeah, that sound like a good idea. Correcting myself, it seems not, seems that oss is the version with all the deps, while there is a stripped versionin /releases. I corrected watch file, copyright, and reimported the corrected version. Unfortunately I needed to override the upstream/1.6.9 tag, otherwise git-buildpackage would have complained in recreating the upstream tarball. Sorry for the noise. I also added a .gitignore and removed the built files from the source tree. cheers, Gianfranco -- Andreas Rönnquist gus...@gusnan.se -- To unsubscribe, send mail to 749815-unsubscr...@bugs.debian.org. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749815: Package updated
Hi Andreas, I have two initial comments (Without having done an in-depth review): We could create an alioth project including a mailinglist, and use that mailinglist as maintainer, and put us all as uploaders. It might ease collaboration, if we just need one email to remember for maintenance questions. What do you think? (Also, I'd like to use my @debian.org email for package maintenance). I changed your mail address, however I'm not sure how to create an alioth group, maybe I need to be a DD for this? Feel free to do it, of course I prefer a lot this way :D (also for team uploads is better) Hmm, I am getting unsure - it seems like they don't want you to create an alioth project if you are only maintaining one package - see https://wiki.debian.org/Alioth/PackagingProject and https://wiki.debian.org/Alioth/FAQ#Will_you_accept_my_project_.3F https://wiki.debian.org/Alioth/FAQ#Do_I_need_an_Alioth_project_.3F - I have asked on the alioth IRC-channel, let's see what they say. BTW upstream changed the name in 1.6.9-oss, while I imported it as 1.6.9, do you think we should change the name accordingly (I mean debian/changelog)? Yeah, that sound like a good idea. -- Andreas Rönnquist gus...@gusnan.se -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749815: Package updated
Hi, Gianfranco, Brilliant work. I am a novice in packaging for Debian, so I am not sure how can I help in continuing this effort. Hi Andreas and Timur, As you might have noticed the new poedit releases uses lucene++ library, this is why in the last few weeks I focused in packaging it. I finally (with great help from Tobi) achieved this goal, and the library is waiting in ftp NEW queue [1] Unfortunately this morning while I was working in packaging poedit, I noticed that a git branch was already available on collab-maint, and I did the whole work again, because the git was missing some debian/unstable releases, with important fixes, and it never got any upload. I'm attaching the lucene++ debian directory, the source can be found here [2], and I'm pushing on collab-maint the changes I did (and the merge). The new releases are huge in size terms, so I removed the deps directory from the source tarball prior to the import (don't know why upstream bundles lucene/wx/boost/... making the source something like 700MB (uncompressed). The debian/copyright still needs to be updated, but I'm pushing the changes to let you know the progresses I did and collaborate on the same repository. Please don't spare your work and your time, let's follow up on the same repository [3]:) [1] https://ftp-master.debian.org/new/lucene++_3.0.6-1.html [2] https://github.com/luceneplusplus/LucenePlusPlus [3] http://anonscm.debian.org/cgit/collab-maint/poedit.git thanks, Gianfranco -- С уважением, Тимирханов mailto:timur.timirkha...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749815: Package updated
Il Mercoledì 10 Settembre 2014 9:00, Тимирханов Тимур timur.timirkha...@gmail.com ha scritto: Hi, Gianfranco, Hi, Brilliant work. I am a novice in packaging for Debian, so I am not sure how can I help in continuing this effort. The best help I think might be to install poedit from unstable/testing, build lucene++ build the new one and install it. The upgrade path should be smoothless, and moreover testing the new release is so appreciated (I'm using it, but would be nice to have some more eyes) thanks, Gianfranco Hi Andreas and Timur, As you might have noticed the new poedit releases uses lucene++ library, this is why in the last few weeks I focused in packaging it. I finally (with great help from Tobi) achieved this goal, and the library is waiting in ftp NEW queue [1] Unfortunately this morning while I was working in packaging poedit, I noticed that a git branch was already available on collab-maint, and I did the whole work again, because the git was missing some debian/unstable releases, with important fixes, and it never got any upload. I'm attaching the lucene++ debian directory, the source can be found here [2], and I'm pushing on collab-maint the changes I did (and the merge). The new releases are huge in size terms, so I removed the deps directory from the source tarball prior to the import (don't know why upstream bundles lucene/wx/boost/... making the source something like 700MB (uncompressed). The debian/copyright still needs to be updated, but I'm pushing the changes to let you know the progresses I did and collaborate on the same repository. Please don't spare your work and your time, let's follow up on the same repository [3]:) [1] https://ftp-master.debian.org/new/lucene++_3.0.6-1.html [2] https://github.com/luceneplusplus/LucenePlusPlus [3] http://anonscm.debian.org/cgit/collab-maint/poedit.git thanks, Gianfranco -- С уважением, Тимирханов mailto:timur.timirkha...@gmail.com -- To unsubscribe, send mail to 749815-unsubscr...@bugs.debian.org. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749815: Package updated
Il Martedì 9 Settembre 2014 15:12, Gianfranco Costamagna costamagnagianfra...@yahoo.it ha scritto: As you might have noticed the new poedit releases uses lucene++ library, this is why in the last few weeks I focused in packaging it. I finally (with great help from Tobi) achieved this goal, and the library is waiting in ftp NEW queue [1] -- 8 -- The new releases are huge in size terms, so I removed the deps directory from the source tarball prior to the import (don't know why upstream bundles lucene/wx/boost/... making the source something like 700MB (uncompressed). The debian/copyright still needs to be updated, but I'm pushing the changes to let you know the progresses I did and collaborate on the same repository. the copyright is up-to-date now. I also switched to autoreconf, waiting for a review :) I have two initial comments (Without having done an in-depth review): We could create an alioth project including a mailinglist, and use that mailinglist as maintainer, and put us all as uploaders. It might ease collaboration, if we just need one email to remember for maintenance questions. What do you think? (Also, I'd like to use my @debian.org email for package maintenance). You have removed a whole lot that has no use in the package such as embedded libraries (Which is good) - but you could have made an Files-Excluded-entry in the copyright for this. This would make those files be removed when using something like git-importorig --uscan also, automating the entire importing process and removing the need to remove files by hand. This also adds the benefit that you just need to add the files that are to be removed once, and simply update the list for each upstream release, if more unwanted files are added to the upstream tarball that we need to remove. See https://wiki.debian.org/UscanEnhancements for information on this. The wikipage mentions Problematic copyright, but this is of course useful in our case too. -- Andreas Rönnquist gus...@gusnan.se -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749815: Package updated
Hi Andreas, I have two initial comments (Without having done an in-depth review): We could create an alioth project including a mailinglist, and use that mailinglist as maintainer, and put us all as uploaders. It might ease collaboration, if we just need one email to remember for maintenance questions. What do you think? (Also, I'd like to use my @debian.org email for package maintenance). I changed your mail address, however I'm not sure how to create an alioth group, maybe I need to be a DD for this? Feel free to do it, of course I prefer a lot this way :D (also for team uploads is better) You have removed a whole lot that has no use in the package such as embedded libraries (Which is good) - but you could have made an Files-Excluded-entry in the copyright for this. This would make those files be removed when using something like git-importorig --uscan also, automating the entire importing process and removing the need to remove files by hand. This also adds the benefit that you just need to add the files that are to be removed once, and simply update the list for each upstream release, if more unwanted files are added to the upstream tarball that we need to remove. See https://wiki.debian.org/UscanEnhancements for information on this. The wikipage mentions Problematic copyright, but this is of course useful in our case too. yes thanks, I was already aware of this, but I didn't use because I though I was the only one caring about poedit :) Now that we are at least three I changed it, however I think the correct string is git-import-orig --pristine-tar --uscan :) I tried to import again the package and git whatchanged didn't even show the entry, so I presume it is working correctly :) BTW upstream changed the name in 1.6.9-oss, while I imported it as 1.6.9, do you think we should change the name accordingly (I mean debian/changelog)? many thanks for the feedbacks, Gianfranco -- Andreas Rönnquist gus...@gusnan.se -- To unsubscribe, send mail to 749815-unsubscr...@bugs.debian.org. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749815: Package updated
Hi Andreas and Timur, As you might have noticed the new poedit releases uses lucene++ library, this is why in the last few weeks I focused in packaging it. I finally (with great help from Tobi) achieved this goal, and the library is waiting in ftp NEW queue [1] Unfortunately this morning while I was working in packaging poedit, I noticed that a git branch was already available on collab-maint, and I did the whole work again, because the git was missing some debian/unstable releases, with important fixes, and it never got any upload. I'm attaching the lucene++ debian directory, the source can be found here [2], and I'm pushing on collab-maint the changes I did (and the merge). The new releases are huge in size terms, so I removed the deps directory from the source tarball prior to the import (don't know why upstream bundles lucene/wx/boost/... making the source something like 700MB (uncompressed). The debian/copyright still needs to be updated, but I'm pushing the changes to let you know the progresses I did and collaborate on the same repository. Please don't spare your work and your time, let's follow up on the same repository [3]:) [1] https://ftp-master.debian.org/new/lucene++_3.0.6-1.html [2] https://github.com/luceneplusplus/LucenePlusPlus [3] http://anonscm.debian.org/cgit/collab-maint/poedit.git thanks, Gianfranco lucene++_3.0.6-1.debian.tar.gz Description: GNU Zip compressed data
Bug#749815: Package updated
Hi again, Il Martedì 9 Settembre 2014 15:12, Gianfranco Costamagna costamagnagianfra...@yahoo.it ha scritto: Hi Andreas and Timur, As you might have noticed the new poedit releases uses lucene++ library, this is why in the last few weeks I focused in packaging it. I finally (with great help from Tobi) achieved this goal, and the library is waiting in ftp NEW queue [1] Unfortunately this morning while I was working in packaging poedit, I noticed that a git branch was already available on collab-maint, and I did the whole work again, because the git was missing some debian/unstable releases, with important fixes, and it never got any upload. I'm attaching the lucene++ debian directory, the source can be found here [2], and I'm pushing on collab-maint the changes I did (and the merge). The new releases are huge in size terms, so I removed the deps directory from the source tarball prior to the import (don't know why upstream bundles lucene/wx/boost/... making the source something like 700MB (uncompressed). The debian/copyright still needs to be updated, but I'm pushing the changes to let you know the progresses I did and collaborate on the same repository. the copyright is up-to-date now. I also switched to autoreconf, waiting for a review :) thanks G. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
