Re: RFS: lusernet.app (updated package)
However, your package is really good and it would be really bad to waste the good work you made, so CC'ing him. Although he is maybe busy until next Monday, he's a friendly guy and will answer you quickly :P I think he will offer you co-maintainership, and if so, I'll sponsor the upload if you want. Yes he is co-maintaining the package, please sponsor this package. Yours, Gürkan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Version 1 accidentally released as version 2...
On Thu, Sep 28, 2006 at 11:14:36AM +1000, Matthew Palmer wrote: On Thu, Sep 28, 2006 at 09:33:46AM +0900, Charles Plessy wrote: OK, thanks all for your answers. I will mention the problem in the README. How can I give a message only to the users who upgrade from the previous version? I do not want to annoy the ones who will install from Etch next year... If you put in NEWS.Debian (it has the same format as debian/changelog, you can even use dch to edit it) then people who are using apt-listchanges and are upgrading from a version older than the version in which the news was logged against will see the message. But that's not what he wants, because then all the people who upgrade to etch with also see it then, even though it's irrelevant for them. What he's asking is if there's a way to show it only if the upgrade is from a high enough version. If the message is important enough for a debconf note, you can use that (and display it depending on a version check in the config script). You shouldn't use debconf notes if the user doesn't actually need to do anything though. (that is, notes are annoying and should only exist because something important is happening, where some action is required from the user.) Thanks, Bas -- I encourage people to send encrypted e-mail (see http://www.gnupg.org). If you have problems reading my e-mail, use a better reader. Please send the central message of e-mails as plain text in the message body, not as HTML and definitely not as MS Word. Please do not use the MS Word format for attachments either. For more information, see http://129.125.47.90/e-mail.html signature.asc Description: Digital signature
Re: RFS: lusernet.app (updated package)
Gürkan Sengün wrote: Yes he is co-maintaining the package, please sponsor this package. done. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Version 1 accidentally released as version 2...
Le Thu, Sep 28, 2006 at 12:19:04PM +0200, Bas Wijnen a écrit : But that's not what he wants, because then all the people who upgrade to etch with also see it then, even though it's irrelevant for them. What he's asking is if there's a way to show it only if the upgrade is from a high enough version. Luckily, the situation is simpler: the package has been created recently, and six popcon-persons installed it. Only one version of the debian package has been released for the moment (i.e. the changelog has only one entry). I would like the persons upgrading to see the message and the people installing for the first time not seeing it. Will NEWS.Debian fit this purpose? Have a nice day, -- Charles -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: lusernet.app (updated package) [sponsored]
В Thu, 28 Sep 2006 12:35:26 +0200, Daniel Baumann написа: Gürkan Sengün wrote: Yes he is co-maintaining the package, please sponsor this package. done. Thank you very much. It seems that someone removed it from m.d.n before I manage to do so, that's good. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Version 1 accidentally released as version 2...
On Thu, Sep 28, 2006 at 07:36:36PM +0900, Charles Plessy wrote: Le Thu, Sep 28, 2006 at 12:19:04PM +0200, Bas Wijnen a écrit : But that's not what he wants, because then all the people who upgrade to etch with also see it then, even though it's irrelevant for them. What he's asking is if there's a way to show it only if the upgrade is from a high enough version. Luckily, the situation is simpler: the package has been created recently, and six popcon-persons installed it. Only one version of the debian package has been released for the moment (i.e. the changelog has only one entry). I would like the persons upgrading to see the message and the people installing for the first time not seeing it. Will NEWS.Debian fit this purpose? Yes. - Matt
Re: gnome-app-install (super-easy package manager) prototype
Le jeudi 28 septembre 2006 06:51, Jason Spiro a écrit : Hi all, My question is in the last paragraph of this email. Progress note: I am working on a port of gnome-app-install to Debian. This utility, made by the folks at Canonical Inc. and Ubuntu, is like Synaptic, but ten times easier to use. Good news, it's fine for noobs :-) It currently does the job but does not always quit after an install operation is finished. Known issues include internationalization, missing icons, the OK button and it currently fails if you try to install anything in non-free. (If you try it, it'd be great if you could let me know, either here or by email, whether the icons in the Popularity column look like little stars or little X-squares. You can install it using the following sources.list lines:) I'll have a look, dunno if I can help... deb http://www.jspiro.com/files/debian experimental/ deb-src http://www.jspiro.com/files/debian experimental/ Why don't you upload it to mentors.debian.net ? I am frustrated at the various bugs I'm seeing but I don't want to give up, as I want gnome-app-install to be in Debian. If you would like to finish packaging the app and take over maintainership, I'd be very glad to stop here and explain to you the changes I've made already. Don't forgive, if people would have stop each time they thought it's too hard, GNU/Linux would not exists ;-) I can help you for the packaging for sure, and maybe for the port. If it's not enough we should run a project @ alioth en try to find some other developpers ! Now for my question: I am working from an upstream .tar.gz file from Ubuntu. The upstream tarball includes .pyc files too, not just .py files. My .diff.gz does not touch the .pyc files when applied to the upstream source. Will this be a problem when people try to apply the .diff? Hmmm... Here is what I think. There are two case : * The original apps is only for ubuntu, you had to makes LOTS OF change in it to get it runnng on Debian. Then I would suggest to fork the project, so you'll recreate a new tarball. * The patches are not su huge and you can handle them through dpatch or quilt. Just leave the upstream tarball as it was but DO NOT INSTALL pyc files. (and report the issue to upstream). Thanks for being here to listen. Jason Spiro NP, Adam. -- The church is near but the road is icy; the bar is far away but I will walk carefully. -- Russian Proverb
Re: [Fwd: RFS: libmtp] (reminder)
Op di, 26-09-2006 te 16:20 +0100, schreef James Westby:
On (26/09/06 11:09), Jean Parpaillon wrote:
I am looking for a sponsor for my package libmtp.
Hi I cannot sponsor, but I have some comments,
* Can you please expand the long description. At least mention what
the MTP is, and what sort of devices support it.
* Should libmtp-doc be in Section: doc?
* Please dtop using ${Source-Version}, see
http://lists.debian.org/debian-mentors/2006/09/msg00228.html
* Please sort out the debian/copyright, see
http://lists.debian.org/debian-devel-announce/2006/03/msg00023.html
Also there are more copyright holders to find, and a few files with
unclear copyright status that should be clarified upstream.
* I'm not sure whether you should install the rules in rules.d or in
the parent dir and add a symlink.
From /usr/share/doc/udev/README.Debian.gz:
MAINTAINERS BEWARE: the use of /etc/udev/rules.d/ by other packages is
discouraged, except when only RUN rules are added.
If you think your package needs to create a file there, then please
contact the udev package maintainer and explain your needs.
Packages should NEVER create files in /etc/udev/rules.d/, but create a
symlink the first time the package is installed (and never try again, to
allow the local system administrator to remove it).
So contact Md and don't install any files in /etc/udev/rules.d!
Greetings Arjan
signature.asc
Description: Dit berichtdeel is digitaal ondertekend
Re: gnome-app-install (super-easy package manager) prototype
On 2006-09-28, Jason Spiro [EMAIL PROTECTED] wrote: I am working on a port of gnome-app-install to Debian. This utility, made by the folks at Canonical Inc. and Ubuntu, is like Synaptic, but ten times easier to use. It currently does the job but does not always quit after an install operation is finished. Known issues include internationalization, missing icons, the OK button and it currently fails if you try to install anything in non-free. (If you try it, it'd be great if you could let me know, either here or by email, whether the icons in the Popularity column look like little stars or little X-squares. You can install it using the following sources.list lines:) deb http://www.jspiro.com/files/debian experimental/ deb-src http://www.jspiro.com/files/debian experimental/ The previous version I released fails to start with a RuntimeError. Please try the new version. It is now tested on both my machines and works on both. Changes: gnome-app-install (0.2.15-2) experimental; urgency=low . * bug-fix release: - fixed datadir defined in /usr/bin/gnome-app-install so that the app will run on PCs other than mine - added new Recommends: yelp (Gnome help) -- The church is near but the road is icy; the bar is far away but I will walk carefully. -- Russian Proverb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: gnome-app-install (super-easy package manager) prototype
On 2006-09-28, Adam Cécile (Le_Vert) [EMAIL PROTECTED] wrote: deb http://www.jspiro.com/files/debian experimental/ deb-src http://www.jspiro.com/files/debian experimental/ Why don't you upload it to mentors.debian.net ? I don't know how to, and I bet the lftp ftp.example.com -e 'mirror -eR source target' command won't work with the site. The command syncs a directory tree on my PC with a directory tree on the target machine. I am frustrated at the various bugs I'm seeing but I don't want to give up, as I want gnome-app-install to be in Debian. If you would like to finish packaging the app and take over maintainership, I'd be very glad to stop here and explain to you the changes I've made already. Don't forgive, if people would have stop each time they thought it's too hard, GNU/Linux would not exists ;-) You're right :) I can help you for the packaging for sure, and maybe for the port. If it's not enough we should run a project @ alioth en try to find some other developpers ! Thank you for your kind offer. I am going to look for somebody in Toronto (preferably at my school) for now. If I don't find anyone, in a week or so, please email me; I think I will take you up on your offer. Where can we host the files? I am on the starter package with my web hosting company (www.moonbase.info) so I can't SSH in. The company has FrontPage Extensions installed on all their webservers; does that mean Subversion will work for the job? I am working from an upstream .tar.gz file from Ubuntu. The upstream tarball includes .pyc files too, not just .py files. My .diff.gz does not touch the .pyc files when applied to the upstream source. Will this be a problem when people try to apply the .diff? Hmmm... Here is what I think. There are two case : * The original apps is only for ubuntu, you had to makes LOTS OF change in it to get it runnng on Debian. Then I would suggest to fork the project, so you'll recreate a new tarball. * The patches are not su huge and you can handle them through dpatch or quilt. Just leave the upstream tarball as it was but DO NOT INSTALL pyc files. (and report the issue to upstream). I think I will pick #2. Cheers, Jason -- When you open Windows, bugs get in. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: gnome-app-install (super-easy package manager) prototype
Le jeudi 28 septembre 2006 16:18, Jason Spiro a écrit : On 2006-09-28, Adam Cécile (Le_Vert) [EMAIL PROTECTED] wrote: deb http://www.jspiro.com/files/debian experimental/ deb-src http://www.jspiro.com/files/debian experimental/ Why don't you upload it to mentors.debian.net ? I don't know how to, and I bet the lftp ftp.example.com -e 'mirror -eR source target' command won't work with the site. The command syncs a directory tree on my PC with a directory tree on the target machine. http://mentors.debian.net/cgi-bin/maintainer-intro I am frustrated at the various bugs I'm seeing but I don't want to give up, as I want gnome-app-install to be in Debian. If you would like to finish packaging the app and take over maintainership, I'd be very glad to stop here and explain to you the changes I've made already. Don't forgive, if people would have stop each time they thought it's too hard, GNU/Linux would not exists ;-) You're right :) I can help you for the packaging for sure, and maybe for the port. If it's not enough we should run a project @ alioth en try to find some other developpers ! Thank you for your kind offer. I am going to look for somebody in Toronto (preferably at my school) for now. If I don't find anyone, in a week or so, please email me; I think I will take you up on your offer. Where can we host the files? I am on the starter package with my web hosting company (www.moonbase.info) so I can't SSH in. The company has FrontPage Extensions installed on all their webservers; does that mean Subversion will work for the job? Alioth is dedicated for this kind of problems. http://alioth.debian.org/ I am working from an upstream .tar.gz file from Ubuntu. The upstream tarball includes .pyc files too, not just .py files. My .diff.gz does not touch the .pyc files when applied to the upstream source. Will this be a problem when people try to apply the .diff? Hmmm... Here is what I think. There are two case : * The original apps is only for ubuntu, you had to makes LOTS OF change in it to get it runnng on Debian. Then I would suggest to fork the project, so you'll recreate a new tarball. * The patches are not su huge and you can handle them through dpatch or quilt. Just leave the upstream tarball as it was but DO NOT INSTALL pyc files. (and report the issue to upstream). I think I will pick #2. Cheers, Jason -- When you open Windows, bugs get in.
Re: RFS: scuttle
I am looking for a sponsor for my package scuttle.
Hi Marcelo,
I cannot sponsor you package, since IANADD, but I've given it a review:
* first of all, here we like to talk with a guy with a name and a
surname, not a nick :) Please write email here with you full name (and
maybe with the email you're using in the package)
* debian/changelog
- I'd like to be Initial release (Closes: #362114), but this is
just a personal feeling, nothing is wrong in what you've written
* debian/compat
- could you bump it to 5?
* debian/control
- if you choose Yes in the previous question, bump versione
depends on debhelper to (=5)
- add Homepage meta-tag
* debian/apache.conf
- what is this file for and how would you like to interact with apache?
* debian/config.inc.php.diff
- what is this file? I got it now, but I dont like this way to
create config file too much, but if you thought about it and find no
prettier way, could be ok
* debian/scuttle.post{inst, rm}
- you restart some services, but is user aware of it? maybe he/she
would not like those service to be restarted at install/remove time...
* teste.sh
- you've added this file that is not in the upstream pkg in the
root dir: the right way is to create it in debian/ and install it
where is neede
* debian/copyright
- you missed almost everywhere copyright years; give a look at [1]
[2] [3] for some guidelines to write this file
- many upstream files miss copyright notice: I think you should
ask upsteam to add that note (but I'd like to hear a DD comments on
this)
- I don't know it it's enough to add here the other projects
included in upstream package (phpBB2, UTF8 Helper Functions and XSPF
Web Music Player) as is needed to include copyright notice on a
per-file basis: someone else would comment on this?
* debian/rules
- remove template header
* ./cache/.cvsignore other
- you should ask upstream to remove unneded file from package
* debian/watch
- could you please add it, if you think could worth having it (I
think so... :)?
Kind Regards,
Sandro
[1] http://lists.debian.org/debian-devel-announce/2003/12/msg7.html
[2] http://lists.debian.org/debian-devel-announce/2006/03/msg00023.html
[3] http://lists.debian.org/debian-legal/2003/12/msg00194.html
--
Sandro Tosi (aka Morpheus, matrixhasu)
My (little) site: http://matrixhasu.altervista.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: png2html (updated package)
Florian Ernst wrote: Well, IMHO it is. Just uploaded. Thanks, your help is very much appreciated. If you want to update your packaging any time in the future please simply contact me directly via private mail. Will do :) Cheers, Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
What to do if upstream downlaod location disappears?
Dear mentors, One of my packages, petris, does not have an upstream download location anymore. I've contacted the author who told me that he is not planning to change this really. He suggested I make it available myself somewhere. I am trying to fix this bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=387371 Policy 12.5 says: [...] In addition, the copyright file must say where the upstream sources (if any) were obtained. It should name the original authors of the package and the Debian maintainer(s) who were involved with its creation. [...] The '(if any)' makes me think I can amend the copyright file like this: It was originally downloaded from http://home1.stofanet.dk/peter-seidler/ which does not exist anymore. There is currently no known download location. However, the pristine last upstream source is in the petris_1.0.1.orig.tar.gz tarball in the Debian archives. Would this be acceptable? Thanks a lot best regards, Andree -- Andree Leidenfrost @ Debian Developer Sydney - Australia signature.asc Description: This is a digitally signed message part
Re: What to do if upstream downlaod location disappears?
On Fri, Sep 29, 2006 at 07:19:04AM +1000, Andree Leidenfrost wrote: The '(if any)' makes me think I can amend the copyright file like this: It was originally downloaded from http://home1.stofanet.dk/peter-seidler/ which does not exist anymore. There is currently no known download location. However, the pristine last upstream source is in the petris_1.0.1.orig.tar.gz tarball in the Debian archives. Would this be acceptable? I would consider that to be a perfectly acceptable statement of the facts. - Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: drapes (updated again)
Hi, I have made another release of the package, adding to the debian/copyright file, the informations about the author of the dpatch that updates the config.guess and config.sub files. I hope to have resolved this problem... :) kind regards. francesco The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/d/drapes - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/d/drapes/drapes_0.4.97-3.dsc -- Francesco Namuri [EMAIL PROTECTED] http://www.namuri.it/ signature.asc Description: Digital signature
Re: How do you include orig with pbuilder?
Joseph Smidt [EMAIL PROTECTED] writes: I usually just build packages in unstable, but I am trying to learn pbuilder. I need to build a package and include the original source in the upload. With dpkg-buildpackage I just pass in -sa to do this. How do I do it with pbuilder? pdebuild --debbuildopts -sa -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How do you include orig with pbuilder?
Le Thu, Sep 28, 2006 at 04:51:21PM -0600, Joseph Smidt a écrit : I usually just build packages in unstable, but I am trying to learn pbuilder. I need to build a package and include the original source in the upload. With dpkg-buildpackage I just pass in -sa to do this. How do I do it with pbuilder? Dear Joseph, When you build a source package it produces the following files: - A .orig.tar.gz file: the upstream sources. - A .diff.gz file: your modifications to it (including the debian directory) - A .dsc file which gives the md5 sums of the previously mentinned files. Most programs assume that those three are all in the same directory. If you give the .dsc to pbuilder, it will check that the md5 sums are matching, and start to build. Actually, other files are frequently produced: - A .deb binary package. - A .changes file, which is a bit similar to the .dsc file, but fits better the needs of package uploading (for instance, it contains an extract of the changelog). You do not need then with pbuilder, dget, dpkg-source, and probably other programs whose purpose is not to upload new packages to a repository. Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
