Re: daemon stop and start during upgrade
Felipe Sateler wrote: > - Behave sensibly when invoked with 'start' and already running > - Behave sensibly when invoked with 'stop' and not running Ah.. yeah, that would be a possible interpretation of the policy. But formalizing something as to "behave sensibly" is not really exact, cause it is up to the reader how he interprets it. I do interpret it like this: - Don't do nasty things with 'start' when already running (like killing the firsts pidfiles, launching a seconds instance, etc.) - Don't do nasty things with 'stop' when not running (like killing other processes or changing something in the environment so it won't start the next time). I understand it so, that the third one is just there to describe it more exactly. Because exiting with zero or non-zero has absolutely nothing to do with "behaving sensibly". Actually returning a non-zero exit code is the right thing to do, cause the action to stop a process _did_ fail, because the process has not been running. Then again it would be "sensible" not to let the upgrade process fail just because of this, but i think thats far from the scope. So in the end I agree that would be sensible to exit with 0, if the process is not running, cause their might be different errors to occur when stopping (even though I never met one), but that it would make sense to describe this more clear in the policy. Regards, Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
doc-base: documentation in different languages
Dear mentors, I'm packaging a Java library that contains its usage documentation in both an English version (Documentation.html) and a French version (Documentation_fr.html). I've created a .doc-base file to register the documentation for Debian help viewers. Is there a way to let doc-base know that there are two versions of the documentation available, and that it should display, e.g., Documentation_fr.html if LC_LANG=fr, and Documentation.html otherwise? Thanks for any help, Jan-Pascal signature.asc Description: OpenPGP digital signature
Re: opencity NMU to mentors
[ I bounced the two previous mails to [EMAIL PROTECTED] and put the list back in the loop with this mail. ] Cyril Brulebois <[EMAIL PROTECTED]> (12/09/2007): > My questions about the exact content of the bug remains, because “FHS > violations” isn't self-explanatory. For the sake of completeness, posting the following here, so as to demonstrate how many points of the Policy the opencity package violates. There are explanations actually. Let's see: | AUTHORS -- doesn't ship, must be in $(DOCDIR) Must? What about the copyright file? | ChangeLog -- OK | COPYING, COPYRIGHT, INSTALL -- don't ship, that's OK | NEWS -- empty file, doesn't ship, that's OK You say they are OK. | OpenCity.desktop -- double-installed in /usr/share/applications | (correct) and $(DATADIR) (redundant) Bug, OK. What violation is that? | OpenCity.png -- double-installed in /usr/share/pixmaps (correct) and | $(DATADIR) (redundant) Maybe a bug, OK. What violation is that? | README, TODO -- don't ship, must be in $(DOCDIR) See Policy 12.3 again. What violation is that? | autopackage/ -- ships in $(DATADIR), no reason to ship at all Maybe a bug, OK. What violation is that? | config/* -- ship in $(DATADIR)/config; must be in $(CONFDIR) Not if it is not meant to be modified by the local admin. That configuration files, although in a directory called “config” can be static data. What violation is that, then? | docs/* -- ship in $(DATADIR)/docs; must be in $(DOCDIR) Policy 12.3 againt, must != should. | graphism/, model/, sound/, texture/ -- correctly ship in $(DADADIR) You say they are OK. How many policy violations remain? -- Cyril Brulebois pgp8KZMggaQHq.pgp Description: PGP signature
Re: opencity NMU to mentors
Neil Williams <[EMAIL PROTECTED]> (13/09/2007): > > The package was breaking FHS, > > Details? Is the breakage RC? Two docs files outside /usr/share/doc. He probably couldn't read “should” in Policy 12.3. > Number? #442029 Please note that I didn't reach the retitle[1] when I answered. 1. http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=12;bug=442029 My questions about the exact content of the bug remains, because “FHS violations” isn't self-explanatory. > Numbers? #442034, #442056 > > Rather than mucking with patches or explaining the issues > > ? Pardon ? The bug reports have to explain the issue behind the report > and for an NMU the bug reports must also include patches. What are the > bug report numbers? At least #442029 doesn't explain anything. I didn't look at the other reports yet, though. BTW, if you have patches, post them, and mark them as such so as to ease RC bug handling. Thanks. > > I figured the easiest thing to do > > Easy is not the objective. The Right Thing to do is to contact the maintainers first. And it is not like the Games Team were totally unresponsive, especially when it comes to handling copyright-related problems (see Miriam's — in particular but not only — incredible work bugging upstreams to clarify their license / consider relicensing). > > is to do a non-DD NMU and let the Games Team sponsor it if they > > want... it seemed silly to duplicate the work. What about letting the team some time to react and fix its package? > There is no duplication involved in an NMU - but you must engage with > the maintainer, explain your proposals, detail your patches and allow > time for the maintainer to either do the upload themselves. From your > request, I have no way to tell if you have done any of those essential > things.A Agreed, thanks for summarizing my thoughts. Cheers, -- Cyril Brulebois pgp3EY1ebAoj9.pgp Description: PGP signature
Re: RFS: ario
Hi On Wed, 12 Sep 2007 19:32:08 +0200 "Marc Pavot" <[EMAIL PROTECTED]> wrote: > > W: ario source: configure-generated-file-in-source config.log > > W: ario: binary-without-manpage usr/bin/ario > > I: ario: desktop-entry-contains-encoding-key > > ./usr/share/applications/ario.desktop:2 Encoding > > W: ario: desktop-entry-invalid-category Application > > ./usr/share/applications/ario.desktop > > W: ario: menu-item-uses-apps-section /usr/share/menu/ario:5 > > > I have fixed all this warnings (but I'm not really sure of solution for > the first one). As mentioned by other reply, simple rm in clean target should do it. > I have uploaded ario_0.2-2, can you please check it again? I just noticed one more thing - as we now have Homepage field support in dpkg, please use it instead of URL pseudo tag (some tools will complain about Homepage for now, but you can ignore it). PS: No need to CC me on reply. -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
RFS: drscheme (updated package)
Dear mentors, This is an update to DrScheme which is already in Debian. It is basically the upstream update plus some rather conservative changes, especially around the web server. I would be happy if someone could check this package. There are a few lintian errors but none of them seemed really problematic to me. Feel free to prove me wrong. As I upload it, I notice there are some things I thought I fixed which I somehow creeped back into the package, so this is more like a RFC than a RFS --- The obligatory template It builds these binary packages: drscheme - PLT Scheme Programming Environment mzscheme - PLT Scheme Interpreter The upload would fix these bugs: 402589, 425539 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/d/drscheme - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/d/drscheme/drscheme_370-1.dsc I would be glad if someone uploaded this package for me. Kind regards François-Denis Gonthier pgpogLasBkkw8.pgp Description: PGP signature
Re: busybox
"K. Richard Pixley" <[EMAIL PROTECTED]> writes: > If there a reason why busybox should not be packaged in such a way as > to provide a mutually exclusive alternative with the packages that it > supplants such as coreutils? It doesn't supplant them. The busybox package installs exactly one executable: '/usr/bin/busybox'. It *can* supplant coreutils commands, if the existing commands are overridden as a link to that binary; but that's not what happens when installing 'busybox', so there's no necessary conflict. -- \ "Unix is an operating system, OS/2 is half an operating system, | `\ Windows is a shell, and DOS is a boot partition virus." | _o__) —Peter H. Coffin | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
busybox
I'm confused about the busybox package. I mean, I'm familiar with busybox and it's applications. However, I'm wondering... If there a reason why busybox should not be packaged in such a way as to provide a mutually exclusive alternative with the packages that it supplants such as coreutils? It seems to me that intuitively, the busybox package should do exactly that, yet the package we have now does not. --rich -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: ario
On 9/13/07, Marc Pavot <[EMAIL PROTECTED]> wrote: > > W: ario source: configure-generated-file-in-source > config.log > I have fixed all this warnings (but I'm not really sure of solution for the > first one). A simple 'rm config.log' in the clean rule of debian/rules should do it. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: daemon stop and start during upgrade
Patrick Schoenfeld wrote: > Justin Pryzby schrieb: >>> It would be a pro to take this into the policy, wouldn't it? >> >> It is 9.3.2: >> >> | [...] > > No, it isn't. Yes, it is. You can dissect the paragraph in 3 ideas: - Behave sensibly when invoked with 'start' and already running - Behave sensibly when invoked with 'stop' and not running - Don't kill unfortunately named user processes. 2 and 3 are separated because of the comma before the 'and'. -- Felipe Sateler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: canorus
Dear mentors, I am looking for a sponsor for my package "canorus". * Package name: canorus Version : 0.3.1-1 Upstream Author : [Matevž Jekovec - [EMAIL PROTECTED] * URL : [http://www.canorus.org] * License : [GPLv2] Section : sound It builds these binary packages: canorus- Free cross-platform music score editor The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/c/canorus - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/c/canorus/canorus_0.3.1-1.dsc I would be glad if someone uploaded this package for me. -- Marco Rodrigues http://Marco.Tondela.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: opencity NMU to mentors
On Wed, 12 Sep 2007 13:10:25 -0700 Thanasis Kinias <[EMAIL PROTECTED]> wrote: > The package was breaking FHS, Details? Is the breakage RC? > so I rebuilt it for my own system after I > filed a bug. Number? > In doing so I noticed a couple of copyright problems and > filed those bugs too. Numbers? > Rather than mucking with patches or explaining > the issues ? Pardon ? The bug reports have to explain the issue behind the report and for an NMU the bug reports must also include patches. What are the bug report numbers? > I figured the easiest thing to do Easy is not the objective. > is to do a non-DD NMU and > let the Games Team sponsor it if they want... it seemed silly to > duplicate the work. No URL, no bug reports, no detail - how do you propose that it gets sponsored? There is no duplication involved in an NMU - but you must engage with the maintainer, explain your proposals, detail your patches and allow time for the maintainer to either do the upload themselves. From your request, I have no way to tell if you have done any of those essential things. -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ pgpn9vaS9Z8HL.pgp Description: PGP signature
RFS: panelfm
Dear mentors, I am looking for a sponsor for my package "panelfm". * Package name: panelfm Version : 1.2-1 Upstream Author : M.K.Srikant <[EMAIL PROTECTED]> * URL : http://panelfm.sourceforge.net/ * License : GPL Section : gnome It builds these binary packages: panelfm- Simple file system explorer applet for Gnome panel The package appears to be lintian clean. The upload would fix these bugs: 441965 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/panelfm - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/panelfm/panelfm_1.2-1.dsc I would be glad if someone uploaded this package for me. Kind regards Luca Falavigna -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
opencity NMU to mentors
Greetings, I've put a NMU of the opencity pacakge on mentors. I'm not looking to hijack the package, just fix some serious policy violations. The package was breaking FHS, so I rebuilt it for my own system after I filed a bug. In doing so I noticed a couple of copyright problems and filed those bugs too. Rather than mucking with patches or explaining the issues I figured the easiest thing to do is to do a non-DD NMU and let the Games Team sponsor it if they want... it seemed silly to duplicate the work. Best regards, -- Thanasis Kinias Doctoral Candidate, Department of History, and Instructor, Professional Enhancement Programs Arizona State University, Tempe, Arizona, U.S.A. . Je ne viens d'aucun pays, d'aucune cité, d'aucune tribu. Je suis fils de la route, ma patrie est caravane, et ma vie la plus inattendue des traversées. -- Amin Maalouf, _Léon l'Africain_ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: ario
Hi, > Please merge changelog entries, it looks a bit strange to have -0 as > initial upload, as initial version in archive should be -1. done. > W: ario source: configure-generated-file-in-source config.log > W: ario: binary-without-manpage usr/bin/ario > I: ario: desktop-entry-contains-encoding-key > ./usr/share/applications/ario.desktop:2 Encoding > W: ario: desktop-entry-invalid-category Application > ./usr/share/applications/ario.desktop > W: ario: menu-item-uses-apps-section /usr/share/menu/ario:5 > > I have fixed all this warnings (but I'm not really sure of solution for the first one). I have uploaded ario_0.2-2, can you please check it again? Thanks for your help. Marc
Re: RFS: gbrainy
Hi, Il giorno mer, 12/09/2007 alle 18.23 +0200, Siegfried-Angel ha scritto: > Dear mentors, > > I am looking for a sponsor for my package "gbrainy". > > * Package name: gbrainy > Version : 0.2-1 > Upstream Author : Jordi Mas i Hernandez > * URL : http://live.gnome.org/gbrainy > * License : GPLv2+ > Section : games > > It builds these binary packages: > gbrainy- a brain teaser game and trainer to have fun and to keep > your brain trained > > The package appears to be lintian clean, except for this message «W: > gbrainy: menu-item-creates-new-section Games/Logic > /usr/share/menu/gbrainy:2». I don't know why it's complaining, since > LogicGames is listed in the Free Desktop specifications. this warning is related to debian/menu, see: http://lists.debian.org/debian-devel-announce/2007/07/msg0.html Cheers, -- Francesco Namuri francesco(at)namuri(dot)it http://namuri.it/ id gpg key: 21A4702A [EMAIL PROTECTED] signature.asc Description: Questa è una parte del messaggio firmata digitalmente
RFS: gbrainy
Dear mentors, I am looking for a sponsor for my package "gbrainy". * Package name: gbrainy Version : 0.2-1 Upstream Author : Jordi Mas i Hernandez * URL : http://live.gnome.org/gbrainy * License : GPLv2+ Section : games It builds these binary packages: gbrainy- a brain teaser game and trainer to have fun and to keep your brain trained The package appears to be lintian clean, except for this message «W: gbrainy: menu-item-creates-new-section Games/Logic /usr/share/menu/gbrainy:2». I don't know why it's complaining, since LogicGames is listed in the Free Desktop specifications. The upload would fix these bugs: 440982 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/g/gbrainy - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/g/gbrainy/gbrainy_0.2-1.dsc I would be glad if someone uploaded this package for me. Kind regards Siegfried-Angel Gevatter Pujals (RainCT)
RFS: gpicview - damn small image viewer based on GTK+ 2.x
Dear mentors, I am looking for a sponsor for my package "gpicview". * Package name: gpicview Version : 0.1.3-1 Upstream Author : PCMan (Hong Jen Yee) <[EMAIL PROTECTED]> * URL : http://lxde.sourceforge.net/gpicview/ * License : GPL version 2 Section : graphics It builds this binary package: gpicview - lightweight image viewer The package is lintian and linda clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/g/gpicview - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/g/gpicview/gpicview_0.1.3-1.dsc GPicView is a damn small image viewer based on GTK+ 2.x. qiv is another lightweight image viewer, but qiv uses GTK+ 1.2. I would be glad if someone uploaded this package for me. Kind regards Wen-Yen Chuang (caleb) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: glchess (updated package)
Thierry Randrianiriana <[EMAIL PROTECTED]> (07/09/2007): > I am looking for a sponsor for the new version 1.0.6+debian-1 > of my package "glchess". Since this game is included in gnome-games, does it make sense to keep it in a single package? > The upload would fix these bugs: 421694, 441156 I missed your answer to the bug since it didn't appear in the thread (I've got a quite huge -bugs-rc backlog), that's why I sent a patch there (yeah, I could have check the whole buglog, but well, things happen… :p). > I would be glad if someone uploaded this package for me. In case you concentrate your efforts on helping with the gnome-games package, please consider asking for the removal of this extra package. Cheers, -- Cyril Brulebois pgprhyiiwlQBJ.pgp Description: PGP signature
Re: [UPLOADED] hex-a-hop (updated package)
2007/9/11, Jens Seidel <[EMAIL PROTECTED]>: > On Tue, Sep 11, 2007 at 03:38:06PM +0200, Bas Wijnen wrote: > > I uploaded the package. I still have some comments (see below), but > > they weren't enough reason to not upload. > > Thanks. > > > On Tue, Sep 11, 2007 at 12:20:11AM +0200, Jens Seidel wrote: > > > > this is a "GPL without version" claim, which according to the GPL > > > > means any version is acceptable. I > > > > > > It's still "GPL without version". I need the permission of Miriam and > > > maybe others before I can change it. > > > > Strictly speaking, you don't. You can choose to accept any version, for > > example "all versions >= 2", like the game itself is licensed. Then you > > have the right to distribute using that license. > > > > However, I agree it is nice to ask people what they intended, and not > > remove license options without reason. > > OK, will probably do this with the next upload. Go ahead Jens, no problem at all :) The idea was mainly: "This patch is released under the same license as the game itself and the packaging", but whatever license or text you prefer will be OK for me :) You can change it yourself if you want, but if you prefer to do it formally nice, just tell me the text you prefer and I'll do the commit myself :) The idea is that not only the program itself and the packaging have a license, but also the patches do have a copyright and license. Maybe the best text would be "This patch is licensed undet the same license as the program, see debian/copyright" or something like that. Greetings, Miry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: kopete-otr 0.6-1
On Wednesday 12 September 2007, Raphael Geissert wrote: > Other minor details: > * debian/copyright says Upstream Author but there are two authors listed. Done. Francesco -- Francesco Cecconi ' |BrAnD| ' [EMAIL PROTECTED] GPG Key ID: 11F6E468 | Debian pkg Maintainer Key fingerprint = A45A 59F0 15F8 BF5E 41AC 8478 D931 DAA2 11F6 E468 signature.asc Description: This is a digitally signed message part.
Re: RFS: kopete-otr 0.6-1
On 2007-09-12, Raphael Geissert <[EMAIL PROTECTED]> wrote:
> On 11/09/2007, Francesco Cecconi <[EMAIL PROTECTED]> wrote:
>> On Tuesday 11 September 2007, Raphael Geissert wrote:
>> > On 10/09/2007, Francesco Cecconi <[EMAIL PROTECTED]> wrote:
>> > > Dear DD,
>> > >
>> > > I am looking for a sponsor for my package "kopete-otr".
>> > >
>> >
>> > Maybe you should send an ITP first and add a (Closes: #nn) to the
>> > debian/changelog
>>
>> done,
>
> By the way, I don't think you require ${misc:Depends} in
> debian/control, so you can remove it.
debhelper(7) encourages you to add ${misc:Depends} no matter what.
/Sune
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Are soname bumps required when library upgrades break compatibility?
> > Policy 8.1 is clear - if the bug documents a crash in an application > > that was not present before the library was updated and the library > > has not changed the SONAME or package name, the library justifies an > > RC bug. > > Actually, Policy 8.1 doesn't say anything about when to change the > soname. Perhaps it should? The bit about the SONAME is implicit in the change of package name (as checked by lintian) and if the package name has changed, then the application will have had to have been rebuilt against the new library API so a crash in those circumstances is still a bug, this time caused by a buggy library AFTER a correct transition. I was just pointing out that if the transition is correct, the bug does not have to be RC. Policy mandates that the library must transition cleanly - the SONAME is just the mechanism used to change the package name which is what actually determines what gets installed. Bugs which result from an updated library package being installed when it should have been held back are examples of an incorrect library transition and break Policy 8.1. There is no need for Policy to delve into the mechanism of complying with Policy as long as the result of the changes has the effect of compliance. -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ pgpF1J19eic6N.pgp Description: PGP signature
Re: daemon stop and start during upgrade
Justin Pryzby schrieb: >> It would be a pro to take this into the policy, wouldn't it? > > It is 9.3.2: > > | [...] No, it isn't. This part of the policy just says that it should not kill other processes, which are eventually named unfortunately, just because the process it *should* kill does not run. It does not say anything about how the init script should behave, if the application is not running. But, and thats important, this does again recommend to use start-stop-daemon which exits with a non-zero exit-code if there is nothing to stop. > It's a very interesting question whether packages should inhibit > starting a daemon that wasn't running when it would otherwise have > been stopped. I guess the current state of affairs is that a That is another thing, but yes, I agree that this is very interestering as well. > think the ideal situation is that a manually-stopped daemon would > cause a message to be printed: "Not starting food: not stopped at > preinst time" in the same style of messages that are shown with > [...] ACK. I think this would be a good proposal. But how to realise this properly? It would need a change to the init script, would it? Regards Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
