Re: Empty binary package
On 20-07-13 06:31, T o n g wrote: On Sat, 20 Jul 2013 03:11:46 +, T o n g wrote: That part was fully clear to me. And as I said, in my tries it was always there. So you did the above normal steps as building any binary package but get different result? Or did you do something more than normal? My bad. Revisiting my work log, I suddenly realized the source package that I built from is not the one that I built from the upstream source but my already tweaked one. So, good. By telling us exactly what you did, you already found the issue yourself. This often happens to me, that is why I want people to explain extensively what they did. Are you saying changing the line binary: binary-indep binary-arch into: binary: binary-indep # binary-arch to remove the second binary build target? [ . . .] No. If you talked about the build %: dh $@ Yes, I was talking about this line. The build target was already present, so now it is double. I am not sure what make is supposed to do with that situation. line, I put them there because I want to fix the following lintian issues: W: libpam-ssh-agent-auth source: debian-rules-missing-recommended- target build-arch W: libpam-ssh-agent-auth source: debian-rules-missing-recommended- target build-indep How else should I fix it then? So this is the remaining issue for me so far (As you can see I've tried to find the answer myself and using the build %:\n\tdh $@ is the answer that I found). Good, you tried and are now asking a specific question. I guess your answer can be the answer, but the way you applied it not the correct one. My suggestion is to either: - Convert your full rules file to short dh(1) style (that would be *my* preference) - Simple: add the build-arch and build-indep targets yourself. If I am not mistaken, with this specific rules file, you can just add them, depend on the build target and do nothing in the target itself. Paul signature.asc Description: OpenPGP digital signature
Bug#675532: RFS: bilibop/0.1 (ITP #675467)
Hi,
and thanks for this review
On 19/07/2013 20:25, intrigeri wrote:
First, was the target distribution change in debian/changelog
intentional? (0.4.12 has experimental, 0.4.13 has unstable.)
Yes it is; the target distribution was set to experimental for the
wheezy's freeze duration... after what it was forgotten. Do you think
I should revert to experimental ?
Second, it looks like important changes and refactoring are flowing in
rather quickly, so I'd like to check that you are confident with the
current state of bilibop, and believe it is stable enough to be part
of a Debian release. Do you confirm this?
The most important changes are about debconf support, which has been
added to bilibop-rules. I consider this as an improvement. Maintainer
scripts are idempotent. I have tested bilibop-rules 0.4.13 installation
in several ways: fresh install (with or without preseeding it), upgrade
from 0.4.11, remove, reinstall, purge: all seems to work as expected.
Other things are mainly addition of comments in the shell library,
update of the documentation, and some changes in the code to take into
account some very specific usecases.
So yes, I am confident with the current state of bilibop (but yes, this
was not the case with 0.4.12 - less than one day of lifetime!). Also
note that bilibop is still in active development, and some enhancements
are planned for the next months or even next years; of course, important
attention is given to not break existing things.
Also, please keep in mind that once bilibop is uploaded to Debian, the
responsibility of backward compatibility will be yours, as the
maintainer. This being said, while I certainly wouldn't mind a bit
more abstraction / factorization at some places, the code looks solid
enough :)
Some nitpicking follows, that should be fixed before the initial
upload IMHO:
+myshell=$(awk -F: \$1 ~ /$(whoami)/ {print \$NF} /etc/passwd)
Maybe use `getent' instead?
Fixed.
Also Lintian says:
I: bilibop-common: spelling-error-in-manpage
usr/share/man/man1/drivemap.1.gz informations information
... and a few others, so you probably want to run it in verbose /
pedantic mode and take the results into account.
Mh... I already used '--info --verbose --pedantic' in my script. I
thought it was enough, as mentors.debian.net/package/bilibop says
'Package is lintian clean'.
The tags you mention are catched by '--display-info'. Fixed.
So, here is the new version:
http://mentors.debian.net/debian/pool/main/b/bilibop/bilibop_0.4.14.dsc
Cheers
quidame
signature.asc
Description: OpenPGP digital signature
Re: Empty binary package
On Sat, 20 Jul 2013 08:26:48 +0200, Paul Gevers wrote: line, I put them there because I want to fix the following lintian issues: W: libpam-ssh-agent-auth source: debian-rules-missing-recommended- target build-arch W: libpam-ssh-agent-auth source: debian-rules-missing-recommended- target build-indep How else should I fix it then? [...] I guess your answer can be the answer, but the way you applied it not the correct one. My suggestion is to either: - Convert your full rules file to short dh(1) style (that would be *my* preference) No, I'm incapable of doing that for now. Even your simple answer gave me a hard time trying to understand it. I'll ask in a separated thread to see if anyone willing to help. - Simple: add the build-arch and build-indep targets yourself. If I am not mistaken, with this specific rules file, you can just add them, depend on the build target and do nothing in the target itself. After a bit of struggle, I think these are the changes to the debian/ rules in your mind, right? -build: build-stamp +build: build-arch build-indep +build-arch: build-stamp +build-indep: build-stamp build-stamp: config.status Thanks again. -- 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/kse6sr$144$1...@ger.gmane.org
Re: RFS: new powertop version
Hi, I update the package to version 2.4. A build of the package can be found under [0], the git repo of the package is under [1]. Best regards, Julian [0] http://rbw.goe.net/jw/debian/pool/powertop/ [1] http://anonscm.debian.org/gitweb/?p=users/jw-guest/powertop.git -- 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/20130720180315.2b8da644@ilfaris
Re: Empty binary package
On 20-07-13 16:29, T o n g wrote: - Simple: add the build-arch and build-indep targets yourself. If I am not mistaken, with this specific rules file, you can just add them, depend on the build target and do nothing in the target itself. After a bit of struggle, I think these are the changes to the debian/ rules in your mind, right? -build: build-stamp +build: build-arch build-indep +build-arch: build-stamp +build-indep: build-stamp build-stamp: config.status Pretty close, but this is even better I think. Looking at the policy [1], you might even do completely nothing (and no dependencies) in the build-indep target, as you don't build any all package. Paul [1] http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules signature.asc Description: OpenPGP digital signature
Bug#706514: RFS: dcraw/9.17-1
Hi Oliver, [Quoting your private mail to me, hoping there is nothing private] 2013/7/19 Oliver Sander san...@igpm.rwth-aachen.de: You want to upload a newer version without intend to maintain it. Right? No. I made up my mind and I promise to be the dcraw maintainer if that is what it takes. The package cannot be adopted now as it is not yet orphaned. CC-ing MIA-team, as, it seems, the current maintainer Steve King is not active in Debian any more. He was CC-ed several times in this bug-thread without any reaction from his side. Yes, but pay attention, NMU is only for critical bug-fixes. Not for new versions or minor changes. See Debian Policy. A new package has been uploaded, which now has the version 9.19-1. Gregor is right, we can do NMU with the new version of the package (thanks him). Sorry for confusing, I did not know that. I have changed your debian/changelog accordingly. See above. The actual maintainer added those files to the package, and I don't really know what they do. But just because _I_ don't know what they do that doesn't mean they don't serve a purpose. That's why I kept them in. gpg_key is not in a current version of dcraw [1], [2]. Wow, you are right! That must be my own gpg_key which must have crept in there silently when I created it for packaging. Sorry for screwing this up. It's gone now. .badpixels, as i understand should not be in a package either, as it is camera-specific file [3]. Why then should it be in the package? As I said: no clue, it wasn't me who put it there. It is also gone now. What's next? Ok, I have uploaded the package. Thanks for contributing! I hope you have learned something from this cooperation. I did not use DELAYED-queue as the original maintainer had enough time to react. Hope, you will continue you work on Debian! Best regards, Anton -- 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/calf6qjm3kse8vpiezuelyagbjy+zdoibygrdt+ssn9ttfvs...@mail.gmail.com
Bug#706514: marked as done (RFS: dcraw/9.19-1)
Your message dated Sat, 20 Jul 2013 19:58:52 +0300 with message-id calf6qjm3kse8vpiezuelyagbjy+zdoibygrdt+ssn9ttfvs...@mail.gmail.com and subject line Re: Bug#706514: RFS: dcraw/9.17-1 has caused the Debian Bug report #706514, regarding RFS: dcraw/9.19-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 706514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package dcraw * Package name: dcraw Version : 9.17-1 Upstream Author : Dave Coffin, dcoffin a cybercom period net * URL : http://www.cybercom.net/~dcoffin/dcraw/ * License : GPL v2 Section : graphics It builds those binary packages: dcraw - decode raw digital camera images To access further information about this package, please visit the following URL: http://mentors.debian.net/package/dcraw Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/d/dcraw/dcraw_9.17-1.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: * New upstream release (Closes: #617543) * Build-depend on libjasper-dev Regards, Oliver Sander ---End Message--- ---BeginMessage--- Hi Oliver, [Quoting your private mail to me, hoping there is nothing private] 2013/7/19 Oliver Sander san...@igpm.rwth-aachen.de: You want to upload a newer version without intend to maintain it. Right? No. I made up my mind and I promise to be the dcraw maintainer if that is what it takes. The package cannot be adopted now as it is not yet orphaned. CC-ing MIA-team, as, it seems, the current maintainer Steve King is not active in Debian any more. He was CC-ed several times in this bug-thread without any reaction from his side. Yes, but pay attention, NMU is only for critical bug-fixes. Not for new versions or minor changes. See Debian Policy. A new package has been uploaded, which now has the version 9.19-1. Gregor is right, we can do NMU with the new version of the package (thanks him). Sorry for confusing, I did not know that. I have changed your debian/changelog accordingly. See above. The actual maintainer added those files to the package, and I don't really know what they do. But just because _I_ don't know what they do that doesn't mean they don't serve a purpose. That's why I kept them in. gpg_key is not in a current version of dcraw [1], [2]. Wow, you are right! That must be my own gpg_key which must have crept in there silently when I created it for packaging. Sorry for screwing this up. It's gone now. .badpixels, as i understand should not be in a package either, as it is camera-specific file [3]. Why then should it be in the package? As I said: no clue, it wasn't me who put it there. It is also gone now. What's next? Ok, I have uploaded the package. Thanks for contributing! I hope you have learned something from this cooperation. I did not use DELAYED-queue as the original maintainer had enough time to react. Hope, you will continue you work on Debian! Best regards, Anton---End Message---
Re: Empty binary package
On Sat, 20 Jul 2013 18:17:20 +0200, Paul Gevers wrote: I think these are the changes to the debian/rules in your mind, right? [ . . . ] Pretty close. . . Thanks a lot again Paul for all the helps you gave. My sponsor request has been sitting there for a while, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716852 even though I've been actively inviting people to look into it. Would you mind sponsor for me please? Thanks -- 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/ksf2ou$ok7$1...@ger.gmane.org
Bug#716852: RFS: libpam-ssh-agent-auth/0.9.5-2.2 [ITP]
Dear mentors, I am looking for a sponsor for my package libpam-ssh-agent-auth. I'v already sent the sponsor request previously, ref, http://lists.debian.org/package-sponsorship-requests/2013/package-sponsorship-requests-201307/msg00087.html This is a new upload. * Package name: libpam-ssh-agent-auth Version : 0.9.5-2.2 Upstream Author : Jamie Beverly soup...@sourceforge.net * URL : http://sourceforge.net/projects/pamsshagentauth/ * License : BSD License Section : libs It builds those binary packages: libpam-ssh-agent-auth - PAM Authentication via forwarded ssh-agent To access further information about this package, please visit the following URL: http://mentors.debian.net/package/libpam-ssh-agent-auth Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/libp/libpam-ssh-agent-auth/libpam-ssh-agent-auth_0.9.5-2.2.dsc More information about libpam-ssh-agent-auth can be obtained from http://sfxpt.wordpress.com/libpam-ssh-agent-auth/. Changes since the last upload: libpam-ssh-agent-auth (0.9.5-2.2) unstable; urgency=low * Fixes so as to build the binary package properly Regards, Tong Sun PS. Please CC me when replying. Thanks -- 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/cammz1odxnbwb5qtujxb6cpqleyu6ntc8dqnzc5zlugancjq...@mail.gmail.com
Bug#716852: Fwd: Bug#716852: RFS: libpam-ssh-agent-auth/0.9.5-2.2 [ITP]
Dear mentors, I am looking for a sponsor for my package libpam-ssh-agent-auth. I'v already sent the sponsor request previously, ref, http://lists.debian.org/package-sponsorship-requests/2013/package-sponsorship-requests-201307/msg00087.html This is a new upload. * Package name: libpam-ssh-agent-auth Version : 0.9.5-2.2 Upstream Author : Jamie Beverly soup...@sourceforge.net * URL : http://sourceforge.net/projects/pamsshagentauth/ * License : BSD License Section : libs It builds those binary packages: libpam-ssh-agent-auth - PAM Authentication via forwarded ssh-agent To access further information about this package, please visit the following URL: http://mentors.debian.net/package/libpam-ssh-agent-auth Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/libp/libpam-ssh-agent-auth/libpam-ssh-agent-auth_0.9.5-2.2.dsc More information about libpam-ssh-agent-auth can be obtained from http://sfxpt.wordpress.com/libpam-ssh-agent-auth/. Changes since the last upload: libpam-ssh-agent-auth (0.9.5-2.2) unstable; urgency=low * Fixes so as to build the binary package properly Regards, Tong Sun PS. Please CC me when replying. Thanks -- 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/CAMmz1Odg3NOHC_VLU6u=zjx7bb-ok75qxl9ybpiev1+h8-3...@mail.gmail.com
Bug#717123: RFS: superkb/0.22-5 [ITP #647877] -- keyboard launcher with on-screen hints
Hi. I uploaded a new version for Superkb, the package for which I'm trying to get sponsorship. The new version is 0.22-5 and this is what I changed: superkb (0.22-5) unstable; urgency=low * Added lintian override for no-upstream-changelog, because it is not in English and this has been fixed upstream. Next upstream release will properly include a changelog and this override will be removed. * Fixed man page invocation to help2man for proper text in the NAME section. * Moved sample-config/superkbrc to debian/ and removed the patch. * Include sample config files under /usr/share/doc/superkb/sample-config. * Improved man page superkb.1. So, technically, the package has no more lintian --pedantic warnings unattended, and hopefully the next upstream version will have most patches directly incorporated (because upstream is me) so the package will become simpler in the future. Even though I'm asking for sponsorship, I'd really appreciate a review even if it's not sponsored. Thanks in advance. Octavio. -- 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/op.w0jzqx0w4oyyg1@alvarezp-samsung
Bug#702174: marked as done (RFS: estonianidcard/3.7.0.1116-1 [ITP] -- Estonian ID card support packages)
Your message dated Sun, 21 Jul 2013 04:23:30 + with message-id e1v0lbc-00061n...@quantz.debian.org and subject line closing RFS: estonianidcard/3.7.0.1116-1 [ITP] -- Estonian ID card support packages has caused the Debian Bug report #702174, regarding RFS: estonianidcard/3.7.0.1116-1 [ITP] -- Estonian ID card support packages to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 702174: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702174 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for a suite of packages for Estonian ID card support. ID card is used extensively in Estonia for authentication and signing digital documents both for public and private sector services. Currently packages are available for Fedora, Ubuntu, openSuse, osx and Windows but not for Debian. * Package name: estonianidcard Version : 3.7.0.1116-1 Upstream Author : i...@ria.ee * URL : http://www.ria.ee/ * License : LGPL 2.1 Section : misc As upstream distributes the components separately, currently the proposed Debian packages are also split in the same way (separate source packages): qesteidutil QT card management utility (certificates and pins but also personal details) qdigidoc QT signing and encryption utiltiy esteidfirefoxplugin enables authentication and document signing in the browser libdigidoc libdigidocpp support libraries for digidoc documents esteidpkcs11loader browser helper to set up authentication and signing authorities and pkcs11 plugin esteidcerts CA, intermediate and OCSP certficates for esteid cards estonianidcard metapackage to install all the above mentioned packages The source packages are provided by the Estonian Information System's Authority, currently at version 3.7.0 (plus a per-component release number that varies) and are available at: http://ftp.ria.ee/pub/id/signed_repository/ mentors.debian.net links for all the source packages: http://mentors.debian.net/package/estonianidcard http://mentors.debian.net/package/qdigidoc http://mentors.debian.net/package/qesteidutil http://mentors.debian.net/package/esteidfirefoxplugin http://mentors.debian.net/package/esteidpkcs11loader http://mentors.debian.net/package/libdigidoc http://mentors.debian.net/package/libdigidocpp http://mentors.debian.net/package/esteidcerts dget commands to download the packages: dget -x http://mentors.debian.net/debian/pool/main/e/estonianidcard/estonianidcard_3.7.0.1116-1.dsc dget -x http://mentors.debian.net/debian/pool/main/q/qdigidoc/qdigidoc_3.7.0.996-1.dsc dget -x http://mentors.debian.net/debian/pool/main/q/qesteidutil/qesteidutil_3.7.0.907-1.dsc dget -x http://mentors.debian.net/debian/pool/main/e/esteidfirefoxplugin/esteidfirefoxplugin_3.7.0.931-1.dsc dget -x http://mentors.debian.net/debian/pool/main/e/esteidpkcs11loader/esteidpkcs11loader_3.7.0.869-1.dsc dget -x http://mentors.debian.net/debian/pool/main/libd/libdigidoc/libdigidoc_3.7.0.912-1.dsc dget -x http://mentors.debian.net/debian/pool/main/libd/libdigidocpp/libdigidocpp_3.7.0.972-1.dsc dget -x http://mentors.debian.net/debian/pool/main/e/esteidcerts/esteidcerts_3.7.0.8890-1.dsc These are all NEW packages, closing their ITP bugs. Regards, Siim Põder ---End Message--- ---BeginMessage--- Package estonianidcard has been removed from mentors.---End Message---
