Re: Packaging pxljr [was: Junior packaging tasks within the Debian Printing Team]
Le mercredi, 8 juin 2011 06.51:49, Henry velez a écrit : Thank you for your help. I rebuilt the git-repo and i got something like your example using the sources from https://launchpad.net/ubuntu/+source/pxljr and i used git-import-dsc to generate the tree. let me know if it's ok or if i have to improve something in the repo. I am following the instructions of 2 sites: http://wiki.debian.org/Games/VCS/git#Uploading_a_package_to_the_repository and http://www.eyrie.org/~eagle/notes/debian/git.html. pxljr git: https://github.com/abadon7/pxljr Hi Henry, almost there. :-) Here are the remaining problems I could identify: == Identification == $ git show | grep Author Author: Henry henry@localhost.localdomain You need to setup this correctly to ensure the traceability of your commits back to you. This is done by (see man gittutorial): $ git config --global user.name Your Name Comes Here $ git config --global user.email y...@yourdomain.example.com (--global to configure that for all your repositories; remove it to configure particular repositories). == Branches == I can't see the other branches than master (upstream and pristine-tar); did you forget to push them ? (Same for the upstream/… and debian/… tags) After fixing those two things, I think we'll be able to start working on further issues. Cheers, OdyX -- OdyX signature.asc Description: This is a digitally signed message part.
Re: Packaging pxljr [was: Junior packaging tasks within the Debian Printing Team]
2011/6/8 Didier Raboud o...@debian.org Le mercredi, 8 juin 2011 06.51:49, Henry velez a écrit : Thank you for your help. I rebuilt the git-repo and i got something like your example using the sources from https://launchpad.net/ubuntu/+source/pxljr and i used git-import-dsc to generate the tree. let me know if it's ok or if i have to improve something in the repo. I am following the instructions of 2 sites: http://wiki.debian.org/Games/VCS/git#Uploading_a_package_to_the_repository and http://www.eyrie.org/~eagle/notes/debian/git.html. pxljr git: https://github.com/abadon7/pxljr Hi Henry, almost there. :-) Here are the remaining problems I could identify: == Identification == $ git show | grep Author Author: Henry henry@localhost.localdomain You need to setup this correctly to ensure the traceability of your commits back to you. This is done by (see man gittutorial): $ git config --global user.name Your Name Comes Here $ git config --global user.email y...@yourdomain.example.com (--global to configure that for all your repositories; remove it to configure particular repositories). == Branches == I can't see the other branches than master (upstream and pristine-tar); did you forget to push them ? (Same for the upstream/… and debian/… tags) After fixing those two things, I think we'll be able to start working on further issues. Hi Didier. I think it is ready. I rebuilt everything again and now i have the 3 branches, the right identification and the output of git tag is debian/1.1-0ubuntu7- upstream/1.1, so i think that tags also are ready . Is it ok? Regards -- Henry Vélez
Re: Packaging pxljr [was: Junior packaging tasks within the Debian Printing Team]
2011/6/6 Didier Raboud o...@debian.org Le jeudi, 2 juin 2011 06.27:04, Henry velez a écrit : Hi guys. This is the git repository to push Ubuntu uploads there.: https://github.com/abadon7/pxljr https://github.com/abadon7/pxljrI took the packages from http://packages.ubuntu.com/natty/pxljr, but I am not shure if those are the correct ones or if I have to use another source to get them. Hi Henry, and thanks for your initial work. Unfortunately, this repository is not very useful: you committed binary packages in (there is no need to keep them) and it doesn't follow the usual layout. See e.g. the pnm2ppa git packaging repository: http://anonscm.debian.org/gitweb/?p=collab-maint/pnm2ppa.git;a=shortlog It contains one upstream branch; that has all the unpacked upstream revisions, and a debian branch that gets all the debian/-related changes in; with regular merges from the upstream branch when needed. Additionnally, there is the pristine-tar branch that contains the pristine-tar blobs to reconstruct the original archives from the upstream branch. In the pnm2ppa case, I created the git-repository from the previous source packages: http://snapshot.debian.org/package/pnm2ppa/ and used git-import-dsc multiple times (and in the correct order). This /should/ give you a more convenient git repository. Can you do that ? Hi Didier. Thank you for your help. I rebuilt the git-repo and i got something like your example using the sources from https://launchpad.net/ubuntu/+source/pxljr and i used git-import-dsc to generate the tree. let me know if it's ok or if i have to improve something in the repo. I am following the instructions of 2 sites: http://wiki.debian.org/Games/VCS/git#Uploading_a_package_to_the_repository and http://www.eyrie.org/~eagle/notes/debian/git.html. pxljr git: https://github.com/abadon7/pxljr Cheers. -- Henry Vélez
Re: Packaging pxljr [was: Junior packaging tasks within the Debian Printing Team]
Le jeudi, 2 juin 2011 06.27:04, Henry velez a écrit : Hi guys. This is the git repository to push Ubuntu uploads there.: https://github.com/abadon7/pxljr https://github.com/abadon7/pxljrI took the packages from http://packages.ubuntu.com/natty/pxljr, but I am not shure if those are the correct ones or if I have to use another source to get them. Hi Henry, and thanks for your initial work. Unfortunately, this repository is not very useful: you committed binary packages in (there is no need to keep them) and it doesn't follow the usual layout. See e.g. the pnm2ppa git packaging repository: http://anonscm.debian.org/gitweb/?p=collab-maint/pnm2ppa.git;a=shortlog It contains one upstream branch; that has all the unpacked upstream revisions, and a debian branch that gets all the debian/-related changes in; with regular merges from the upstream branch when needed. Additionnally, there is the pristine-tar branch that contains the pristine-tar blobs to reconstruct the original archives from the upstream branch. In the pnm2ppa case, I created the git-repository from the previous source packages: http://snapshot.debian.org/package/pnm2ppa/ and used git-import-dsc multiple times (and in the correct order). This /should/ give you a more convenient git repository. Can you do that ? Cheers, -- OdyX -- To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201106061341.01939.o...@debian.org
Re: Packaging pxljr [was: Junior packaging tasks within the Debian Printing Team]
2011/6/2 Till Kamppeter till.kamppe...@gmail.com On 06/02/2011 06:27 AM, Henry velez wrote: This is the git repository to push Ubuntu uploads there.: https://github.com/abadon7/pxljr https://github.com/abadon7/pxljrI took the packages from http://packages.ubuntu.com/natty/pxljr, but I am not shure if those are the correct ones or if I have to use another source to get them. The version you have taken is correct. Do you have a printer which is used with this driver? If yes, can you investigate this problem: Sadly I don't have one. But can I help in other ways? https://bugs.launchpad.net/pxljr/+bug/777670 It seems that there is some incompatibility with Ghostscript 9.xx. Till -- Henry Vélez
Re: Packaging pxljr [was: Junior packaging tasks within the Debian Printing Team]
On 06/02/2011 06:27 AM, Henry velez wrote: This is the git repository to push Ubuntu uploads there.: https://github.com/abadon7/pxljr https://github.com/abadon7/pxljrI took the packages from http://packages.ubuntu.com/natty/pxljr, but I am not shure if those are the correct ones or if I have to use another source to get them. The version you have taken is correct. Do you have a printer which is used with this driver? If yes, can you investigate this problem: https://bugs.launchpad.net/pxljr/+bug/777670 It seems that there is some incompatibility with Ghostscript 9.xx. Till -- To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4de73fe7.9080...@gmail.com
Re: Packaging pxljr [was: Junior packaging tasks within the Debian Printing Team]
Hi Henry (Note that according to my previous N.B. at the end of my mail, I dropped the explicit CC, assuming that you are subscribed to debian-printing@l.d.o). Henry velez wrote: Although note that in any case, importing the past Ubuntu uploads into a git repository, hosted on alioth.debian.org, is a good thing to do; this helps reviewing past and future changes. Can you do that (hint: bzr-fastexport should help) ? (You can start in a private git repository stored elsewhere before pushing it to the official location.) I will start right now. Great. When could be a good time to create an ITP bug? As soon as you begin to work on the package; that means now. When working on existing package, writing the ITP is easier as you can steal^Wtake the existing descriptions and such from the existing package. Do do it The Right Way, you could set the X-Debbugs-CC pseudo-header to this list so that the people subscribed will see it. (FWIW, I'll be away from any type of internet access for the next 4 days, so don't expect fast answers until then.) Cheers, OdyX -- To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/is5c29$8mf$1...@dough.gmane.org
Re: Packaging pxljr [was: Junior packaging tasks within the Debian Printing Team]
Hi guys. This is the git repository to push Ubuntu uploads there.: https://github.com/abadon7/pxljr https://github.com/abadon7/pxljrI took the packages from http://packages.ubuntu.com/natty/pxljr, but I am not shure if those are the correct ones or if I have to use another source to get them. Regards Henry Vélez
Re: Packaging pxljr [was: Junior packaging tasks within the Debian Printing Team]
2011/5/31 Till Kamppeter till.kamppe...@gmail.com I am OK with having all these packages co-maintained in Debian and Ubuntu. As I mentioned earlier we should approach a unique printing stack for Debian and Ubuntu to reduce duplicated effort. The packages should be done in a way that the source packages for Debian and Ubuntu are equal, special Ubuntu-only functionality, like for example the Apport hook for automatic bug reports on Launchpad, should be present but only be built/installed if the package gets built on a Ubuntu system. This way most packages can be actively maintained at Debian and auto-synced by Ubuntu. AFAIK CUPS works this way. At least packages can get released as snapshots from the same code repository, as it is done with HPLIP. That sounds good. What do we need do to get it? Till On 05/31/2011 11:54 AM, Didier Raboud wrote: By which yould you like to start with (I don't think it's good to work on both at the same time) ? In my humble opinion, it's maybe better to start with modifying an existing package, that would be pxljr. For pxljr, the first task would be to Contact the current Ubuntu maintainers to ask them if they would be interested in (co-)maintaining the package directly in Debian. Would you be ready to draft a mail to the current Ubuntu maintainer (Till Kamppeter), asking him what his opinions are ? Although note that in any case, importing the past Ubuntu uploads into a git repository, hosted on alioth.debian.org, is a good thing to do; this helps reviewing past and future changes. Can you do that (hint: bzr-fastexport should help) ? (You can start in a private git repository stored elsewhere before pushing it to the official location.) Once we have Till's answer and the past source packages in a git repository, we'll be ready for the needed changes to get it uploaded to Debian (in any case, we need an ITP bug, e.g.). Don't hesitate to ask any questions you might have! Cheers, OdyX, who is happy to have found someone. N.B. I CC'ed you on my answer, contrary to the Debian lists netiquette (which assumes that no copies are wanted). Are you subscribed to debian-printing or do you want explicit copies each time (which you should state explicitely each time) ?