Re: Packaging pxljr
Hi Didier. Maybe you checked the git repo, I think it is ready. So, I was trying to build the package, but i am getting an error. To start with the package I did this. 1. I deleted the debian folder of the source. (previously i did a copy in another place) 2. I ran the dh_make command to generate the debian folder again. 3. I copied the rules and the changelog files of the old (ubuntu) package into the new debian folder 4. I ran the debuild -rfakefoot command. I know that the git repo is to use git-buildpackage, but i wanted to use the classical way to be sure that everything is OK with the new package. Attached you will find the output of debuild -rfakefoot. Thank you very much. Regards. 2011/6/9 Didier Raboud o...@debian.org Le jeudi, 9 juin 2011 06.23:55, Henry velez a écrit : 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 almost there again. :-) The tags haven't appeared on the repository; you need to push them all at once (git push --tags) or explicitely (git push debian/1.1-0ubuntu7 upstream/1.1). And what is the reason for your commit f02a4bd [0] ? This will create an unnecessary difference between the original code and the debian'ized source. Now, the next steps are 1) send an ITP bug (reportbug wnpp), that uses the information from debian/control. 2) build the package in a clean chroot and make all needed changes towards the Debian upload (the lintian output is a very good starter) 3) commit each change independently with a good commit message. In the obvious things to enhance, I would see: * conversion to 3.0 (quilt) source format * conversion of the debian/rules to tiny dh7 style * conditional installation of the Ubuntu-specific apport hook Ready to start ? Cheers, -- OdyX [0] https://github.com/abadon7/pxljr/commit/f02a4dbdf0aa27eed9c5af196fc051f504108ddf -- Henry Vélez pxljrpackageerror Description: Binary data
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]
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]
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) ?
Re: Junior packaging tasks within the Debian Printing Team
Hi Didier. My name is Henry Vélez. I am starting in Debian as a helper, because of that I would like to take care of these 2 packages: rastertosag-gd pxljr Please let me know if it is possible. Regards. 2011/5/30 Didier Raboud o...@debian.org Dear prospective maintainers, As packaging in teams and work on specific areas of Debian is often (and rightly so) preferred to one-shot pet-package sponsoring, I would like to propose 4 relatively easy packaging tasks. The global goal of those packaging tasks are: * to make sure Debian provides more printer drivers (this eliminates the need for hand-installation of drivers) * to offer low-barrier entry-points for newcomers to packaging; * to get new blood onboard the Debian Printing Team and in Debian in general. For all the following packages; those are the common tasks: * Make sure to have an ITP filed, and have the eventual RFPs renamed correctly. * Check their DFSG-freeness. * Packages have to be checked against latest Policy, so eventually updated. (lintian -ivI --pedantic with explained and reasonable exceptions is a good goal.) * Packaging is preferably done in git, under collab-maint. Bonus points if the history of the package is reflected in the packaging repository. (master/upstream/pristine-tar git workflow is preferred). === Merge two drivers back to Debian === Currently, two drivers have been available in Ubuntu but got never synced to Debian: m2300w pxljr For these two, the following additional tasks have to be handled (first): * Contact the current Ubuntu maintainers to ask them if they would be interested in (co-)maintaining the package directly in Debian. === Package two drivers for Debian === Currently, two drivers have been added to recent new foomatic-db entries: rastertosag-gdi c2esp For those, the packaging has to be done from scratch. === Feedback and upload === For those 4 packages, I will happily provide feedback on packaging techniques, processes, etc. More globally, I will make sure to mentor the person taking the challenge and guide him/her until the package gets out of NEW (including sponsoring the package; of course). I will also happily mentor and sponsor subsequent uploads of those packages. === Candidate ? === Anyone willing to get involved in making Debian better on the long term (having DM and/or DD statuses in sight is good), ready to maintain said packages on the long-term, with reasonable preliminary knowledge of the Debian Policy, packaging techniques and git usage can apply. (If you think you don't qualify, then don't be shy and apply anyway!) A candidate owning or having access to a printer needing the given driver is a big bonus; of course. Please answer to debian-printing@lists.debian.org mentioning the package(s) you would like to care about and/or talk to me over IRC in #debian-printing on irc.debian.org. Looking forward for collaboration, cheers, OdyX
