Re: First pass all buildds before entering unstable
On Wed, Nov 19, 2003 at 11:21:18AM +0100, Giacomo A. Catenazzi wrote: > I worry about indirect delays. Scenario: developer A@ do good job with > packages A, but A requires packages B. What should A do? > Waiting and not lose the motivation? > Help B@, maybe with a NMU, but still waiting the canonical time for NMU > (on normal time)? > > Do A@ have knows enought about B to help? (Maybe B is in a other > language, for glibc, XFree86,.. specific architectures knowelenge are > maybe required,... IMHO, We should not warry about indirect delay/problems. It's not A's fault, thus A should be warranted to be released (in a way or in another): A not being in testing because of B is "part of the game". The problem which must be handled is B, and who or how to handle it is too case specific to be considered here. We have 'help' tag on BTS and specific mailing lists to ask for help on specific topic. BTW, when i did NMU i based the delay either on the best practice and on the need of the fix. I thought it to be reasonable. > - the developers (maybe requiring not only uploader) could override the > waiting status in pre-unstable queue. I do not understand this: what do you mean? ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: First pass all buildds before entering unstable
On Wed, Nov 19, 2003 at 11:10:14AM +0100, Andreas Tille wrote: > Exactly this was the idea. I'm unsure whether experimental could serve as > this kind of staging area. I would keep experimental only for experiments (:P), while i see your proposal as a new step to be included in our packages workflow; thus i would use unstable. Moreover, experimental is not autobuilded because of high chances of broken packages in it. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: First pass all buildds before entering unstable
On Wed, Nov 19, 2003 at 11:02:17AM +0100, Wouter Verhelst wrote: > I don't think people would like it if their package stayed in incoming > for multiple weeks because there's a backlog on some architecture. Neither i. This is why i would like to receive baklogs mailed to maintainer if autobuild fails. But i would like to receive backlogs even for pre-autobuilds, so that i could fix the problem, contact the upstream etc. BTW, i think that the correct workflow would be: Move package from incoming to autobuild. If all architectures build, continue (as before this change); else, if not builded but is not upstrea/maintainer fault, continue (as before this change). Else reject the package. > Unstable is there for that kind of things. And to detect other kinds of > bugs, too. If you're going to keep packages in incoming like this, > people won't be able to test it until it's built on all architectures. If we stay as it is, we'll continue to get slowed by badly built packages/softwares. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language. pgpykhdfZUnbE.pgp Description: PGP signature
Re: First pass all buildds before entering unstable
On Wed, Nov 19, 2003 at 09:44:31AM +0100, Giacomo A. Catenazzi wrote: > No!!! it would delay to much the entry of some important packages in > unstable. It would maybe improve some architectures, but definitely > would reduce extensive testing of newer versions. In which way would it improve some architectures and not the overall Debian quality? why would it reduce extensive testing of newer versions? Rejecting a package which is not buildable on a spacific architecture, because of an unpstream or maintainer fault, is a semi-automatic testing that can be implemented. If we let it in and then we auto-build it, we get a new package with FTBFS (i.e RC) bugs and slow down release even more. If we auto-build it first and, if no upstream/package faults, we let it in, we get less RC bugs. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: First pass all buildds before entering unstable
On Wed, Nov 19, 2003 at 08:48:10AM +0100, Michael Piefel wrote: > Am 19.11.03 um 07:42:18 schrieb Andreas Tille: > >After each buildd was able to build a package the whole > >set with all architectures enters unstable at once. I like the idea. > Yeah, cool. That would get rid of many buggy packages. And many clean > ones. Some buildd are horribly behind time. No offence meant, it's not > necessarily sloppy maintainers, rather it's slow computers and extremely > complex packages. I don't think the speed of some of our buildd would be the point. Sooner or later the new packages will be compiled on our buildd: better before entering Debian than after and.. > Take workrave, for instance. Perfectly stable, as far as I can tell. Not > built recently on m68k (because of libgnomeuimm2.0-dev), not built on > alpha for a very long time (same reason). It's not in testing, which is > bad enough, with your idea only ancient versions would be in unstable. I think this is not what Andreas ment: I suppose he was trying to drop FTBFS bugs for those new packages missing correct Build-* fields. Packages that cannot be built because of correct source fields but missing dependencies, should not receive bugs (AFAICT) > Don't get me wrong. I actually quite like the thought. It just won't > work. Perhaps limit it to "when it's built for i386, powerpc, hppa and > arm". (That's were I got all my architecture-dependent bugs from, and > they are all quite current.) IMHO it would indeed work, if only we consider meaningful buildd reports (for what is our purpose). ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: ftpmaster accepts packages that have been rejected a few days ago
On Sat, Nov 15, 2003 at 01:48:40AM +1100, Martin Michlmayr wrote: > Yes, this is true. We never really reached a conclusion on this, I > think. This might be moved to -newmaint. [...] > Yes, it's a shame, but it's just a fact of life that not everything > can be 100% open. As to the DAM discussion being available to [...] Ok, i see the point of private stuff. > In the case of keyring and DAM in the past, we were well aware that > nothing happened even without seeing the archives. ;-) Gladly, the > situation has changed. [...] > Look, I'm not against being transparent; not at all. I try to be very > open and approachable. But in some cases it just doesn't make sense. Let's be positive thinking: i like it. This mean that we suppose anything to go on in the best way in the future, we will never face again these problems with DAM or keyring or whatever internal Debian structure because things changed. This makes any issues here irrilevant. Thinking to a solution for a 100% transparent structure would be a waste of time. We are supposed to accept this for paceful living, because we trust the good changes or perheps because delegates are choosen from the DPL (person which we are supposed to trust). I think it won't stand for long. In any case, since structure is not so open and it's not worth of changing, complains about it should not be sent on -devel, because we can't do anything in almost all the cases (not to mention -private which can't be reached by anyone)... > And I don't see the problem here; if you see a _concrete_ problem, > please mail [EMAIL PROTECTED] And here i understand that we should redirect any attempt to flame^Wcomplain any one in Debian key-points to [EMAIL PROTECTED], assuming people to think they have _concrete_ problems (really reasonable; i suppose it already happened in some way). "This is OT here. If you think you have a problem with Debian structure, you should speak with [EMAIL PROTECTED]" will cut any thread short. I supose DPL should not complain about this, because, after all, he choosed them. I sow a problem, but i was told to live with it: I'll remember it, and go on. > > Trust is not a transitive property: i trusted you as DPL, this does > > FWIW, I'm not speaking as DPL at the moment; I use [EMAIL PROTECTED] in From: > to indicate when I do. Oh, well, sorry. I did not ment to write to you as the DPL, but you know... it happens that you are :) I can rewrite my sentence as "I trust the DPL, this...", and it would have the same meaning. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: ftpmaster accepts packages that have been rejected a few days ago
On Fri, Nov 14, 2003 at 08:53:42PM +1100, Martin Michlmayr wrote: > It hasn't happend yet. You have to understand that rejections at the > DAM stage are quite rare; most applications are rejected at the AM > stage (and most of them because the applicants don't have enough time > or interest, not because of philosophical or technical problems). I understand, but they happen, and i think this to be a not-so-open point in our open structure. DAM discussion with applicants (and vice-versa) should be open for reading (as well as discussion with keyring and ftpmasters, archived or not archived). Indeed there is the issues about rejection being public, which should be also covered. It makes sense to me that poeple being rejected (at any level) would not like this to be known. In another mail you also say: > So what's exactly the problem you're trying to solve? The da-manager > alias is archived and if a "complain[sic] pops up" someone can surely > get access to the archive to see what happened. Although, if the > complaint is a lack of response, you surely wouldn't find anything > in the archive, would you? But if i do not a good job anyone can read my bug reports (actually there are a lot of people reading reports to my packages); if i do not reply to reports, fix bugs, be active for a while, i can become MIA, my packages be orphaned and eventually i can resign (or be forced to). On my side (a simple maintainer) evrything i do is under control, and open: people on some keypoints in Debian structure do not have the same treatment. Not being as open as the rest of Debian is one of the reasons they are falmed. Please, I don't want people NMUing keyring/ftpmasters/dam job. The concept is indeed the same. Of course if the do not reply mails i would not find anything, but being subscribed i could read directly what happen, or be aware of the fact that nothing happens. Haveing a list for DAM does not makes sense? Make DAM discuss _evrythig_ or be publically contacted (for example about status reporting) on -newmaint. Trust is not a transitive property: i trusted you as DPL, this does not mean i trust your delegates. I'd like to know what they do, when they do something for Debian. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: ftpmaster accepts packages that have been rejected a few days ago
On Thu, Nov 13, 2003 at 11:09:39PM -0600, Manoj Srivastava wrote: > And a number of other people, also at various levels of > Debian, like James, and respect the work he has put in. The point? Later... > > There must be somthing true in it, > > I think you really need to examine your understanding of > causation. Lots of people hold a view, so it must be true? I might have translated an Italian expression in english (this might not have the same meaning), but i meant that there maust be something in the entire issue that is true/matter of fact/source of the issue. I did not ment that the entire issue is true. If people don't like James as DAM, i did not meant that James is "bad", but somthing bad happened, while he was representing Debian. When something like that happen i (we?) can't for sure defend or blame James, because one is more driven by the good things heared, the other is driven by people saying bad things. > And what about the other people that Like James? Can they too > not be wrong? There must be something true in this too: for example he did something that people liked a lot (it's all but hard to figure what). Now It's true that i started this short mail exchange thinking of James haveing dnoe "yet another ... from elmo": some one sayed it's not. May be. If we focus on open structure, we must be open not only in users <-> developers direction but olso developers <-> developers (ftpmasters and keyring), and developers <-> almost-developers (da-manager). ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: ftpmaster accepts packages that have been rejected a few days ago
[ I'm subscribed: please avoid to Cc me ] Hi Russel, On Fri, Nov 14, 2003 at 12:09:43PM +1100, Russell Coker wrote: > I think that we have more of a problem of people being afraid to contribute > because of the fear of undue criticism or rejection than we have of unworthy > people joining. > > The number of people who have been rejected is small. The number of people > who are good coders who could contribute to Debian if they chose is much > larger. This is a matter of opinion: is my opinion that motivation is more important than skills: enthusiasts, and motivated people are ready to learn and willed to bring the best, hence to be good coders. People who already are good coders might not be so interested and might not want to bring the same quality. Anyway, we must (because we can), let good coders in, and reject not motivated people. I propose to move AM/DAM[1] reports to a public list with a private archive. Anyone must be able to know what's going on in the _entire_ NM process by subscribing the list. At the same time it's reasonable to nicely handle rejection by not letting reports be publically browsable: any one willing to have old information for the archive must ask a Debian member [2]. ciao, [1] This means that all mails sent by DAM, must be also sent to the list. [2] I know that people myght archive this list anyway, but we must trust our users as they trust us. Disclaimers may be added to the end of the each essage. -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: ftpmaster accepts packages that have been rejected a few days ago
On Thu, Nov 13, 2003 at 09:28:02AM -0500, Lukas Geyer wrote: > He, this would be a great signature... (Luca, oxygen is the quite > essential stuff you breathe, constitutes about 20% of the air around > us...) eh, dict.org was down so i could not check them. A quick google search showed too many things to be sure (my primary doubt was with flogiston). [...] > and one of the major reasons was the state of the NM process. I am > pleasantly surprised that Martin Michlmayr managed to improve the > situation without creating big conflicts, thanks to both him and James > Troup. That's correct, but there still are unclear point in this workflow. The problem is that a new complain pops up, this is yet another discussion with no backlog, so i've to build my opinion from what happened in the past. The past was not so happy with James (i still can't say that now is not like before). > What is the current state there? Do you have any evidence of James' [...] Look, he is indifferent to me: i neither like nor i dislike him. There is nothing personal against him. I want things working: if people wants to complain, i would like to care of their complains, but actually i can't because issues eveolved in private mails, while he is doing a public service for Debian. Can you tell? Cool, but i don't want to poll each DD to know about his impression/experiance about James (as well as other people in our keypoint) and his contribution. That's waht i meant. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: ftpmaster accepts packages that have been rejected a few days ago
On Fri, Nov 14, 2003 at 01:12:50AM +1100, Pascal Hakim wrote: > A da-manager list would be a very bad idea. We do not want > people's rejection from Debian to be archived in a public list which > anyone can see. Imagine if searching for your name in google had "Luca > De Vitis is unsuitable to join debian due to ..." as its first hit? Why not: this would discourage people who try to join Debian without real motivation. BTW, we already have people rejection archived in debian-newmaint, so i do not see this point. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: ftpmaster accepts packages that have been rejected a few days ago
On Thu, Nov 13, 2003 at 10:45:09PM +1100, Martin Michlmayr wrote: > Also note that the DAM's decision can be overridden. AFAICT, i never sow this to happen, but if you say so i take it for sure (but i'd now like to have an example, just out of curiosity). > Right, just take Eray as an example (and note that the NM committee > agreed 100% with the DAM's decision; yet the DAM got all the blame). Indeed you're right. To me we sohuld make things more open. Let's make da-manager a mailing list (debian-dam?) with archive, so that evrything may be read openly by anyone and things get commented by themselves[1]. The same should be for ftpmaster: indeed we have debian-www, why not debian-ftp? keyring is another important issue: this should be a list too. I also want to read what happen there. ciao, [1] alternatively i would deprecate da-manager in favour of debian-newmaint (since we already have a list for a similar purpose). -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: ftpmaster accepts packages that have been rejected a few days ago
On Thu, Nov 13, 2003 at 11:02:26PM +1100, Russell Coker wrote: > Saying "this is crap" in response to something you strongly disagree with is > pretty much standard practise in the Internet community. It is done both > online and off-line. > > Anyone who wants to get involved in email debates or to go drinking with > programmers should be able to handle such things. If you can't handle such > things then you shouldn't be criticising the social skills of other people. Curiously, i go drinking with programmers very often, and this rarely happen. I'm sorry you face it commonly (of course one can live with it). That's to me means this is a not common behaviour, hence it is not supposed to know by anyone. > The nature of our development process is somewhat combative. If you search > the archives of this list you will see many serious flame-wars, some of which > produce positive outcomes. You just have to learn to deal with these things. Flames make me sick, and fill my box of things i unfortunately can't tag as spam. People flameing recall me of animals fighting. A primitive way of interacting. I just ingnore them. Of course i can live with people behaving this way, and i can handle them: shouldn't i, i would have started yet another flame. > Look on the bright side, having someone refer to your email as "crap" is > better than being called a "nerd" at school, which I think happened to most > people on this list and probably happened to you. ;) That's a point, despite the fact that i was never called a nerd or geek for the simple reason i never behaved in such a way. Those who know me can tell you. And i know more people who cannot even turn on a computer, than hakers, geek, programmers and such. I pay that by not haveing the tecnical skill most of you have: that's a trade off i accept and like. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: ftpmaster accepts packages that have been rejected a few days ago
On Thu, Nov 13, 2003 at 09:40:08AM +, Steve McIntyre wrote: > Sorry, but this is crap. James is doing multiple jobs, several of > which are just about guaranteed to draw criticism and lots of people > not liking him. That's going to be part of the job when you're the > person who says "no".. What should you be sorry for if you refer to my mail as a crap? This is hypocrete. You could have written those few rows in a lot of adifferent ways instead of "this is crap". That's what i mean. Should i've been there in front of you, you'd probably have never told me such things in person. That's a pity. BTW, He his doing a lot of jobs for us, tecnically well done, but socially a disaster. And he can no more. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: ftpmaster accepts packages that have been rejected a few days ago
On Thu, Nov 13, 2003 at 10:23:08AM +0100, David Weinehall wrote: > A lot of people believe that Elvis still is alive, a lot of people used > to believe in flogiston rather than oxygen, a lot of people "knew" that > that world was flat... The list goes on for ages. Face it, > that a lot of people have strong feelings about something just doesn't > make it true; we have war, religion and modern financial theory as > evidence for this. I've nothing to face. If you don't prove me otherwise, what i've said stands. It was proven that earth was not flat, it was probably proven that oxygen was better thatn flogiston (I don't really know what both are), and Elvis... i'll skip any superflous comment on this. > As for James: if you are in a position where you decide who's to go in > and who's not (as the DAM), and to decide _what_ goes in and what > doesn't (as an FTP-master), you must: [...] You did absolutely misreaded what i've written: i've not meant that he should not take unpopular decisions, but you where probaly focused on finding some not very helpful argument for the discussion. If you are in charge of any position in a community you inevitably get a political role. You can take popular or unpopular decision, but in neither case you can behave rudely or cut disuccion short or take any mail lightly. You are discussing with people from other countries with different language and different culture. You _must_ take time and give your best to explaint the reason of any choice you made because it's not obvious the the recipient might understand. _THIS_ is the problem. As for the DAM, i wander why an AM racommends an applicant, but the DAM does not accept him. What does this mean? Is AM role relevant or in effect DAM is the real one who decides? If the latter, why haveing AM? As you can see, this has nothing to deal with popular or unpopular decision. Do we want to talk about keyring? ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: ftpmaster accepts packages that have been rejected a few days ago
On Wed, Nov 12, 2003 at 08:59:22PM +0100, Josip Rodin wrote: > No way, man. We simply have to have people repeat the same fodder on > debian-devel over and over again. The three hundred odd mails per day > from the new fodder just aren't enough! Yes, but realy a lot of people at any level in Debian have strong negative feelings towards James (just to leave it to your immagination), for various reasons. There must be somthing true in it, and since i'm involved in Debian i never sow this situation to get better. We might repeat the same fodder with the same mails, and write the same mails with with the same words: perheps we use the wrong words, or simply we still use the rude words. I see most people still not understanding that we read mails: we don't see faces, we don't looks each other in the eyes. Reading mails is differen from speaking face to face. You can't write anything in any way on mails: you must be careful. Most of you (hey James, you too) simply don't care. Deal with other people the same way you'd like to be dealt with. To say it shortly: if a lot of people don't like you, thay can't all be wrong about you (and believe me, there are really a lot). ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Removing python-pygresql and libpqpp packages
On Fri, Oct 10, 2003 at 06:05:05PM +0100, Oliver Elphick wrote: > Go for it. > > The existing python-pygresql packages will cease to be built when the > first postgresql 7.4 packages go into unstable. I will then ask the ftp > maintainers to remove them, so as to clear the way for your packages. Just for curiosity: shouldn't the old python-pygresql be automatically removed from the archive once it is no more builded? ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: eek, phpgroupware
On Mon, Sep 22, 2003 at 04:59:57PM +, Thomas Viehmann wrote: > I have some phpgw packages ready at <http://vman.de/debian/>. They seem to > fix some > of the more pressing problems in phpgw/sid, however they don't correspond to > Luca's > package split. At this point it doesn't matter any more: i dont' want to care phpgroupware any longer. I can review your package and eventually upload them by the end of this week. I also can be an uploader/sponsor for your packages untill you'll able to upload them by your self or trough some other developer just more interested then me. Any one willing to step in is wellcome. > Anyhow, my lack of response (hopefully resolved by end of next week) is not a > result > of disinterest or anything, but rather of lack of connectivity. I'm very > honored by > Luca's offer and intend to accept once I'm able to communicate and build > debian > packages again. (But I just found this mail in the haystack of 400 Spam mails, > teaches me about client-side filtering...) By now, 0.9.14.006 is good enough and the week end is a good timespan IMHO. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: [PROPOSAL] Debian Release Plan [was: Re: Future releases of Debian]
On Sat, Aug 02, 2003 at 06:01:51AM -0500, Luca - De Whiskey's - De Vitis wrote: > What we need, is a task management system almost like our bug tracking system. > A way we can express task that have to be done before next relese or any other tasks > goal we wants to achive. A system where tasks may be splitted, merged, want achieve > spowned, assigned, revoked, opened, closed, tagged. A system where tasks, like spawned > bugs, can have severities, can be handled via mail, browsed via web interface > etc. That would be a system to let us to show our user what we are users > planning to do, how we want to achive our goal, who will work on what, discuss achieve > with them. > > A system i was thinkg about from time but which i had never time to implement. thinking > Looking at these discussions, i'm really considering to bould one. Guys, don't be too hurry in sending mails... ops that mail was mine... ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language. pgpyN5ineBCq3.pgp Description: PGP signature
Re: [PROPOSAL] Debian Release Plan [was: Re: Future releases of Debian]
On Fri, Aug 01, 2003 at 07:03:46PM +0200, Arnaud Vandyck wrote: > Adrian Bunk <[EMAIL PROTECTED]> wrote: > [...] > > [3] http://www.fs.tum.de/~bunk/Debian/freeze > > Reading the whole "Future releases of Debian" thread, I thought that > the main idea was that Debian need a more 'readable' status for the next > stable release. > > I propose to create a meta-package called 'release-status-sarge' that > depends on packages (with version number) that we want to see in sarge. What we need, is a task management system almost like our bug tracking system. A way we can express task that have to be done before next relese or any other goal we wants to achive. A system where tasks may be splitted, merged, spowned, assigned, revoked, opened, closed, tagged. A system where tasks, like bugs, can have severities, can be handled via mail, browsed via web interface etc. That would be a system to let us to show our user what we are planning to do, how we want to achive our goal, who will work on what, discuss with them. A system i was thinkg about from time but which i had never time to implement. Looking at these discussions, i'm really considering to bould one. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language. pgpCiEl7ULOmj.pgp Description: PGP signature
Re: CUPS should be the default print service in Debian/Sarge
On Thu, Jul 31, 2003 at 11:35:13AM -0700, Keegan Quinn wrote: > FWIW, I've had very good experiences with the CUPS in unstable, so > I'd not object to this. OTOH, installing it without it being 'default' > is already quite trivial. What would this change entail, exactly? So i had/have either in unstable and in stable. Should exim not to be the default MTA, it would be trivial to install too. This is not the point: the point is that CUPS is perfectly working for most of us and shows really a lot of good features, a user-friendly interface, quite large number of direvers support. It is a good solution for any user level with most common printers/needs, thus it should be the default (IMHO). ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language. pgp8IiEFCw2jg.pgp Description: PGP signature
Re: debconf 2005 in Vienna, Austria
On Wed, Jul 30, 2003 at 09:22:57AM +0200, Christian Perrier wrote: > Anyway, that could give the following schedule : > > Thursday-Sunday : LinuxTag at WhereverHeim, Germany > Sunday evening : folks travel to Debcamp in Vienna, Austria > Monday-Friday : Debcamp > Saturday, Sunday : Debconf Just my 2 cents: DebConf should no more end on sunday afternoon/evening but on morning by lunch time. This is for a simple reason (i sow at DebConf 3): people start leaving in the afternoon to be home by evening/night. It's better to let it start a day before than make it end with people so in hurry. Because of this i could not attend Branden talk about SubVersion at DebConf 3: how am i supposed to live on this? Some time, life is really unfair. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: New wnpp tag: Request For (Co-Maintainer|Help|Whatever)
On Thu, Jul 24, 2003 at 07:31:02AM -0500, Luca - De Whiskey's - De Vitis wrote: [...] Ops... I made a wrong alias on my mutt. Please follow-up on -qa. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
New wnpp tag: Request For (Co-Maintainer|Help|Whatever)
I was wandering about that kind of bug. It should mean that a maintainer (or a group of) is looking for more volunteer fo a kind of packge. It's not really a RFA, and it should probably have its own place on w.d.o/devel/wnpp page. RFC does not sounds good, but RFCM or RFH might. Any comment? ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Cosing ITA bugs when you've changed your mind.
On Thu, Jul 24, 2003 at 08:27:06AM +0200, Thomas Viehmann wrote: > You have RFA'd phpgroupware and I've ITA'd it. Waiting until the ugly work > (i.e. > the security update to stable) is getting done by others and then popping back > out of your hole to say "April fools" is not acceptable. > Your maintainance of phpGroupWare has been limited to yelling at people > wanting > to finally do something about the embarrassingly poor state of Debian > packages, > and it's time to let that go. [0] (In private mail, one of the upstream > developers who uses Debian told me that he "would not use those debs, even if > someone paid [him]", I've been getting private mails form other users with the > same bad experience with phpgroupware.) Maybe you are one of the examples on > why > the NM process isn't thorough (slow) enough at present. Your ideas of hindering people contributing is a non-sense i've already told you. There is no benefit in this for anyone. We have never discussed about your adoption of phpgroupware, so i don't see why you felt free to adopt it. I've already told you, and i'm writing it publically, that an infrastructure to cooperate is up in place and i've already told you i would have let you contribute beside your almost intent to hijack. I wrote it publically in _many_ ways i wanted people to help me, but the only answares i got was to take over the packges (and many fake intent to contribute). This really make me sick. > If you cannot incorporate a simple patch in BTS fixing RC bugs into your > packages [1], how will you collaborate using alioth? I would let people apply their patch to the cvs directly being able to catch diffs and reviewing work and seeing people really contribute. > Ever wondered why your appeals for cooperation have no response? Look at > #164354. Have I ever received a response to my offer to help (along with > patch) > in #183896? No. You still do not understand what is being busy might mean (apart the fact that you patch didn't provide a real solution to the bug). I don't know how to demonstrate any more that your opinon about me are faulty. I supposed my self to be the last person who would not let people work with me. I'm still here saying that i'll be happy to cooperate and let you in, but i'm wandering if i'm doing the right thing. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language. pgpSwDLH1yhE5.pgp Description: PGP signature
Re: Why back-porting patches to stable instead of releasing a new package.
On Wed, Jul 23, 2003 at 04:35:04PM +0200, Adrian Bunk wrote: > If you _really_ need or want a more recent version of a package there's > always the possibility to use a backport. So you agree on having a bounce of personal archives on p.d.o rather than a way of getting them in stable trough oficial channels? ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Why back-porting patches to stable instead of releasing a new package.
On Wed, Jul 23, 2003 at 03:54:32PM +0200, Adrian Bunk wrote: > If there was a stable release of Debian once a year Debian 3.1 was > already released. hehe, i knew you would have came to that suggestion sooner or later :) But there are softwares for which it could make sense to update more than once in a year. Wat bout them? ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Why back-porting patches to stable instead of releasing a new package.
On Wed, Jul 23, 2003 at 09:10:01AM -0400, Matt Zimmerman wrote: > This is already in the security team FAQ, and in the developers reference in > section "5.8.5.3 Preparing packages to address security issues", but > apparently it requires further explanation, because this issue comes up from > time to time. I will expand the developer's reference more when I get a > chance. The main points are: That would be cool. > - Security advisories and the associated packages should fix security > vulnerabilities and nothing else. It is irresponsible to "sneak in" > additional changes or try to use a security vulnerability as an excuse to > bypass the normal process for updating a package in stable to fix other > bugs. > > - If your package is so buggy in stable that it is useless, you should have > made an upload to proposed-updates a long time ago. Don't wait for a > security advisory and try to use that to get random bug fixes in. They > will not be accepted as part of a security update. Things are clearer now. You're right: i should have done a new package by time, but you probably ignore that, due to lack of time, i've filed an RFA on phpgroupware which resulted in many mails and no real effort (apart a new version from Tilo Levante few time ago). In this span of time package was subject to many bugfix releases, which i could not care about. Now that I'm back working on it i've to deal with a security issue. What am i supposed to do? Build a new version for the proposed-update procedure? thanks, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Why back-porting patches to stable instead of releasing a new package.
On Wed, Jul 23, 2003 at 03:05:23PM +0200, Adrian Bunk wrote: > Do not even start thinking about something like this. To late: if i wrote it, i thought it :) > If you start asking you will likely find more than thousand packages > where someone will have a good reason for an update of the package in > Debian 3.0. If only every 10th of these updates introduces a new bug > (IMHO a conservative estimation) these packages will bring 100 new bugs > into _a released stable_. I understand that this might happen, and that whould probably end up in a mess, but one point that come out from this small thread is that there are some case in which a backport of a package to stable would be more than a kindness from the Debian developer. This kind issue should be addressed in some way. Just to be sure, i was/am not referring to package like... zope. I mean: i would not release 2.6.1 for stable even if it add really a lot of wanted/nice features. I'm speacking about cases like phpgroupware which provides bugfix relase of the same version, or sensible packages like snort or spamassassin, which hevily depends on up-to-date data/plugins/whatever. I accept your observation on my proposal, but i would more appreciate other ideas and/or solutions. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Why back-porting patches to stable instead of releasing a new package.
On Wed, Jul 23, 2003 at 01:31:52PM +0200, Fabio Massimo Di Nitto wrote: > Because you can never be sure that it will not change the package > behaviour in all its small details and that will not introduce new bugs. ...And that is a rock solid concept if applied in general. > Probably in the specific case it can apply but this is not true for all > packages. Policy/developer-references have to carry the most generic case > as possible, as a best/current practise. So, let's assume that there may be some cases in which our general behaviour might fail, or not be the more appropriate, or simply not the best one. If so... > If you will relax these points you will loose the meaning of having > stable/testing/unstable. Everyone will be encourged to upload to stable to > fix even the most insignificant whishlist bug. ... said that your points are good, it may be useful to define a forum for the discussion of cases like phpgroupware or snort. In the end i whould say that there must be a general behaviour, but we should leave space for discussion: packages are not all the same. I don't like the "pessimistic" approach of saying "we discourage": i would rather say that the behaviour described in Policy/developers-reference are trusted, solid but general, and that some particular cases may be discussed on debian-whatever list. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Why back-porting patches to stable instead of releasing a new package.
On Wed, Jul 23, 2003 at 01:19:25PM +0200, Sander Smeenk wrote: > The same happened with one of my packages: snort. There was a /really/ > old release in stable, because new uploads didn't make it in time. There > were a couple of reasons why it would be good to have a new upstream > version of the snort package installed in stable. But the Debian Policy > forbids it. This is another example, that i like: who would ever use an old IDS? I think that in this case a system administrator would really like to see a new package for his stable box even if it introduce new features, functionalities or uses a different behaviour. > I think Q&A (or others) should take such a package and test it > thorougly, and then maybe decide to put it in stable. Unfortunately such > a thing takes a lot of time and work. So really, putting your own > backported packages on p.d.o seems like the best option. I don't know if QA should test it before releasing to stable (assuming that a new version might be the solution [1]), but i would use this kind of approach. I don't like putting back-ported packages on p.d.o (i should place more than 8 MB of binary packages), because if i do a package back-port and people start using my archive instead of the official one, to me it means the there is something wrong in the procedure to handle uploads to stable or something like that. ciao, [1] i mean that i'd like to see more disucssion on this issue to undestand if i'm wrong or what else. -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Why back-porting patches to stable instead of releasing a new package.
On Wed, Jul 23, 2003 at 11:57:54AM +0200, Fabio Massimo Di Nitto wrote: > > http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-bug-security > > in particular "5.8.5.3 Preparing packages to address security issues" It doesn't answare my question. I should explain my self in a different way. My point is: i understand what said in that paragraph, but what if new version is a bugfix release that does not address only a secutiry issue? I'm not sure that system administrators would like to have a buggy package on their hosts with a security bug fixed, but with many other open nasty bugs. Why that package has nusty bugs? Of course because they where reported after woody release. Let me bring the specific case into the discussion. phpgroupware in woody is a 0.9.14 Release Candidate 3 (which was a feature-freeze release for testing): that package got really a lot of bug fixed and there is now a 0.9.14.006 which is a 0.9.14 in all aspects. 0.9.14.006 neither have new features nor different behaviour: only bugs fixed. "5.5.1 Special case: uploads to the stable distribution" says: -- Basically, a package should only be uploaded to stable if one of the following happens: * a truly critical functionality problem * the package becomes uninstallable * a released architecture lacks the package -- and -- It is discouraged to change anything else in the package that isn't important, because even trivial fixes can cause bugs later on. -- IMHO, these points should be relaxed while speaking about bugfix package release. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Why back-porting patches to stable instead of releasing a new package.
On Tue, Jul 22, 2003 at 06:36:06PM -0400, Matt Zimmerman wrote: > > I've some questions for you, first. > > Would you mind, please, to explain to me why back-porting a patch for a > > buggy package in stable would be better than releasing a new package for the > > stable distribution? > > Do you mind taking this discussion to a public mailing list so that I don't > have to explain over and over? The kind of patch we were talking about was for a security fix. I was asking this question to Matt because the new package i'd like to release for stable also fixes many other bugs. I'm sorry if some of you might think this question to be dumb or stupid, but it's not obvious to me. Please, please, please: no reference/flame about releasing new stable distribution more often. That would not be the point. ciao, P.S.: Matt, if you felt this question to be common, it might be worthy to add some/your explanations to the developers-reference too. -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: [Debconf] Re: The slides for my talk
On Tue, Jul 22, 2003 at 04:20:07PM +0200, Javier Fern?ndez-Sanguino Pe?a wrote: > The problem is, I've not had time to organise all of them in a proper way > so that they can be available from some common place (obviously that would > be w.d.o/events/talks which does have some slides atm) So I would > appreciate if anybody raised his hand to offer help and organise that > information in a better way (I would send him the full archive :-) Sorry, I'm not raising my hand to offer help, but to add a comment for those people going to do it: consider a way to include information about the language of the talk. I've done a talk about debian-jr but in Italian: not many people would get valuable help with it. On my side, i may consider to translate it in English, but that would not be the point (i can do it, but other people might not want to do it for many reasons). ciao, P.S.: Another interesting thing that can be done about talks is to provide some sort of official/suggested slide templates. I was looking for them while i was preparing that talk. -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language. pgpaadSa7qD94.pgp Description: PGP signature
Re: NEWS.Debian support is here
On Fri, Jul 04, 2003 at 01:01:14AM -0400, Joey Hess wrote: > Thanks to Matt Zimmerman and Joe Drew, apt-listchanges will now display > NEWS.Debian entries for upgraded packages. They're displayed before the > regular changelog entries, and Matt plans to later let it be configured > to only display news, if the user wants (more useful for stable users). Is it reasonable to think about some sort of localizzation support for NEWS file? Changes documented there might be worthy of translation. > The NEWS.Debian file is installed as > /usr/share/doc//NEWS.Debian.gz. Always compressed, always with > that name even in native packages. If you use debhelper, upgrade to > 4.1.51 and dh_installchangelogs will install debian/NEWS files for you[1]. Just curious: why not NEWS.gz for native packages? ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language. pgpTIeR1qCp3R.pgp Description: PGP signature
Re: Bug#198957: ITP: email -- Send email from command line, either via MTA or SMTP, with optional encryption
On Sat, Jun 28, 2003 at 04:08:05PM +0100, Millis Miller wrote: > OK, let me see if I can address all the comments I've received so far. [...] Thanks, for your explanations, but i think that the most important issue here is the license. You'd better keep in touch with upstream author and try to convice him to relax the license terms to let us redistribute 'email' at least in non-free section. The best would be to make him change the license up to a DFSG compliant license. This bug should be tagged 'wontfix' untill license issue will be resolved. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language. pgpXWpfJLMPnR.pgp Description: PGP signature
Re: Bug#198665: ITP: pmk -- The pmk project aims to be an alternative to GNU/autoconf (configure scripts).
On Wed, Jun 25, 2003 at 10:20:06AM +0200, Sven Luther wrote: > I though the limit was 60 chars, as stated in one of the debian > documents. > > Friendly, Beside the fact that is was to hurry in sending that mail (synopsis was short enough), as i can read from Policy (I've 3.5.10), it must be less then 80 characters for sure (5.7.1). "Description: " should be shorter then 80 characters (reasonably), so the "" should be about 60-65 characters. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Bug#198665: ITP: pmk -- The pmk project aims to be an alternative to GNU/autoconf (configure scripts).
On Wed, Jun 25, 2003 at 03:18:28AM -0500, Branden Robinson wrote: > * lose the article Why? > * do not capitalize the beginning of the description unless a proper > noun, proper adjective, abbreviation, or acronym requires it Why? ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language. pgpwos4bClfF7.pgp Description: PGP signature
Re: Bug#198665: ITP: pmk -- The pmk project aims to be an alternative to GNU/autoconf (configure scripts).
On Tue, Jun 24, 2003 at 10:59:19PM +0200, Marek Habersack wrote: > It's not quite a substitute, as it won't reuse autoconf's configs etc. How > about "A tool for configuring software source similar to GNU Autoconf"? Sorry for my previous reply to this message, your suggestion is definitely good. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language. pgpYTsqJvgowt.pgp Description: PGP signature
Re: Bug#198665: ITP: pmk -- The pmk project aims to be an alternative to GNU/autoconf (configure scripts).
On Tue, Jun 24, 2003 at 10:59:19PM +0200, Marek Habersack wrote: > It's not quite a substitute, as it won't reuse autoconf's configs etc. How > about "A tool for configuring software source similar to GNU Autoconf"? I see your point, but your suggestion is still too long: it should be rephrased to stay within 60-65 characters. What about "A source configuring tool like GNU/Autoconf"? ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language. pgp17SXQXTPUn.pgp Description: PGP signature
Re: Bug#198665: ITP: pmk -- The pmk project aims to be an alternative to GNU/autoconf (configure scripts).
On Tue, Jun 24, 2003 at 09:30:31PM +0200, Marek Habersack wrote: [...] > Description : The pmk project aims to be an alternative to GNU/autoconf > (configure scripts). Description field is inappropriate, use something like: Description: A GNU/autoconf alternative. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Bug#190302: Misusage of changelog!
On Tue, May 27, 2003 at 08:31:39AM -0700, Brian Nelson wrote: > Uhh, your packages include the upstream source, and therefore the > upstream source is "part of your package working". So it is part of my work, and changes to my work should be included in changelog.Debian... > > To demostrate how much this issue is stupid, i'll make any one here > > happy by including the entire upstream changelog in > > changelog.Debian.gz, next time i'll build a new upstream. ... And since all upstream changes are included in upstream changelog, there is nothing wrong or childish in including the entire file in the changelog.Debian. have a nice day, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Bug#190302: Misusage of changelog!
On Tue, May 27, 2003 at 05:12:22PM +0200, Mathieu Roy wrote: > I can. > You wrote that you have "to list each change in the upstream > changelog" to know which bug can be declared as closed. Right? That is what i wrote, but is not what i meant: it have a difference meaning if you take it out of the context, but my english is not so good to commit that i explained my self. I'll rephrase: -- You people told me that: - If i make a change to a package i've to list my changes in the package changelog (Matt Zimmerman, no one ever objected this). - If i build a new upstream, i've to list each change in the upstream changelog that let me declare a bug as closed; change that does not refer to the Debian package (but to the original upstream), and that i did not applied as part of my package working (because it was applied from the upstream). -- The second contradict the first, and does not follow what stated in policy about debian chagelog file (13.7 an 5.3 of policy). > Do you think that users should list "each change in the upstream > changelog" to know how the bug they submitted as been closed? If you mean "read" by the word "list", of course i do. First came the upstream changelog, then the Debian one. > So the only way you have to demonstrate it is to act as a child? So the only way to confute my observation is to bring childish arguments to the discussion? > You have an easy solution: follow the 4. of the Debian social > contract ( http://www.debian.org/social_contract ). I'm already doing it in many ways and, untill now, no one has conviced me that this would be a real improovement. have a nice day. -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Bug#190302: Misusage of changelog!
On Tue, May 27, 2003 at 03:11:11PM +0200, Michael Banck wrote: > Didn't you just complain that people said you wouldn't have common > sense? > > How odd. Not that odd: if someone feels to be in the position of telling me that i've no common sense or express any other kind of colorful expression about my works, i thought i should have given him a real reason. The real odd think is that there are really a lot of people who think to be in the right position to point other maintainers as "loosers" or "without common sense"; and many are in charge of something in Debian. That make me wander... Have a nice day, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Bug#190302: Misusage of changelog!
On Tue, May 27, 2003 at 03:10:36PM +0200, Mathieu Roy wrote: > Anybody has the right to express a point of view on anybody else work, > right? I'll try to keep in mind this gentlemen example of "expressing a point of view on anybody else work" next time, so i'll not misunderstend it with an offense. > You said you have "to list each change in the upstream changelog" to > know which bug can be declared as closed. And that's, as maintainer, > your job, isn't it? But is it users job to do it too? I do not understand that: could you rephrase? > Is this mature? It is as much mature as all the argument you people brought to this discussione, from my point of view. If you asked that question yourself, you're probably going to understand my point. > You still did not answer to the question: is it too much extra work > you can afford to add in the changelog what permits you to declare a > bug closed? Speaking about entry like "New upstream closes #...", my position is: This kind of request is futile, redundant and of no real need in _any_ case. Hunting maintainers down for a log entry of that kind is a waste of time either for the maintainer and for the hunters. All the arguments brought to this discussion to confute my observation are so childish and contraddictory, that the only way i have to demonstrate it is to act as previously stated. Have a nice day, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Bug#190302: Misusage of changelog!
On Tue, May 27, 2003 at 10:47:15PM +1200, Nick Phillips wrote: > If your changelog merely says "New upstream version, closes: #123 #456", > it's no help whatsoever, and I will (rightly) think that you suck. This is debian-devel: as soon as one declares he stops reading a thread, beasts came out and offends by praying on the tail of a discussion. You discriminate and offend people only by reading a list of changes, and i should be the one who suks (supposing i'm not right)? > FFS, it's a *change*log -- so log the effing changes in it. The contraddiction of all this tread, is that: if i make a change to a package i've to list my change in the package changelog (Matt Zimmerman, no one ever objected this). If i build a new upstream, i've to list each change in the upstream changelog that let me declare a bug as closed; change that does not refer to the Debian package (but to the original upstream), and that i did not applied as part of my package working (because it was applied from the upstream). To demostrate how much this issue is stupid, i'll make any one here happy by including the entire upstream changelog in changelog.Debian.gz, next time i'll build a new upstream. have a nice day, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Bug#190302: Misusage of changelog!
On Tue, May 27, 2003 at 12:47:10AM -0400, Matt Zimmerman wrote: > It is. Unfortunately, common sense is not always as common as we would > like. Are you trying to say that i've no common sense? ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Bug#190302: Misusage of changelog!
On Mon, May 26, 2003 at 01:13:06PM -0400, Matt Zimmerman wrote: > A changelog entry which says only Closes: # is worthless; it is the > same as leaving the changelog empty and closing the bug by hand. We are not speaking of a generic line with a "Closes: #1..."; we are speaking of one of the most common chages: new upstream source close some bugs. I don't realy see the point in bothering the maintainer in further explanation of what happened: it is obvious and anyone has _all_ the information he may need to find it for himself. Should it ever happen to me, i would exactly think: I do spend my time maintaing, fixing upgrading the software, keep in touch with the upstream, forwarding report or any othern thing needed, so how do you now dare to bother me because i did not write a verbose, futil and redundant changelog entry? How could you tell me that writing what you wanted, would have taken me only few minutes? Are you teling me that what i do isn't enough? Your comment is only a waste of time for me that read the mail and for you who wrote it: you would surely have spent less time seeing it for yourself then reopening that bugs. > This is not a bother to maintainers, and no amount of enhancement to > apt-listchanges relieves the maintainer's responsibility to document his > changes. I do think that complining because a maintainer worte "New upstream closes: #1...", do not lead anywhere: it only bother the maintainer. Should i ever write such an entry, please don't waste your time and mine. Do you know what? I've more important things to do than spending my time reading the last, never ending thread, about the most stupid issue in the open source world. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Bug#190302: Misusage of changelog!
On Mon, May 26, 2003 at 05:15:48PM +0200, Philipp Matthias Hahn wrote: > Example: > 1. detect bug > 2. run reportbug > 3. sees, other person was faster and reported bug 42. > 4. wait for new version > 5. read changlog > 6. what the heck was bug 42, was it mine ? $ w3m http://bugs.debian.org/42 I'm not so bothered by writing 32 characters to know what was it. Off-line? Wait until on-line.. Do you know how not to bother maintainers? Ask to the apt-listchanges developers to add a feature to download bugs report for each bug closed in changelog. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Bug#190302: Misusage of changelog!
On Mon, May 26, 2003 at 02:37:21PM +0100, Colin Watson wrote: > Perhaps the submitter might like to know what was changed to fix the > bug? I don't know about you, but I usually actually go and confirm the > fix rather than blindly accepting it. I don't know you, but i usually actually go and read the upstream changelog to know haw it was fixed: if i'm not satisfied (that may happen), i go trough reading the source if i like. I'm not blind, i can read. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Bug#190302: Misusage of changelog!
On Mon, May 26, 2003 at 02:45:16PM +0200, Josip Rodin wrote: > Yes, but there's still no bloody point in making the submitter hunt around > for information that the maintainer already knows and for which it takes > them full 10 seconds per bug to list (15 if they type very slowly). Submitter receive a mail from bts which include the message that opened the bug: what should he hunt for exactly? ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Bug#190302: Misusage of changelog!
On Mon, May 26, 2003 at 02:26:10PM +0200, Andreas Metzler wrote: > Which does not help everybody else at all, who have just > the meaningless changelog and are using apt-listchanges to read it > before installation. I don't see even this: are you warried about grave bugs? Use apt-listbugs. BTW, you can always grep the upstream changelog from the deb file using dpkg-extract. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: Bug#190302: Misusage of changelog!
On Mon, May 26, 2003 at 11:16:51AM +0200, Gerfried Fuchs wrote: > You are plainly misusing your changelog for closing #190302. This has > *nothing* to do in the changelog, there are no *changes* in this upload > that address this. Rather send a mail to [EMAIL PROTECTED] explaining why > you close them. I agree on this, but > Btw., your line for "Upstream fix: closes:" is not very helpful for the > bug submitters neither. They'd have to check their records to see what > this bug really was. Please add informations on what was fixed so it can > be seen offline, too. I really don't see the point in this. Submitters always have a copy of their report, so they have evrything they need. "New upstream closes: #1, #2, #3" implyes an update of the upstream changelog file so it's worth of checking: listing changes already documented would be redundant and not so helpful. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: The Debian Mentors Project
On Tue, May 13, 2003 at 05:41:12PM +0200, Emile van Bergen wrote: > That's not mutually exclusive. Also, you ask who would ever wish to > delegate the maintainership of a package. I think the answer is every DD > who has filed a RFA on a package. RFA is a Request For Adoption, not a delegation. There is no sense in makeing a delegation. If one cannot/don't want to maintain a package any more, he lets other people to take it (RFA or O). > I know. However, there are *existing* packages for which DDs don't > always have enough time or interest. If you think that isn't true, then > what are all those orphaned packages doing on WNPP? [...] > I know. But because of the packages up for adoption, and the orphaned > packages, I was under the impression that the DDs need help with those > packages. So what's the point? there is someone who wants to maintain a package? Well: he should take it, close as many bugs as possible, produce a good working release, and bring us a results. Then what? what does he really need? a repository for his work or a sponsor? Both you'd say, and that's it. For the former he may use alioth, for the later he needs a place to look for a willing sponsor. > If that's not the case, why are those orphaned packages not removed > outright? They are periodically removed. > Well, I didn't see why you would object to the second sentence. If > somebody's able to maintain a package through a sponsor well, he may > still have no desire to become a DD. So that's the point: you didn't got my reply at all. That sentence is unfair because it blame the NM process, while mentors.debian.net try to be a Debian subproject. Debian that blames Debian? > Well, mentors.debian.net exists, whereas the one you're describing does > not, so apparently people felt more need for the former. http://www.internatif.org/bortzmeyer/debian/sponsor/ Have you ever seen our "Developer's corner"? ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: The Debian Mentors Project
On Tue, May 13, 2003 at 12:07:12PM +0200, Emile van Bergen wrote: [...] > Regardless, I actually think it's a wonderful scaleability measure to > provide some infrastructure that allows DDs to delegate some of the > packaging work to NMs in the queue, who can prove that they are worth > their salt, or to non-DDs, who can contribute to the project in a > controlled manner that way. This is conceptually wrong: if a DD wishes to co-maintain his package, Debian offers alioth.d.o which is already up and running; if he wishes to delegate... who wishes to delegate the maintainership of a package? I'd rather say that a DD sponsors other non-DD contributions. There is a plenty of ways a NM can contribute/join Debian: packaging is only the simpliest. Try to take some job or a package from the QA, a task from http://www.debian.org/devel/todo/ or anything that can came out from the "Developer's corner" section on the main site. Non-DDs contributing in this way do not help Debian: have you ever read of our lacks of packages? You don't, because we haven't. Do you want to proove your salt? You can do the same things a NM can do (see above). You insist in maintaining a package, well take one and work on alioth in the mean while. > I think there is a niche for such non-DD contributors. No there is not. The fact is that if one wants to contribute Debian, that is to say help the DDs, he should work in those fields Debian needs help. > Allowing DDs to take advantage of the work of lesser gods, whenever that > is practical and useful, seems a good thing for all parties concerned. that's a pity... there is no one here who feels to be a god: unfortunately, there are many outside here that think to be... looser gods. > And no, IANADD. We don't need you to tell us: db.debian.org does it. Finally, i do not understand why you quoted my mail... I was only objecting with this sentence: But becoming a DD is a long and painful way. Many developers just want to make their software available to Debian users but not become DDs. They are invited to upload their packages here and tell other users about this server. If you ask me what i think about mentors.debian.net i'd say we do not need such a service: i would have made any contributor to use alioth (register, work on your favorite package and release it). A better service would have been to create a place to coordinate people looking for sponsorship with those willing to offer it. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Re: The Debian Mentors Project
On Tue, May 13, 2003 at 10:02:11AM +0200, Christoph Haas wrote: > Please bear with me but from what I was told by a number of package > maintainers it is a really long way until one has become a DD. Just > because Daniel was assigned an AM does not mean there is a guarantee he > will get his DD access in the next weeks. I doubt that. That's may be true or not: i joined Debian in less than a month. There are many factors around that issue. I want to add my two euro-cents too: IMHO is very unfair, for a Debian project, to blame another Debian Project or Debian it self (NM is part of Debian). More over, it seems to me that you intend to help any non-Debian developer to distribute his software regardless of the fact he may want or not to join Debian: that's why i also don't see the point in haveing such a sentence. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language.
Bug#188437: ITP: zope-xmlmethods -- Set of methods to perform XML processing on Zope objects
Package: wnpp Version: unavailable; reported 2003-04-10 Severity: wishlist * Package name: zope-xmlmethods Version : 1.0.0 Upstream Author : Ariel Partners LLC * URL : http://zopexmlmethods.sourceforge.net * License : BSD Description : Set of methods to perform XML processing on Zope objects ZopeXMLMethods consists of a set of methods that can be applied to Zope objects to perform various types of XML processing. In general each type of method is applied to a Zope object in the same manner that a standard DTML Method or Python Script might be applied. The only requirement for the source Zope object is that it must somehow produce XML. Currently, this XML must be in ASCII or UNICODE form, but in the future additional formats such as DOM or SAX events will be supported. ZopeXMLMethods includes a Cache Manager that is specialized to notice changes to the XML source files and to store cached contents in files in the filesystem, rather than the Zope object database. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux darkness 2.4.20 #1 Wed Mar 26 08:45:16 CET 2003 i686 Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL set) -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][-A-Za-z]*[iy]'?s$ | as fine or rude sentences have Infinite loop: see `Loop, infinite'.| something in common: they Loop, infinite: see `Infinite loop'.| don't depend on the language.
Bug#188435: ITP: zodb3 -- A persistent system for Python objects
Package: wnpp Version: unavailable; reported 2003-04-10 Severity: wishlist * Package name: zodb3 Version : 3.1 Upstream Author : Zope Corporation * URL : http://sourceforge.net/projects/zodb/ * License : http://www.zope.org/Resources/ZPL Description : A persistent system for Python objects Actually this is an intent to split the ZODB from Zope package. I'll probably provide more than a package, and perheps use the same upstream for ZEO[1] (I'm still not sure) [1] http://bugs.debian.org/186567 -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux darkness 2.4.20 #1 Wed Mar 26 08:45:16 CET 2003 i686 Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL set) -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][-A-Za-z]*[iy]'?s$ | as fine or rude sentences have Infinite loop: see `Loop, infinite'.| something in common: they Loop, infinite: see `Infinite loop'.| don't depend on the language.
file format for debian/copyright
What about having control file like format for copyright files? --- copyright --- Packaged-By: Luca - De Whiskey's - De Vitis <[EMAIL PROTECTED]> Packaged-On: Sun, 08 Dec 2002 00:52:10 +0100 Original-Source: ftp://ftp.example.org/upstream-1.0.0.tar.gz Upstream-Authors: Foo Bar Copyright: GNU General Public License (file:///usr/share/common-licenses/GPL) This package is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 dated June, 1991. This package is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this package; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. --- copyright --- This format could improove the accuracy of lintian checks (for example, copyright-should-refer-to-common-license-file-for-gpl may fail to understand that GPL is only mentioned in the copyright notice, and is not the type of the license); we could also provide some frontend to grep-dctrl to query that file. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][-A-Za-z]*[iy]'?s$ | as fine or rude sentences have Infinite loop: see `Loop, infinite'.| something in common: they Loop, infinite: see `Infinite loop'.| don't depend on the language.
Re: Pick a name, any name...
On Wed, Nov 27, 2002 at 11:03:58AM +0100, Roland Mas wrote: > Current candidates include: > - Actarus: Actarus is the pilot of Goldorak/Grendizer/what's it called > in your language. No particular reason except that it was a very > famous cartoon here in France some ten-fifteen years ago. Alcor is > another name in that series. I like either Actarus or Alcor :) > - Your idea here. Or the simpliest forge.debian.org, or smithers.debian.org which also recall the Simpson character and his role of secretary (after all it should be the secretary for our projects). ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][-A-Za-z]*[iy]'?s$ | as fine or rude sentences have Infinite loop: see `Loop, infinite'.| something in common: they Loop, infinite: see `Infinite loop'.| don't depend on the language.
Re: debconf template translations from ddtp
On Tue, Nov 26, 2002 at 05:54:21PM -0600, Steve Langasek wrote: > > We've started the translation of debconf templates some weeks ago. > > See http://ddtp.debian.org/debconf/gnuplot/ddts-stat.png It seems that you don't use po-debconf: isn't it? AFAIK we all should switch to po-debconf for a better translation system. > Is it your intention for these translations to only be made available on > the ddtp website, instead of being submitted directly to maintainers as > bug reports? I would like to recive the translation as bugs, so i hope you'll set it up in this way sooner or later. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][-A-Za-z]*[iy]'?s$ | as fine or rude sentences have Infinite loop: see `Loop, infinite'.| something in common: they Loop, infinite: see `Infinite loop'.| don't depend on the language.
Stop trolling! [ Re: Debian Desktop? Desktop Debian? ]
On Mon, Nov 25, 2002 at 04:57:07PM -0600, Brandt Dusthimer wrote: >Hrm... topics like this just seem to keep turning up. Folks, not to > be nasty or anything, but Debian's not going to change anytime soon. You are going to troll: if you don't exactly konw what you are going to write about, please don't. You could ask something about it first. http://www.debian.org/devel/debian-desktop Please, stop trolling on loosing user and such. Bring these subject on a more appropriate forum (/dev/null) or stop sending that amazing amount of mail: use your time productively working on you (supposed) Debian distribution. Those who believes in Debian propose, work on, help with changes; the other people keep on writing unusefull mail, wasting time. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][-A-Za-z]*[iy]'?s$ | as fine or rude sentences have Infinite loop: see `Loop, infinite'.| something in common: they Loop, infinite: see `Infinite loop'.| don't depend on the language.
Re: New maintainer process
On Fri, Nov 22, 2002 at 02:45:59PM +0100, Joerg Jaspert wrote:
> I dont know if anyone else has something, but i sent tbm a postgresql
> dump from 2002-07-20. Not very actual, but its there.
Cool, that means that nm.d.o is going to be back (not as up to date as we
would it to be, but by now it's the best we can do).
> But hey, every AM should know his NM's and their state. :)
:) that's why i suggested to ask to -newmaint.
ciao,
P.S.: this discussion lead me to a question: is it possible that we do not
have any kind of backup for thing like that? I mean: even something like cvs
offers a kind of backup, periodical dump of the db and such should save some
other kind of valuable data. What if {bugs,db}.d.o catch fire?
--
Luca - De Whiskey's - De Vitis | Elegant or ugly code as well
aliases: Luca ^De [A-Z][-A-Za-z]*[iy]'?s$ | as fine or rude sentences have
Infinite loop: see `Loop, infinite'.| something in common: they
Loop, infinite: see `Infinite loop'.| don't depend on the language.
Re: New maintainer process
On Fri, Nov 22, 2002 at 09:52:13PM +1000, Andrew Pollock wrote: > Hi, > > Since satie.d.o has been destroyed, where does this leave the NM process? The web site is only a nice fornt-end for the applicants to know something about you place in the queue and the ste you passed. Please, read http://www.debian.org/devel/join or http://www.debian.org/devel/join/newmaint or, at least, contact [EMAIL PROTECTED] to know what you need. If you need a sponsor/advocate you may ask for one on debian-mentors@lists.debian.org or here on [EMAIL PROTECTED] ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][-A-Za-z]*[iy]'?s$ | as fine or rude sentences have Infinite loop: see `Loop, infinite'.| something in common: they Loop, infinite: see `Infinite loop'.| don't depend on the language.
Bug#143446: ITP: zope-cmfldap -- Zope CMF LDAP membership management tools
Package: wnpp Version: N/A; reported 2002-04-18 Severity: wishlist * Package name: zope-cmfldap Version : 1.2 Upstream Author : Jens Vagelpohl <[EMAIL PROTECTED]> * URL : http://www.dataflake.org/ * License : see below. Description : Zope CMF LDAP membership management tools CMFLDAP is a Zope CMF product that replaces the standard membership management tools (Membership Tool, Member Data Tool) with a set that speaks LDAP. Copyright (c) Jens Vagelpohl. All right reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions in source code must retain the above copyright notice, this list of conditions, and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Jens Vagelpohl requests that attribution be given to Zope in any manner possible. A significant investment has been put into Zope, and this effort will continue if the Zope community continues to grow. This is one way to assure that growth. 4. All advertising materials and documentation mentioning features derived from or use of this software must display the following acknowledgement: "This product includes software developed by Jens Vagelpohl for use in the Z Object Publishing Environment (http://www.zope.org/)." In the event that the product being advertised includes an intact CMFLDAP distribution (with copyright and license included) then this clause is waived 5. Names associated with Jens Vagelpohl must not be used to endorse or promote products derived from this software without prior written permission from Jens Vagelpohl. 6. Modified redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by Jens Vagelpohl for use in the Z Object Publishing Environment (http://www.zope.org/)." Intact (re-)distributions of any official CMFLDAP release do not require an external acknowledgement. 7. Modifications are encouraged but must be packaged separately as patches to official software releases. Distributions that do not clearly separate the patches from the original work must be clearly labeled as unofficial distributions. 8. In the interest of improving this product the author requests that changes be made available to him. This is not mandatory but part of good open source development etiquette. Disclaimer THIS SOFTWARE IS PROVIDED BY JENS VAGELPOHL ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL JENS VAGELPOHL OR HIS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux pinot 2.4.18-xfs #1 Sat Mar 16 22:59:30 CET 2002 i686 Locale: LANG=C, LC_CTYPE=C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#143442: ITP: zope-ldapuserfolder -- The Zope LDAP user folder
Package: wnpp Version: N/A; reported 2002-04-18 Severity: wishlist * Package name: zope-ldapuserfolder Version : 1.3 Upstream Author : Jens Vagelpohl <[EMAIL PROTECTED]> * URL : http://www.dataflake.org * License : see below. Description : The Zope LDAP user folder This product is a replacement for a Zope user folder. It does not store its own user objects but builds them on the fly after authenticating a user against the LDAP database. Copyright (c) Jens Vagelpohl. All right reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions in source code must retain the above copyright notice, this list of conditions, and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Jens Vagelpohl requests that attribution be given to Zope in any manner possible. A significant investment has been put into Zope, and this effort will continue if the Zope community continues to grow. This is one way to assure that growth. 4. All advertising materials and documentation mentioning features derived from or use of this software must display the following acknowledgement: "This product includes software developed by Jens Vagelpohl for use in the Z Object Publishing Environment (http://www.zope.org/)." In the event that the product being advertised includes an intact CMFLDAP distribution (with copyright and license included) then this clause is waived 5. Names associated with Jens Vagelpohl must not be used to endorse or promote products derived from this software without prior written permission from Jens Vagelpohl. 6. Modified redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by Jens Vagelpohl for use in the Z Object Publishing Environment (http://www.zope.org/)." Intact (re-)distributions of any official CMFLDAP release do not require an external acknowledgement. 7. Modifications are encouraged but must be packaged separately as patches to official software releases. Distributions that do not clearly separate the patches from the original work must be clearly labeled as unofficial distributions. 8. In the interest of improving this product the author requests that changes be made available to him. This is not mandatory but part of good open source development etiquette. Disclaimer THIS SOFTWARE IS PROVIDED BY JENS VAGELPOHL ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL JENS VAGELPOHL OR HIS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Debian Release: 3.0 Architecture: i386 Kernel: Linux pinot 2.4.18-xfs #1 Sat Mar 16 22:59:30 CET 2002 i686 Locale: LANG=C, LC_CTYPE=C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
