Re: Joining the team?

[Till Kamppeter]

On 06/18/2011 06:52 AM, Rogério Brito wrote:

Hi there.

I didn't even know that this team existed (I only noted this today after I
saw the maintainer of the epson-escpr package).



We are not only trying to take more care of Debian's printing stack but 
also to join forces for Debian and Ubuntu packaging of printing stuff.



I have some interest in printing stuff, and I currently keep the package
magicfilter, as I am not exactly a fan of cups (partly, perhaps, because of
lack of the understanding together with some troubles in the past) and I
like the lprng system of doing things.



Why Magicfilter? It is not maintained upstream any more for decades 
(1996 it was already 1.2 and it still is). You can replace it by 
Foomatic (I did not remove LPRng support) which is maintained upstream 
by me and used by many driver authors, even printer manufacturers. 
Especially it is based on PPD files and so it supports every PostScript 
printer perfectly.



Seeing as we have a team, I think that this would give me some incentives to
better manage my packages and to learn about other printing solutions.

So, how is the status of the team?


You are welcome to join the team and discuss the work on 
printing-related packages and ask for help here.


   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/4dff7a10.80...@gmail.com

Re: Packaging pxljr

[Henry velez]

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