Fwd: Packaging php app/scripts
I forgot to cc the list:
-- Forwarded message --
From: Guido van Steen
Date: Tue, Sep 6, 2011 at 10:00 AM
Subject: Re: Packaging php app/scripts
To: kuLa
Hi KuLa,
> I forgot one IMHO important info there is no makefile for this project
> as php is not compilable.
How are you supposed to build/install the package? Can't you adjust
the package to have a - possibly empty - "Makefile.am"s?
> But package_1.0.0.orig.tar.gz created during build process is containing
> all files I need.
Package_1.0.0.orig.tar.gz should be a exact copy of the upstream
tar-ball. Therefore it has to contain all the files needed.
> cp: cannot stat `debian/tmp/src/index.php': No such file or directory
> My whole php app code is in src directory, so all files from this dir
> should be copied into package and they aren't.
It would be handy if you provided the contents of your package as well.
Best wishes,
Guido
On Tue, Sep 6, 2011 at 8:57 AM, kuLa wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 05/09/11 22:20, Igor Pashev wrote:
>> 06.09.2011 00:44, kuLa пишет:
>>> Hi all,
>>> I have simple app in php and would like to package it. Source is in git
>>> (2 branches; upstream and debian, gbp.conf is pointing into these branches).
>>> I used dh_make to debianised package, relevant packages has been edited.
>>> When running git buildpackage final deb package is containing only docs
>>> in usr/share/doc/[package] dir (dh_installdocs i surnning as meant).
>>> When I'm trying to override_dh_install with dh_install --sourcedir=src
>>> I'm still having:
>>> cp: cannot stat `debian/tmp/src/index.php': No such file or directory
>>> My whole php app code is in src directory, so all files from this dir
>>> should be copied into package and they aren't.
>>> But package_1.0.0.orig.tar.gz created during build process is containing
>>> all files I need.
>>> Can anybody point me what should I change to achieve my goal?
>>> Thx for any help in advance.
>>
>> Would be nice if you show all files in ./debian
>> (and its content)
>
> 1st thx for your reply :-)
> I forgot one IMHO important info there is no makefile for this project
> as php is not compilable.
> There is nothing unique in my list of files for this package, I removed
> all files I'm not going to use, *.ex files on the list will be used
> later on.
> List:
> changelog
> compat
> control
> copyright
> docs
> rules
> gbp.conf
> README.Debian
> postinst.ex, postrm.ex, preinst.ex, prerm.ex, glocon.doc-base.EX
>
>
> Content of d/control:
> Source: [app]
> Section: php
> Priority: extra
> Maintainer: kuLa
> Build-Depends: debhelper (>= 7)
> Standards-Version: 3.8.3
> Homepage: http://www.app.com
>
> Package: [app]
> Architecture: any
> Depends: ${shlibs:Depends}, ${misc:Depends}, apache2 (>=2.2.9), php5
> (>=5.2.6)
> Description: GUI allowing to manage and maintain backend application
>
>
> Content of d/gbp.conf:
> [DEFAULT]
> upstream-branch = upstream
> debian-branch = debian
> export-dir=../build
>
> sign-tags = True
> keyid = 0x83adec84
>
>
> Content of d/rules:
> export DH_VERBOSE=1
>
> %:
> dh $@
>
> override_dh_install:
> dh_install --sourcedir=src
> - --
>
> |_|0|_| |
> |_|_|0| "Heghlu'Meh QaQ jajVam" |
> |0|0|0| kuLa - |
>
> gpg --keyserver pgp.mit.edu --recv-keys 0xC100B4CA
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJOZcRJAAoJEOqHloDBALTKPFEH+QEnClEwrJggQgMMb6jn1jZQ
> vVlyamJcDzzJ0aavko3BwNPlb0xpMoQpQ6NtVjXuRejT81AQ5+g+mfa5cJdProWS
> 2ZHMLu5RCi8V+ELN9vPZQorDI6X4eay+R4icWfn5NNLOWeKyYJADwkGLBaFjZQ0w
> PHLcn0NOL4ZfX7/zIAU9Tjd0J/09QAOTr4qWx5NVIIJgluYOFf+5flEEhB2BPvfZ
> LdMaDHTNK1NajfKIfgWoN05OjQmMPi9VTxVf74kiXOmuC/GCd/nv3xDJB3h+v+jJ
> FMBVX1gHpe9k36CzKM4GSej5sCKMp8/FfFV5MohgyLTwTI99hY1bQ7/FfVywc3w=
> =d8XN
> -END PGP SIGNATURE-
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/4e65c449.2020...@kulisz.net
>
>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/camtvz+vpiuokwg9nzatjzoymxr9k6m9z0mbqbrwdqce8ha-...@mail.gmail.com
Re: Packaging php app/scripts
Hi, Kula.
I guess you should
1. list files you want to install in debian/pkg,install:
==
src/script.php dest/dir/
=
2. Use trivial debian/rules (without overrides):
%:; dh$@
3. Do not use ${shlibs:Depends} ;-)
Re: Becoming DM [was: Re: Tracking RFSs as bugs]
On Mon, Sep 5, 2011 at 11:09 PM, Michael Tautschnig wrote: > Could you please be more precise about that last bit? What exactly is hard > about > becoming DM? > > I really wish more people applied for DM. Sponsoring the same package more > than > a few times makes little sense in most cases (there are exceptions, and I for > one are regularly sponsoring at least one such exception). I think that he really wants to say: it is hard to get a (first) package into debian. That is not a problem which is solved by becoming a DM. I have never faced problems finding sponsors for updates of my package, and I don't have the impression that it are those packages which don't find a sponsor. Apart from that: I haven't applied for DM yet because I still found it useful that someone reviews my package prior to uploading. Although one can also argue that that is partly the role of 'unstable'. Johan -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAJOp35=chmkx0pbq1d3o4daunefrmyxojybwvd6_rehvy_h...@mail.gmail.com
Re: Packaging php app/scripts
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/09/11 09:09, Игорь Пашев wrote:
>
> Hi, Kula.
>
> I guess you should
>
> 1. list files you want to install in debian/pkg,install:
> ==
> src/script.php dest/dir/
> =
>
> 2. Use trivial debian/rules (without overrides):
> %:; dh$@
>
> 3. Do not use ${shlibs:Depends} ;-)
Hello again
well I tried what you're suggesting and end up with this:
cp: cannot stat `debian/tmp/src/index.php': No such file or directory
dh_install: cp -a debian/tmp/src/index.php debian/glocon/var/www/
returned exit code 1
make: *** [binary] Error 2
so looks like atm only problem to solve is how to change source dir as
debian/tmp/src/ doesn't exist
- --
|_|0|_| |
|_|_|0| "Heghlu'Meh QaQ jajVam" |
|0|0|0| kuLa - |
gpg --keyserver pgp.mit.edu --recv-keys 0xC100B4CA
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOZdpWAAoJEOqHloDBALTKqckH/j3HwQBY9A8oRUJpBXRNIuQL
GeQu9xcEXXYLdrFfCMdJPsFuowXvRPUwH/xR+6tlDlak8A4ynuC9J/8va3eNBPLz
f0nj3w7WtSvz6Im0mJLObq1qUEDviTsOnaq1bsemfrwRS9LaQzr9AkCcQEdULK1N
ZcKRH02RkJHFot9UcvnixFMnpOcmIHa7YP92yJYsCCHH06Yg/W8FiAMqzOQp5Pfk
pywPifq/GOTDVc/g02LDvZAerksUI/W8UUUuBajjoWS+J4pV4dM+UKFDKuBAvvdC
zEC4phatFqPbHtRXF+qI85RzLi47GLTKW79koY3KIOgNHNi3NLGme07Twy+ppTI=
=0TXN
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e65da56.1010...@kulisz.net
Re: Becoming DM [was: Re: Tracking RFSs as bugs]
Le Tue, Sep 06, 2011 at 10:29:34AM +0200, Johan Van de Wauw a écrit : > > Apart from that: I haven't applied for DM yet because I still found it > useful that someone reviews my package prior to uploading. Although > one can also argue that that is partly the role of 'unstable'. Dear Johan, DM and DDs can also ask for comments on debian-mentors. Cheers, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110906083639.ga7...@merveille.plessy.net
Re: Packaging php app/scripts
Hi! kuLa writes: > > Content of d/control: > Build-Depends: debhelper (>= 7) > > Content of d/rules: > override_dh_install: > dh_install --sourcedir=src for override targets you need debhelper >= 7.0.50~ debhelper 7 isn't enough > dh_install: cp -a debian/tmp/src/index.php debian/glocon/var/www/ Installing into /var/www is a no-go for packages. I'll need to install into /usr/share/$packagename and make sure your webapp can work without the whole lot of scripts located in the documentroot. Regards Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer pgpiImyHFpmiq.pgp Description: PGP signature
Re: Packaging php app/scripts
2011/9/6 Guido van Steen > It would be handy if you provided the contents of your package as well. +1
Re: Tracking RFSs as bugs
Il giorno mar, 06/09/2011 alle 08.12 +0900, Charles Plessy ha scritto: > Le Mon, Sep 05, 2011 at 10:46:11PM +0200, Jakub Wilk a écrit : > > * Michael Tautschnig , 2011-09-05, 20:51: > > >>I've noticed that the release team has a lot of success > > >>addressing their issues in a rather timely manner. I think that > > >>this success comes from the fact that they treat all of the > > >>items they need to accomplish as bugs [0]. So, as requests get > > >>old, they notice that and do something about it (or they just > > >>close it out if the submitter isn't responsive). > > > > This is not a new idea: > > http://lists.debian.org/debian-mentors/2002/08/msg00262.html > > And http://wiki.debian.org/PackageReview :) > I'm really not much active in sponsoring/reviewing, neither in asking for sponsorship/reviews, but my very humble opinion is that _this_ is the right approach, the only "systemic" one that can change things. Except that I would require at least 2 reviews of other packages, not just one. Pietro Battiston -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1315303707.2494.41.ca...@demporaneo.pietrobattiston.it
Re: RFS: getstream
On Mon, Sep 5, 2011 at 13:36, Christoph Egger wrote: > I'm mostly fine with uploading. However I'm wondering about the > licensing. I couldn't find any information about a license apart from a > single file that claims to be taken from the kernel and being GPLv2 (not > GPLv2 or later like in debian/copyright though that doesn't matter > probably as it was Public Domain before). Is there any claim hidden > somwhere that the rest of getstream is GPLv2? There used to be a COPYING file in the original tarball, but it seems to have vanished after getstream-20070419. Author's website states that "Forgot also to license the code. Put the GPL in it." I have contacter the author to make sure it is still in GPL but I have yet not received an answer. Cheers, -- Herve Rousseau -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAAszSUYA2HPM7=z+tdbzqqyyuh9cbwnc-rho0cry6yhcaop...@mail.gmail.com
Re: Packaging php app/scripts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/09/11 09:49, Christoph Egger wrote: > Hi! hello > kuLa writes: >> >> Content of d/control: >> Build-Depends: debhelper (>= 7) >> >> Content of d/rules: >> override_dh_install: >> dh_install --sourcedir=src > > for override targets you need debhelper >= 7.0.50~ debhelper 7 isn't > enough dunno why dh put 7 in there but in real it's 7.4.15 >> dh_install: cp -a debian/tmp/src/index.php debian/glocon/var/www/ > > Installing into /var/www is a no-go for packages. I'll need to install > into /usr/share/$packagename and make sure your webapp can work without > the whole lot of scripts located in the documentroot. I fully agree but for time being I have to do it that way, actually 1st I want to make this working and then will start cleaning it up. As I'm not the upstream but have some influence in that matter. Thus I have to show them that this can be done. So any help with this is appreciated. - -- |_|0|_| | |_|_|0| "Heghlu'Meh QaQ jajVam" | |0|0|0| kuLa - | gpg --keyserver pgp.mit.edu --recv-keys 0xC100B4CA -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOZhAdAAoJEOqHloDBALTKAewH/2k37FcgR42U6FVr5AOSt7sU kQPymspyjAlzfkPmEI0dwyY6lis6lg4ymSRLyRi2SZj5NfJ+o1cWplrjUxHfPMH3 +xBNzsKbxqyMb7JnDpWWLchwAUs/yPeGSqrddEPsTKPKS0njjPcCtAohz775sCi4 nqYAAYvaPfLNwKwDVEdlYkNB4a/RxkB6HvZuyZ+6PBfVgMdcncy5F/6qG3FCH4Jx 6lOmwRqbXoyYtB4YNLZ/0r2OGCc9ySi01uIj78vYJ5Mbyn3Yq9w4LXelvpJ6oNQB UxLncPpUCdOjqdjdb3uDPvpzNzJVY8E3PpXumt8vuPQqfEFfajwOa5YjCKFPuLQ= =v07+ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e66101d.1020...@kulisz.net
Re: Fwd: Packaging php app/scripts
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/09/11 09:03, Guido van Steen wrote:
> I forgot to cc the list:
>
> -- Forwarded message --
> From: Guido van Steen
> Date: Tue, Sep 6, 2011 at 10:00 AM
> Subject: Re: Packaging php app/scripts
> To: kuLa
>
> Hi KuLa,
>
>> I forgot one IMHO important info there is no makefile for this project
>> as php is not compilable.
>
> How are you supposed to build/install the package? Can't you adjust
> the package to have a - possibly empty - "Makefile.am"s?
Ok, I created simple Makefile (content below):
prefix := /tmp
DESTDIR:= $(prefix)/var/www
SRCDIR := ./src
install:
install -d $(DESTDIR)
cp -R $(SRCDIR)/* $(DESTDIR)/
uninstall:
rm -rf $(DESTDIR)/*
>> But package_1.0.0.orig.tar.gz created during build process is containing
>> all files I need.
>
> Package_1.0.0.orig.tar.gz should be a exact copy of the upstream
> tar-ball. Therefore it has to contain all the files needed.
and funny part is it does :-)
>> cp: cannot stat `debian/tmp/src/index.php': No such file or directory
>> My whole php app code is in src directory, so all files from this dir
>> should be copied into package and they aren't.
>
> It would be handy if you provided the contents of your package as well.
np below you've got what I have after unpacking deb:
debian-binary
control.tar.gz
data.tar.gz
when untarring data.tar.gz i have this:
usr/share/doc/glocon/{copyright,README.Debian,changelog.Debian.gz}
and nothing more
> Best wishes,
and you too
- --
|_|0|_| |
|_|_|0| "Heghlu'Meh QaQ jajVam" |
|0|0|0| kuLa - |
gpg --keyserver pgp.mit.edu --recv-keys 0xC100B4CA
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOZhRDAAoJEOqHloDBALTK2nsH/1XAgyRpJId7Qok267xy4nMc
gUYcBRwe4qjplUY9i9GXQzWOm14xNhdKAnpK8HoVsDvAe5sPGHtC+WkDGkgGEbdP
FWJG5hiM3RdcJktCroXBc1WSbbK+2BK+vvO722mQkW82KWmeWhJTFbZNP6xs/3E/
jMYBdSsL3xxIkV7xbCnBixnfT65HDm7g4VkG/W+KUR5Mz1dln+58ay/qYxwHWGmn
0NjlEgzLQD3KpuMCloUGJU52sbWH5FWZZyMhVlMQPzgGCyhz/J5yXcZjoHp/X35t
X0o71MeB9ZEXwR375EkKSfLwWY9QrkmjRLP4bY1x60BULzGnZ5Rk9jyRj7tBWSI=
=JS2D
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e661443.1090...@kulisz.net
RFS: mercurial-server
Dear mentors, I am looking for a sponsor for my package "mercurial-server". * Package name: mercurial-server Version : 1.2-1 Upstream Author : Myself: Paul Crowley * URL : http://www.lshift.net/mercurial-server.html * License : GPL V2 or later Section : devel It builds those binary packages: mercurial-server - shared Mercurial repository service To access further information about this package, please visit the following URL: http://mentors.debian.net/package/mercurial-server Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/mercurial-server/mercurial-server_1.2-1.dsc I would be glad if someone uploaded this package for me. Kind regards, Paul Crowley -- [][][] Paul Crowley [][] LShift Ltd [] [] www.lshift.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e66189b.1010...@lshift.net
Re: Tracking RFSs as bugs
I'm concerned that this might turn out about as useful as filing an RFP bug against wnpp; not very useful at all. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKTje6GGWEk28=WKHq7kXq6os7H=ymcoydvvbvqym0bzfke...@mail.gmail.com
Re: Tracking RFSs as bugs
> I'm concerned that this might turn out about as useful as filing an > RFP bug against wnpp; not very useful at all. > Hmm, not sure - after all, people are still free to remind potential sponsors about outstanding RFS via debian-mentors. Well, and with such a new tracking possibility, e.g., sprints could be organized from time to time. We'd definitively need some more formal assignment of responsibilities for sponsoring. People assigned those responsibilities are required to ask for help from time to time, organize such sprints, send pings for open RFS tagged "more-info" (or close them), work closely with the authors of debexpo, and probably some other tasks that go beyond the basic step of sponsoring uploads. Best, Michael pgpyEJzCB5alJ.pgp Description: PGP signature
Fwd: Packaging php app/scripts
Fwd-ed to the list... -- Forwarded message -- From: Guido van Steen Date: Tue, Sep 6, 2011 at 5:52 PM Subject: Re: Fwd: Packaging php app/scripts To: kuLa > Ok, I created simple Makefile (content below): > prefix := /tmp > DESTDIR:= $(prefix)/var/www > SRCDIR := ./src > > install: >install -d $(DESTDIR) >cp -R $(SRCDIR)/* $(DESTDIR)/ > > uninstall: >rm -rf $(DESTDIR)/* > You may decide to use autotools. This way you make sure everything in your files is more or less standard. I remember trying to package a self-rolled makefile as well. I saw errors everywhere. After I changed to autotools the packaging process went smoothly. Best wishes, Guido
Re: Tracking RFSs as bugs
On Mon, Sep 05, 2011 at 04:49:59PM -0400, Michael Gilbert wrote: > Also, a very useful thing (I think) would be reportbug integration. > Thus submitters would be able to reference their existing ITP > submission and not have to re-enter the same information in their RFS > (this duplication has always irked me about the mentors process). FWIW, debexpo lists the bugs that are closed by the package upload on the package detail page, which should include the ITA/ITP. Since this page should be linked to in your RFS email, this duplication is probably unnecessary. Thanks - Kyle Willmon -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110906175502.gs31...@mail.tuxags.com
Re: Tracking RFSs as bugs
On Mon, Sep 05, 2011 at 01:51:46PM -0700, Don Armstrong wrote: > (I expect it would > have debian-mentors@lists.debian.org as its maintainer, with > mentors.debian.org as the pseudopackage name) Is mentors.debian.org here suggesting that it should be added to the official infrastructure or is this just a typo? Thanks -- Kyle Willmon -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110906175815.gt31...@mail.tuxags.com
Re: Packaging php app/scripts
# find
.
./src
./src/index.php
./debian
./debian/control
./debian/rules
./debian/changelog
./debian/my-pkg.install
./debian/compat
./debian/copyright
# find -type f -exec echo '=== {} ===' \; -exec cat {} \; -exec echo
'---' \;
=== ./src/index.php ===
---
=== ./debian/control ===
Source: my-pkg-src
Section: math
Priority: optional
Maintainer: Igor Pashev
Build-Depends:
debhelper ( >= 8 ),
Standards-Version: 3.9.2
Package: my-pkg
Architecture: all
Depends: ${misc:Depends},
Description: package
---
=== ./debian/rules ===
#!/usr/bin/make -f
%:
dh $@
---
=== ./debian/changelog ===
my-pkg-src (1.2.3-4) UNRELEASED; urgency=low
* Initial release. (Closes: #XX)
-- Igor Pashev Tue, 06 Sep 2011 22:02:10 +0400
---
=== ./debian/my-pkg.install ===
src/index.php usr/share/binary/
---
=== ./debian/compat ===
8
---
=== ./debian/copyright ===
---
# fakeroot ./debian/rules binary
dh binary
dh_testdir
dh_auto_configure
dh_auto_build
dh_auto_test
dh_testroot
dh_prep
rm -f debian/my-pkg.substvars
rm -f debian/my-pkg.*.debhelper
rm -rf debian/my-pkg/
dh_installdirs
install -d debian/my-pkg
dh_auto_install
dh_install
install -d debian/my-pkg/usr/share/binary/
cp -a ./src/index.php debian/my-pkg/usr/share/binary//
dh_installdocs
install -g 0 -o 0 -d debian/my-pkg/usr/share/doc/my-pkg
install -g 0 -o 0 -m 644 -p debian/copyright
debian/my-pkg/usr/share/doc/my-pkg/copyright
dh_installchangelogs
install -o 0 -g 0 -p -m644 debian/changelog
debian/my-pkg/usr/share/doc/my-pkg/changelog.Debian
dh_installexamples
dh_installman
dh_installcatalogs
dh_installcron
dh_installdebconf
install -o 0 -g 0 -d debian/my-pkg/DEBIAN
dh_installemacsen
dh_installifupdown
dh_installinfo
dh_pysupport
dh_pysupport: This program is deprecated, you should use dh_python2 instead.
Migration guide: http://deb.li/dhs2p
/usr/share/python-support/private/movemodules debian/my-pkg
dh_installinit
dh_installmenu
dh_installmime
dh_installmodules
dh_installlogcheck
dh_installlogrotate
dh_installpam
dh_installppp
dh_installudev
dh_installwm
dh_installxfonts
dh_installgsettings
dh_bugfiles
dh_ucf
dh_lintian
dh_gconf
dh_icons
dh_perl
dh_usrlocal
dh_link
dh_compress
cd debian/my-pkg
chmod a-x usr/share/doc/my-pkg/changelog.Debian
gzip -9nf usr/share/doc/my-pkg/changelog.Debian
cd '/home/pashev/tmp/test'
dh_fixperms
find debian/my-pkg -print0 2>/dev/null | xargs -0r chown --no-dereference
0:0
find debian/my-pkg ! -type l -print0 2>/dev/null | xargs -0r chmod
go=rX,u+rw,a-s
find debian/my-pkg/usr/share/doc -type f ! -regex
'debian/my-pkg/usr/share/doc/[^/]*/examples/.*' -print0 2>/dev/null | xargs
-0r chmod 644
find debian/my-pkg/usr/share/doc -type d -print0 2>/dev/null | xargs -0r
chmod 755
find debian/my-pkg/usr/share/man debian/my-pkg/usr/man/
debian/my-pkg/usr/X11*/man/ -type f -print0 2>/dev/null | xargs -0r chmod
644
find debian/my-pkg -perm -5 -type f \( -name '*.so.*' -or -name '*.so' -or
-name '*.la' -or -name '*.a' \) -print0 2>/dev/null | xargs -0r chmod 644
find debian/my-pkg/usr/include -type f -print0 2>/dev/null | xargs -0r
chmod 644
find debian/my-pkg/usr/share/applications -type f -print0 2>/dev/null |
xargs -0r chmod 644
find debian/my-pkg -perm -5 -type f \( -name '*.cmxs' \) -print0
2>/dev/null | xargs -0r chmod 644
find debian/my-pkg/usr/lib/perl5 debian/my-pkg/usr/share/perl5 -type f -perm
-5 -name '*.pm' -print0 2>/dev/null | xargs -0r chmod a-X
dh_strip
dh_makeshlibs
rm -f debian/my-pkg/DEBIAN/shlibs
dh_shlibdeps
dh_installdeb
dh_gencontrol
echo misc:Depends= >> debian/my-pkg.substvars
dpkg-gencontrol -ldebian/changelog -Tdebian/my-pkg.substvars -Pdebian/my-pkg
chmod 644 debian/my-pkg/DEBIAN/control
chown 0:0 debian/my-pkg/DEBIAN/control
dh_md5sums
(cd debian/my-pkg >/dev/null ; find . -type f ! -regex '.*/DEBIAN/.*'
-printf '%P\0' | LC_ALL=C sort -z | xargs -r0 md5sum > DEBIAN/md5sums)
>/dev/null
chmod 644 debian/my-pkg/DEBIAN/md5sums
chown 0:0 debian/my-pkg/DEBIAN/md5sums
dh_builddeb
dpkg-deb --build debian/my-pkg ..
dpkg-deb: сборка пакета «my-pkg» в файл «../my-pkg_1.2.3-4_all.deb».
# dpkg -c ../my-pkg_1.2.3-4_all.deb
drwxr-xr-x root/root 0 2011-09-06 22:11 ./
drwxr-xr-x root/root 0 2011-09-06 22:11 ./usr/
drwxr-xr-x root/root 0 2011-09-06 22:11 ./usr/share/
drwxr-xr-x root/root 0 2011-09-06 22:11 ./usr/share/doc/
drwxr-xr-x root/root 0 2011-09-06 22:11 ./usr/share/doc/my-pkg/
-rw-r--r-- root/root 0 2011-09-06 21:58
./usr/share/doc/my-pkg/copyright
-rw-r--r-- root/root 162 2011-09-06 22:06
./usr/share/doc/my-pkg/changelog.Debian.gz
drwxr-xr-x root/root 0 2011-09-06 22:11 ./usr/share/binary/
-rw-r--r-- root/root 0 2011-09-06 21:58
Re: RFS: eviacam
Hi, I've managed to upload eviacam again to mentors site and appears to be lintian clean. http://mentors.debian.net/package/eviacam Thanks, César El 24/08/2011 0:25, Cesar Mauri escribió: Hi Kilian, Thanks for your review. The file debian/po/templates.pot has a lot of template headers still though. Please fill in all fields that are still holding bogus data. Done. Also added Catalan and Spanish translations. However, every time I run debconf-updatepo this file gets overwritten and so the headers. Is there a way to update this file without losing the headers? Regarding the activation I'd still vote for a group to be created and the chmod to be 4750 if SUID and 0755 if not SUID. You may want to use dpkg-statoverride for this to set both user:group and chmod permissions in one line. If you need a good template I'd need to dig among the last packages I have reviewed. There was a really good postinst doing exactly this. I tried the dpkg-override way (I took mlocate package as reference) but I didn't find a proper way to reset ownership/permissions when the user chooses not SUID without resorting to chown/chmod commands. Thus I left the chown/chmod commands. Your text then should also include the name of the group (probably eviacam) and that the sysadmin should add users if they're supposed to use the program. Done. b) which users should be added to the group interactively I would need some help here. Can you point a good document (or better, an example) on how to interactively add users to a group using debconf? I was thinking of the libc version asking for which processes need to be restarted. Not sure though if that's useful considering that e.g. sudo leaves this to the sysadmin too. I guess we can live with just the SUID-yes and SUID-no question in debconf. OK. Fine for me also. Unfortunately, due to problems with mentors site (I've already contacted the support team to find a solution) I haven't been able to upload the new changes. Once the problems are sorted out I'll ping you again. In the meantime you might find the latest changes in the git repo (sorry for the inconvenience): http://eviacam.git.sourceforge.net/git/gitweb-index.cgi Best regards! Cesar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e66764f.9000...@crea-si.com
RFS: Gkamus
Dear mentors, I am looking for a sponsor for my package "gkamus". this packages already in Ubuntu archive and i suppose to Debian archive too. * Package name: gkamus Version : 1.0-1 Upstream Author: Ardhan Madras , Firmansyah URL : http://gkamus.sourceforge.net/ License : GPL-2+ Section : utils It builds those binary packages: gkamus - Indonesian English dictionary gkamus-dbg - gkamus Indonesian English dictionary (debug) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/gkamus Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/g/gkamus/gkamus_1.0-1.dsc FYI, those package have lintian clear both binary and source. Also i've tested it before. I would be glad if someone uploaded this package for me. Kind regards, Mahyuddin Susanto -- [ Mahyuddin Susanto ] - http://udienz.web.id signature.asc Description: OpenPGP digital signature
svn-buildpackage fail
Hi all, I solved this [1] Now, update new version in changelog, run svn-buildpackage and this fail, used $ svn-buildpackage --svn-ignore these are the errors; 1.- dpkg-checkbuilddeps: warning: can not analyze the dependence libobasis34-en_us-math dpkg-checkbuilddeps: warning: can not analyze the dependence libobasis34-en_us-base dpkg-checkbuilddeps: aviso: no se puede analizar la dependencia libobasis34-en_us-binfilter dpkg-checkbuilddeps: aviso: no se puede analizar la dependencia libobasis34-en_us-writer dpkg-checkbuilddeps: aviso: no se puede analizar la dependencia libobasis34-en_us dpkg-checkbuilddeps: aviso: no se puede analizar la dependencia libobasis34-en_us-calc dpkg-checkbuilddeps: aviso: no se puede analizar la dependencia libobasis34-en_us-res what is this? yes, i use libreoffice out repos, downloaded directly from their page, 2.- dpkg-source: fallo (fail): LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B .pc/01_desktop_file_exec_F.patch/ < decibel-audio-player-1.07.orig.HEjami/debian/patches/01_desktop_file_exec_F.patch devolvió un estado de salida de error 1 This is a patch that is no longer necessary, is corrected in the new version. I do? Just delete it? For not open another thread, 1.- how to update? Standards-Version: debhelper compat only change the numbers? 2.- how to update these in changelog? example; * New upstream release * debian/control: - Standards-Version is 3.9.2, no changes needed. - Add python-imaging to depends. * Removed 01_desktop_file_exec_F.patch completely from debian/patches. is necessary mentioned? debhelper compat Please how? Appreciated help :) [1] http://lists.debian.org/debian-mentors/2011/09/msg00056.html Leonardo. -- L.J.Marín Linux Debian User pgpjIme6h81VN.pgp Description: PGP signature
Re: Becoming DM [was: Re: Tracking RFSs as bugs]
On 06/09/2011 09:29, Johan Van de Wauw wrote: On Mon, Sep 5, 2011 at 11:09 PM, Michael Tautschnig wrote: Could you please be more precise about that last bit? What exactly is hard about becoming DM? I really wish more people applied for DM. Sponsoring the same package more than a few times makes little sense in most cases (there are exceptions, and I for one are regularly sponsoring at least one such exception). I think that he really wants to say: it is hard to get a (first) package into debian. That is not a problem which is solved by becoming a DM. I don't think that is what I wanted to say (though I agree that it is hard to get one's first package into Debian). I think what I meant was that part of the social contract, if I understand correctly, is that we're all here to become DMs/DDs, not just to get our packages uploaded by someone else and walk away. So why is it that DDs sponsor packages and not people? Debian has a steep learning curve - I've been running several Debian systems for ~9 years, packaging for ~2.5 years and still have tons to learn. I would greatly appreciate the ability to correspond with someone about issues which arise for me *before* I have a package ready for review - or even which are only tangentially related to my package(s) but relevant to my broader understanding of Debian and the journey towards DM. FWIW I'd support the use of the BTS for tracking RFSs. For new packages, couldn't it be as simple as tagging ITP bugs as "packaged, uploaded and awaiting review"? (Not sure about upgrades.) Cheers, CC -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e669ea9.4090...@gmail.com
Re: Becoming DM [was: Re: Tracking RFSs as bugs]
Hi Chris, [...] > I think what I meant was that part of the social contract, if I > understand correctly, is that we're all here to become DMs/DDs, not > just to get our packages uploaded by someone else and walk away. So > why is it that DDs sponsor packages and not people? > In the ideal case, and this is largely where I started my sponsoring activities from, I'd only mentor a few people. Indeed I used to have (and sometimes still have) a lot more interaction with the people behind those packages than just the occasional "uploaded." email. I used to ask people what their long-term intentions were, tried to understand their background, etc. It was around the 4-days-proposal that I decided to trade quality for quantity. Sadly, this trade off had to be made. I'd still be happy to mentor (more) people if someone were interested in getting into this mentoring relationship; but so far most people seemed just happy with getting their package uploaded, apparently not caring about more than that. > Debian has a steep learning curve - I've been running several Debian > systems for ~9 years, packaging for ~2.5 years and still have tons > to learn. I would greatly appreciate the ability to correspond with > someone about issues which arise for me *before* I have a package > ready for review - or even which are only tangentially related to my > package(s) but relevant to my broader understanding of Debian and > the journey towards DM. > As said above: I for one would be perfectly fine to offer this kind of mentoring to you. I'm not sure whether you had ever had a negative answer to such a request for mentorship - have you ever asked for it (before)? > FWIW I'd support the use of the BTS for tracking RFSs. For new > packages, couldn't it be as simple as tagging ITP bugs as "packaged, > uploaded and awaiting review"? (Not sure about upgrades.) > I believe the workflow could be implemented as simply reassigning the ITP to the proposed mentors.debian.(org|net) pseudo-package. No need for extra tagging, it would all come for free. Best, Michael pgpsmfcOmc95i.pgp Description: PGP signature
RFS: mail-notification (updated package; NMU for RC bugs among others)
Dear mentors, I am looking for a sponsor for the package "mail-notification". This update would fix a couple of RC bugs (the usual Evolution updates, which also require a switch to GTK+ 3); I've also included a number of fixes for bugs with patches in the BTS, and activated SSL support. (See the m.d.n link below for the list of bugs fixed.) Note that this is an NMU, so far with no reaction from Qi (I mentioned the patches for the RC bugs only yesterday, but the bugs involved have had no reaction at all). It builds these binary packages: mail-notification - mail notification in system tray mail-notification-evolution - evolution support for mail notification To access further information about this package, please visit the following URL: http://mentors.debian.net/package/mail-notification Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/mail-notification/mail-notification_5.4.dfsg.1-2.5.dsc I would be glad if someone uploaded this package for me. Kind regards, Stephen Kitt -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110906225703.gh28...@sk2.org
Re: RFS: mail-notification (updated package; NMU for RC bugs among others)
Am 07.09.2011 00:57, schrieb Stephen Kitt: Dear mentors, I am looking for a sponsor for the package "mail-notification". This update would fix a couple of RC bugs (the usual Evolution updates, which also require a switch to GTK+ 3); Hm, the package still build-depends on libgtk2.0-dev, is that an oversight? Also, the package seem to still use a lot of deprecated GNOME 2 libs, like libgnomeprintui2.2-dev, libgnomevfs2-dev and libgnome2-dev. Are they still required? If so, you should consider porting them to the newer interfaces, like GVFS. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e66be39.4010...@debian.org
Re: RFS: mail-notification (updated package; NMU for RC bugs among others)
Hi Michael, On Wed, 07 Sep 2011 02:43:37 +0200, Michael Biebl wrote: > Am 07.09.2011 00:57, schrieb Stephen Kitt: > > I am looking for a sponsor for the package "mail-notification". This > > update would fix a couple of RC bugs (the usual Evolution updates, > > which also require a switch to GTK+ 3); > > Hm, the package still build-depends on libgtk2.0-dev, is that an oversight? It's only needed for gtk-builder-convert; I suppose I could just provide the .ui files in a patch, but I'd rather build everything from the original sources as far as possible. > Also, the package seem to still use a lot of deprecated GNOME 2 libs, > like libgnomeprintui2.2-dev, libgnomevfs2-dev and libgnome2-dev. > Are they still required? If so, you should consider porting them to the > newer interfaces, like GVFS. OK - do you have any pointers to migration documentation? The main intent of the NMU was to fix the FTBFS, not really overhaul the whole package, but it would indeed be better to avoid leaving predictable future FTBFSes... Thanks for looking at the package, Stephen -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110907081243.098fc...@sk2.org
