Re: NMU upload for gdesklets
zufus wrote: > there is a sonsoring request for an NMU on gdesklets: > > http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=gdesklets > > I was wondering if is it OK to upload it as it fixes an RC bug (in case, > I can sponsor the upload) or if there are some work in progress on this > package, and in this case, it might be better to wait (for example to > fix some of the 168 lintian warnings). Treat it as if you were doing the NMU yourself. So The note was only posted to the bug yesterday and it didn't include the patch which it should have done! Karl needs to fix that. The package doesn't appear to be low-NMU so you should wait a few days. Then, if no response upload to delayed and post a deb-diff of the NMU to the bug. regards, Colin -- Colin Tuckley | +44(0)1223 293413 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE Try to learn from other people's mistakes, you haven't time to make them all yourself! - Anon -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: agedu (updated package)
Alexander Prinsier wrote: > I uploaded the new version which fixes the issues below. > > The package can be found on mentors.debian.net: > - URL: http://mentors.debian.net/debian/pool/main/a/agedu > - Source repository: deb-src http://mentors.debian.net/debian unstable > main contrib non-free > - dget http://mentors.debian.net/debian/pool/main/a/agedu/agedu_8642-2.dsc Uploaded as agedu_8642-1 Note that it's not required to update the version number on mentors, only when uploading to the main archive. Otherwise people wonder what has happened to the interim versions Colin -- Colin Tuckley | +44(0)1223 293413 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE A hug is a perfect gift: one size fits all & nobody minds if you exchange it - Ivern Ball -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: agedu (updated package)
Quoting Alexander Prinsier : Is there nobody who wants to sponsor this upload? It's a really basic package, no oddities :) I took a look at this. First, the changelog doesn't say it's a new upstream version, which it appears to be. Second, are the debian/changelog items in the latest entry really what has changed upstream? If so they shouldn't be in debian/changelog. Colin -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: why?
Leinier Cruz Salfran wrote: > I have a package online since 2 weeks ago, I sent 3 RFS and I have found > no sponsor yet. > > why That was about when DebConf was ending. People were busy travelling home and catching up on their other lives I expect. Colin -- Colin Tuckley | +44(0)1223 293413 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE Good advice is something a man gives when he is too old to set a bad example. - La Rochefoucaud -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: basic256 (updated package)
Ryan K. wrote: > I am looking for a sponsor for the new version 0.9.2-3 > of my package "basic256". > > It builds these binary packages: > basic256 - educational BASIC programming environment for children > > The package appears to be lintian clean. I'll take a look at this. A first glance shows that you've altered the changelog entry for 0.9.2-2, (the bit about the standards version change) why? Is the only change really the addition of a watch file? if so then it doesn't really warrant an upload. regards, Colin -- Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE Those who dream by day are cognisant of many things that escape those who dream only by night. - E. A. Poe. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: vidalia
Vern Sun wrote: > The package can be found at: > - dget > http://people.openrays.org/~s5unty/debian/vidalia/0.1.2-1/vidalia_0.1.2-1.dsc The packaging is now good! However, vidalia doesn't work very nicely with the Debian package for Tor. Are you aware of and have you read Item 6 of: https://www.torproject.org/volunteer#Projects As vidalia currently stands it's not really usable with the Debian package for Tor since the user needs to mess about with the configuration of both to get things working. regards, Colin -- Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE "My mind free-associates far too much; I'm going to have to start charging it." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: vidalia
George Danchev wrote: > On Sunday 25 May 2008, Colin Tuckley wrote: >> Finally, this is the first ever Debian package for vidalia so it should >> have a Debian version of -1. > > I consider such requirement quite suboptimal. 1) you kill history 2) even not > being officially published, Please go and read what I said. This package has *never* been in Debian so there is *no* history. Uploading it to mentors doesn't really count since it won't stay there after it's been uploaded to Debian. > Even more to consider: > http://people.debian.org/~codehelp/#increment > and *reasoning* behind. Yes, I know about what Neil has said and while I agree with most of his sponsoring suggestions I disagree with this one. It's more important (in my opinion) that the package history in the archive doesn't have unexplained gaps. Colin -- Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE A door is what a cat is perpetually on the wrong side of. - adapted from Ogden Nash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: vidalia
Vern Sun wrote: > That's great. Updated from version 1.0.2-2~b2 to 1.0.2-2. I've had a look and it mostly looks good. However, as Ansgar said, you have misused the Vcs-* field. Also, your debian/changelog has all of the upstream changelog in it. This is incorrect, debian/changelog is the changelog for the *packaging*. The upstream changelog is already available in the CHANGELOG file so you don't need to repeat it. You just need a single entry stating this is the first Debian package and detailing any changes from upstream that you needed to make. I'm also getting the following lintian warning: W: vidalia: postinst-does-not-load-confmodule N: N: Even if your postinst does not involve debconf, you currently need to N: make sure it loads one of the debconf libraries. This will be changed N: in the future. Finally, this is the first ever Debian package for vidalia so it should have a Debian version of -1. Unfortunately I don't think mentors will let you upload a -1 now that you've uploaded a -2 which is unfortunate. If you have some webspace that you could upload a new -1 package to then please do that and let us know the URL. Having -1 as the first real Debian version means that the orig.tar.gz gets automatically uploaded too and so makes the sponsors job easier. regards, Colin -- Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE "Heisenberg may have slept here" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: vidalia
Vern Sun wrote: > I am looking for a sponsor for my package "vidalia". I'm interested in sponsoring this. I agree with the comments from Michael Schutte, you need to fix those and then I'll take a look. regards, Colin -- Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE Why isn't phonetic spelled the way it is pronounced? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: wordgrinder
David Given wrote: > Ta muchly. Uploaded! regards, Colin -- Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE A fanatic is one who can't change his mind and won't change the subject. - Winston Churchill -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: wordgrinder
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Given wrote: > I am looking for a sponsor for my package "wordgrinder". I've had a quick look, it looks ok. I'll take a closer look tomorrow and if I don't find anything wrong I'll sponsor it for you. > I would be glad if someone uploaded this package for me. It's very > nearly linda and lintian clean (linda complains about me using > Standards-Version 3.7.3, but if I use 3.7.2 then lintian complains that > I'm not using 3.7.3...), and it builds cleanly under pbuilder. That is linda bug #454130 regards, Colin - -- Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE Do not meddle in the affairs of dragons, for you are crunchy and taste good with ketchup. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHkjgsj2OPlhswRc4RAlAGAJ9waVEAMSy1yD+/ZavaWquNHDsVEwCdFtBa IJ/YTl1FvGB/ZO8HzFVbtEs= =3azC -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alpine_1.0+dfsg-2_source.changes REJECTED
Asheesh Laroia wrote: > I'm a Debian Maintainer now Congratulations. > That sort of creeps me out - I'd much rather exercise a buildd and make > sure that a pristine package gets into the archive. It's a bit of a historical thing, left over from the days when everybody used i386 boxes. There is only one i386 buildd (which was down recently). The idea is that since you should be test building your package in a clean sid chroot anyway you might as well upload the results (after signing it of course) to save time on Debian resources. regards, Colin -- Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE Do not meddle in the affairs of dragons, for you are crunchy and taste good with ketchup. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dupload
Jean-Christian BEDIER wrote: > I create this tool myself, but when i try to uplaod this package, i need > a .changes file and i don't know what can i put in this file because > it's the first version of my tool, moreover i don't find information > about the changes files :/ The .changes file is *not* the changelog, although it includes it. If it is a new application then debian/changelog should contain "New Upstream Release" and whatever changes you made to "debianise" the application. The .changes file is generated by dpkg-buildpackage, see the Debian New Maintainers' Guide: http://www.debian.org/doc/maint-guide/ch-build.en.html -- Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE What would life be like if there were no hypothetical questions? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Packages getting created without signature
iluvlinux wrote: > but dpkg-buildpackage command asks for passphrase just before building the > package (at dh_builddeb ). so how can i check it with lintian etc. You can sign it when dpkg-buildpackage asks you. Since you will have to be actually there to do that you can then run lintian to check the package as well. > Do you want that first i should build a package, check it and than use gpg > separately for signing the package? You can do this as an alternative. Also note that unless you are building the package on a Debian box running sid/unstable then you *must also* build it again in a sid chroot using something like pbuilder. You can then use deb-sign to sign the package before you upload it. -- Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE Any sufficiently advanced technology is indistinguishable from magic. - Arthur C. Clarke -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: colordiff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dave Ewart wrote: > Actually, can I leave those references to Graham in for now? > Technically, those bits of the text are part of the 'upstream' program > which (although I am also the author) is not something that would > normally be changed as part of the Debian packaging process. My thought was that they might cause confusion if someone wanted to contact the Debian Developer who uploaded the package. Obviously I was only referring to the "packaging" references and not to the other work he did on the program. There isn't anything that says that the "packaging" process mustn't touch the 'upstream' program, it often has to, the Makefile for instance. All the changes get documented in the .diff.gz for anyone who wants to view them. regards, Colin - -- Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE "Energize!" said Picard and the pink bunny appeared... -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHYZG9j2OPlhswRc4RAlLYAKCNiRobql86DvIrDGTqYS/hLeJWxgCg8f/Q UkXfnGTGWz11+FxwWNbYkYA= =PSlj -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Packages getting created without signature
Peter Pentchev wrote: > Well, there's always gpg-agent, of course... isn't this pretty much > what it was *written* for? :) Yes, but gpg-agent is a short term temporary volatile cache! Which is very different from putting your passphrase in the ENVIRONMENT or a script. -- Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE Try to learn from other people's mistakes, you haven't time to make them all yourself! - Anon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: colordiff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dave Ewart wrote: > Hmm, standards version to 3.7.3? Oh, that must be quite new... I'll > check that out. Yes, in fact so new that I don't think the lintian update has made it into testing yet (you do run lintian -i on your package don't you?). >> Any reason for still using debhelper compat level 4? > > Can you clarify: are you referring to the build-depends on debhelper? No, I'm talking about the value in debian/compat which tells debhelper what compatibility level to use, see the description in the man page for debhelper. You should use level 5 unless there is some reason not to. If you do move to level 5 then you can build depend on debhelper (>= 5.0.0) One additional thing I noticed with the package; it still mentions Graham Wilson as the sponsor in a couple of places in addition to his earlier roles in the development of the package. It's probably easiest to remove references to who sponsored the package rather than having to keep changing it. If you can get those things sorted then I'll upload it for you. I'm also willing to be the regular sponsor. Colin - -- Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE Common Sense is the collection of prejudices acquired by age eighteen. - A. Einstein -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHYGLij2OPlhswRc4RAt7wAKDzqFNjNQYJ09pE5DwFbt/2aRuo2ACfebjt 3KJ8UwdvYFc9DdTzBcVkggc= =XlxI -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: colordiff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dave Ewart wrote: > I'm looking for a new (hopefully long-term) sponsor for colordiff. The > previous sponsor, Graham Wilson, is no longer working on Debian. The standards version needs bumping to 3.7.3 and the changes checking. Any reason for still using debhelper compat level 4? Apart from that it looks like a nice small and simple package and ideal as the first sponsored package for a new DD. Colin - -- Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE APATHY ERROR: Don't bother striking any key. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHYETzj2OPlhswRc4RAtbPAJ9EUmHCbawypUndlPHCBcL0X+ck5gCgxMhX sbaKvA5PtKSJ0W9+pDESr40= =TJfQ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Change in my sponsorship requirements
martin f krafft wrote: > You may have missed my point about merging the changelog entries > when preparing the final version. Until then, having changelog > entries for mentee changes is rather helpful to the sponsor, > I think. No, I saw it and assumed that is what would happen in the case where the uploads use ~r1 etc and the final upload to Debian by the sponsor deleted the extra part of the revision. It's having all the changelog entries for the packaging *attempts* in the final debian package that I'm objecting to. Colin -- Colin Tuckley | [EMAIL PROTECTED] | PGP/GnuPG Key Id +44(0)1903 236872 | +44(0)7799 143369 | 0x1B3045CE "My mind free-associates far too much; I'm going to have to start charging it." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Change in my sponsorship requirements
Bart Martens wrote: > It's not a huge problem, but it's not so nice to have all beginners > mistakes logged forever for the whole world to see. Speaking as someone in NM, that is an important point. I don't use mentors for my uploads, I either use my own web space or a system put in place by my AM which allows me to upload packages to his puiparts system where they get checked. Both mean that I can keep the version the same until it's ready for upload. If I did have to use mentors then I wouldn't mind using the ~r1 idea, with the final uploaded version having that part removed, but I would be against changing the actual Debian revision each time for two reasons. 1) I don't want my failed attempts seen forever. 2) it's a lot of unneeded and irrelevant information. (it's about the packaging *attempt* not about the packaging). Colin -- Colin Tuckley | [EMAIL PROTECTED] | PGP/GnuPG Key Id +44(0)1903 236872 | +44(0)7799 143369 | 0x1B3045CE No trees were harmed during the production of this message, but a large number of electrons were terribly inconvenienced -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: linda errors about doc-base
Colin Tuckley wrote: > > linda says for every file in debian/doc-base: > > > > W: brandy; File not found for field Files in doc-base file > > /usr/share/doc/brandy/README Ah! seems this is bug #368557 Colin -- Colin Tuckley | [EMAIL PROTECTED] | PGP/GnuPG Key Id +44(0)1903 236872 | +44(0)7799 143369 | 0x1B3045CE Experience is the hardest kind of teacher. It gives you the test first, and the lesson afterwards. - Anonymous -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
linda errors about doc-base
I've tried adding doc-base stuff to a package for the first time and I'm getting a linda error that I don't understand, the doc-base documentation hasn't helped. linda says for every file in debian/doc-base: W: brandy; File not found for field Files in doc-base file /usr/share/doc/brandy/README The files do exist and I don't get any errors while running dpkg-buildpackage. The package files are here: http://tuckley.org/debian/brandy_1.20~pre2-1.dsc The package isn't ready for upload to Debian yet because we are still working on the actual application. Can someone tell me what is wrong with my doc-base stuff please. regards, Colin -- Colin Tuckley | [EMAIL PROTECTED] | PGP/GnuPG Key Id +44(0)1903 236872 | +44(0)7799 143369 | 0x1B3045CE There are 10 types of people in the world. Those that know binary, and those that don't. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kqemu package
Adam Borowski wrote: > The problem is, you are not allowed to distribute kqemu. So, the only > thing you will be legally permitted to do with your package will be > installing it on any number of machines under your control. Why not? According to the sourceforge web sites both kqemu and kommander are GPL'd Colin -- Colin Tuckley | [EMAIL PROTECTED] | PGP/GnuPG Key Id +44(0)1903 236872 | +44(0)7799 143369 | 0x1B3045CE "Captain, the tribbles are eating the boards, the dilithium is decrystalizing, the warp core integrity is shot, the engines refuse to talk to me, and -- worst of all -- we're out of duct tape!" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Packaging Qemu Launcher, unmaintained but useful software
Linas Zvirblis wrote: > One late evening browsing trough requested packages in [1] I came across > Qemu Launcher [2]. It is a Perl/Glade front end for QEMU (CPU/computer > emulator). It being the only GTK based application of this kind that I > know of, I decided to give a try packaging it for Debian. > > Then I realized that it is fairly outdated and does not support QEMU 8.0 > (the latest version). The last version of Qemu Launcher seems to be > released somewhere around 3-4 months ago, so I tried contacting the > author (about a month ago and again a few days ago), but got no reply so > far. There also does not seem to be any activity on the project site. The version here: https://gna.org/projects/qemulaunch appears to have work as recent as December, and also mentions work being done on the Debian package in November. regards, Colin -- Colin Tuckley | [EMAIL PROTECTED] | PGP/GnuPG Key Id +44(0)1903 236872 | +44(0)7799 143369 | 0x1B3045CE A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
