Debian Packaging Workshop at COEP Jan 2017

I am packaging aproba

I am packaging console-control-strings

hoek

You have to fix the description, it was rejected by ftp masters.

I am packaging aws4

node-aws4 was rejected by ftp masters, they have replied with a comment. Can you update your package?

I am packaging aws-sign2 (0.6.0).

Can you fix your package? It is missing some copyright notices. You can run licensecheck --deb-machine -l0 -r to see license statements of all files in your package.

I am packaging has-unicode

Amarpreet :
json-schema

I am packaging jsbn.

i am packaging tweetnacl

I'm packaging assert-plus

I am packaging call-signature

Your package was rejected. Can you fix it?

I'm packaging extsprintf

asynckit

I am packaging binary-extensions

I am packaging common-path-prefix

I'll be packaging caseless

I am packaging clean-yaml-object

i am packaging asn1

tough-cookie

Your package node-imurmurhash was rejected. Please fix copyright and description.

I am doing is-error

I am packaging fn-name

I am packaging is-obj

Packaging "arrify

ci-Info under packaging....

is-generator-fn

slice-ansi

I am packaging stringstream(0.0.5)

I am packaging plur(2.1.2)

I am packaging 'buf-compare'

I am packaging md5-hex

I am taking single-line-log

term-size

I am packaging throttleit

I am packaging caller

I am packaging require-inject

"I've responded to a few of these ITPs and have found the responses I've
received suggest that you've chosen your recruits well, so it strikes me
as a shame that they are underselling themselves by submitting ITPs in
this state."

Philip Hands on debian-devel list,

https://lists.debian.org/debian-devel/2017/01/msg00283.html

Some good words for all of you and important advice, be careful about descriptions in ITPs too. Feel free to ask for help if you can't find a good description

Where have the photos disappeared?

Sir, photos are there on the pre-requisites page.

If any rfs is waiting for review/upload, please contact me. Also please contact me if you have not yet found a software to package, I will suggest some software for you to package.

Next steps for those who are serious about maintaining packages:

1. Install debian sid on your main machines (dual boot will do).
2. Configure your mail clients for gpg. See https://emailselfdefense.fsf.org/en/ for setting up thunderbird + enigmail for your laptop and see https://k9mail.github.io/documentation/security/pgpmime_current.html for setting up K9 Mail with Open Keychain.

@amarpreetsingha can you fix email address in your package's control file?

Those who created their keys on your phones may import your keys to your laptops using this guide https://www.openkeychain.org/faq/#how-to-import-an-openkeychain-backup-with-gpg It will allow you to use your key on your laptop too (you'll need it when you are ready to upload your packages yourself without a sponsor). It will also serve as a backup in case you lose your keys on the phone like @abhishekkuvalekar (he had to reinstall his phone and lost his keys).

If your request to join pkg-javascript team is accepted, follow the steps below to import your package to alioth. Import all your packages to alioth and use it directly for all future packages (we were using git.fosscommunity.in only as a temporary option till we got access to alioth).

1. Configure your alioth username in ~/.ssh/config and add ssh keys to alioth. See link below. https://wiki.debian.org/Alioth/SSH#How_to_handle_differing_username
2. Remove origin from your existing repos. git remote remove origin
3. gbp create-remote-repo --remote-url-pattern='git+ssh://git.debian.org/git/pkg-javascript/%(pkg)s.git' (I have saved this command as js-create-repo). This will create a repo in alioth and push your changes there. Make sure your directory name is same as package name (it starts with node-) and also the debian/xyz-1 tag is pointing to latest commit. (git tag -d debian/xyz-1; git push origin :debian/xyz-1; git tag debian/xyz-1)

Before sending an RFS, please check you can install the package correctly using dpkg -i (you'll know if its dependencies are packaged or not). If a dependency is available from experimental, enable experimental in your sources.list and install it. If a dependency is available in NEW, gbp clone (with --pristine-tar option) the repo from alioth (all repo addresses follow the same pattern, differing only by the actual package name), build the package locally and install it.