Re: Processed: Fixed in NMU of tetex-base 2.0.2c-2.1
Hi Frank, > Please calm down. Sure, it isn't usual to upload such a quick NMU, but > (as Goswin already pointed out) such a bug that makes a package > uninstallable that is a common build-depends can really hurt the > autobuilders. You're free to discuss with lamont how to handle such > cases in the future (and communicating him your anger) but please > don't overreact. > Whats about uploading such packages to experimental more often. As i am being told on IRC, experimental is autobuilded on most architectures now. Greetings Martin -- Bachelor: A man who chases women and never Mrs. one.
Re: please post listing and status of NEW queue
Hi Anibal, On Saturday, 12 Feb 2005, Anibal Monsalve Salazar <[EMAIL PROTECTED]> wrote: > On Mon, Feb 16, 2004 at 02:50:27PM -0500, Joe Nahmias wrote: > >Package: ftp.debian.org > >Severity: wishlist > > > >Hello ftp-masters, > > > >It would be nice if there were a webpage (updated eg. once a day) > >listing the packages in the NEW queue in (roughly) the order they will > >be processed in. Perhaps also the last 10-15 packages that were acted > >on and the date of the action, so that it is easier to estimate the wait > >time in NEW. > > http://qa.debian.org/~anibal/debian-NEW.html > > The above page is based on previous work done by Peter Reinholdtsen. > > It still work in progress. > > Any input is welcome. from the page: "Total package count: 356" is that the number of source package, or the number of binaries? Greetings Martin -- Too many people are thinking of security instead of opportunity. They seem more afraid of life than death. -- James F. Byrnes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mirror the Packages files _after_ the packages!
Hi Dan, On Wednesday, 09 Feb 2005, Dan Jacobson <[EMAIL PROTECTED]> wrote: > I know you Debian people think it's just hilarious when users try to > apt-get upgrade during the period after when the Packages files > arrive on the mirrors, but before the packages they describe have > fully arrived. see http://lists.debian.org/debian-www/2005/01/msg00199.html Greetings Martin -- Love is the only game that is not called on account of darkness. -- M. Hirschfield -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mirror the Packages files _after_ the packages!
Hi Jeroen, > How mirrors do their mirroring is up to the local mirror administrator, > not to the general debian developer's community. Debian could promote > this two-phase mirroring a bit more maybe, and/or provide nice scripts, > that's probably why #6786 is still open. > > BUT DEBIAN CANNOT IN ANY WAY FORCE/CONTROL HOW MIRRORS OPERATE, > especially not the secundary mirrors. But Debian could at least offer an updated rsync-script. Its over a month ago, i posted an updated script to [EMAIL PROTECTED] but noone yet cared and updated it. Greetings Martin -- What's done to children, they will do to society. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Is NEW processing on hold? (was: Question for candidate Towns)
Hi Marc, On Monday, 07 Mar 2005, Marc Haber <[EMAIL PROTECTED]> wrote: > On Sat, 5 Mar 2005 18:03:50 +0100, Nico Golde <[EMAIL PROTECTED]> wrote: > >* Frank Küster <[EMAIL PROTECTED]> [2005-03-05 17:52]: > >>http://lists.debian.org/debian-devel-changes/2005/03/msg00019.html > > > >But it is very slow at the moment. > > Yes. And the people responsible refuse - as usual - to communicate. So > nobody knows about the reason. Might it be that they try to get no new packages into the archive before a release? It is just a guess... Greetings Martin -- Old Japanese proverb: There are two kinds of fools -- those who never climb Mt. Fuji, and those who climb it twice. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Do not make gratuitous source uploads just to provoke the buildds!
Hi Hamish, On Saturday, 12 Mar 2005, you wrote: > Is there anything that can be done to help with arm/mipsel? Not uploading any new packages *g* As it has been said earlier, the machines are back, but just need to catch up. So just waiting might be the easiest thing to do. Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Do not make gratuitous source uploads just to provoke the buildds!
Hi Ingo, On Saturday, 12 Mar 2005, you wrote: > On Sat, Mar 12, 2005 at 02:06:24PM +0100, Martin Zobel-Helas wrote: > > > As it has been said earlier, the machines are back, but just need to > > catch up. So just waiting might be the easiest thing to do. > > More machines can catch up faster than few can do. > When one machine out of a dozen machines is unavailable, it has less impact > than one machine failure out of two machines, although the chances will > raise that a machine will fail somewhen with more machines. But the impact > is less critical... > I can't understand why no additional machines are being accepted. Please clarify this with the wanna-build admin(s). Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Very informative changelog entry (was: Accepted jwhois 3.2.2-2 (i386 source))
Hi Peter, On Monday, 14 Mar 2005, you wrote: > jwhois (3.2.2-2) unstable; urgency=low > . >* Updated default configuration. > (Closes: Bug#201603, #202192, #203022, #208573, #210631, #210811, > Bug#211690, #212182, #212184, #212418, #212607, #212608, > Bug#213298, #216652, #216653, #221903, #223782, #237577, > Bug#237578, #241998, #242452, #244111, #244825, #244939, > Bug#246189, #250816, #278896, #270303) this is not a very informative changelog entry, even if you only changed RIPE IP spaces. Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: status of buildds?
Hi Ingo, On Tuesday, 15 Mar 2005, you wrote: > On Mon, Mar 14, 2005 at 11:37:31PM -0800, Thomas Bushnell BSG wrote: > > > > >The s390 porting team can perfectly well do what the hurd-i386 porting > > > >team does: build them themselves. I mean, umm, you don't have to be > > > >hooked into w-b to upload packages. > > > Why are some architectures refused the same service that others get? > > You have to ask w-b for that one. But regardless, which is better? > > Do nothing, because w-b isn't doing what s390 wants, or deal with it > > oneself? Instead of fighting about who should solve the problems, why > > not solve it? > > It's the job of w-b admins to add new buildds in a timely manner. If they > don't do that, they simply fail (one significant part of) their job. or they just have their reasons not to do. -- Please do NOT CC me, i am reading the lists i am posting to. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: The sarge release disaster - some thoughts
Hi Adrian, On Tuesday, 15 Mar 2005, you wrote: > The timeline for another failed release date: > - August 2nd 2004: announcement > - August 8th 2004: "Official security support for sarge begins" > - September 15th 2004: announced release date > > The milestone that included the start of the official security support > for sarge was only 6 days after the announcement, but is was missed by > more than 6 months. > > Whyever it was expected to get testing-security for sarge that quick, it > should have been obvious 6 days later that it wasn't possible that > quick. > > What would have been a second plan? > Use testing-proposed-updates. That wouldn't work eiter. T-P-U and T-S are using the very same chroot on most machines. So if T-S doesn't work, T-P-U won't either. The problem here is, that we were/are still missing wanna-build databases for T-P-U/T-S for some architectures. I think the real problem within Debian is the lack of communication of some people within the project. If the wanna-build admins and/or the ftp-masters would have said: "stop, were are still missing , without it you will not be able to release" everyone would have understood. Also i hoped the release team and the ftp-masters would have worked on the current release instead of planing for the next on. Having all these people together sitting in one room working on the current release would have been much more prodcutive. Perhaps they did. But they didn't told us. Also some lack of communication. At least, what the rest of the Debian community sees is the mail Steve send via debian-devel-announce. This mail mainly covers etch, not sarge. I wish all these people would communicate much more and tell us facts. Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: The sarge release disaster - some thoughts
Hi Pierre, On Tuesday, 15 Mar 2005, you wrote: > Le Mardi 15 Mars 2005 16:15, Martin Zobel-Helas a écrit : Full ACK on the whole mail. Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Accepted valknut 0.3.7-1 (i386 source)
Hi Pasi, On Friday, 18 Mar 2005, you wrote: > Changes: > valknut (0.3.7-1) unstable; urgency=high > . >* New upstream release (Closes: #289643, #269952, #265284, #270096, > #286234) is there any reason for not giving some more explanation, when closing bugs with urgency=high and only listing "New upstream release" as only changelog entry. I would like to have some more explanation for this in the changelog. Also Debian Developers reference 6.3.1 gives some good advice on "Writing useful changelog entries". Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: getting unstable lintian & linda into stable
Hi Christoph, On Friday, 11 Nov 2005, you wrote: > Maybe lintian could detect if if was running on stable when it should > be on unstable, and warn the user. I'm not sure how to do this, since > there are legitimate uses on stable where you wouldn't want to get the > warning. it could parse the changelog entry and try to detect if the upload is for stable-(security|proposed-updates). If not, and "APT prefers stable" (stolen from reportbug), lintian/linda could give a warning. This requires lintian/linda to run in the same enviroment than the package has been build (ie. a chroot). Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Stephen Frost MIA?
Hi José, how about sending this to Frontdesk <[EMAIL PROTECTED]> or MIA, <[EMAIL PROTECTED]> instead of spamming debian-devel with that? Greetings Martin > Hi, Stephen. > > Having sent you e-mails with my last answers to the Tasks&Skills > stage of the NM process on 2005/10/05, and having received receipt > confirmation from you on 2005/10/18, i still have no answer from you. > Moreover, i have ping'd you on 2005/10/07, 10/12, 10/15 and 21/11; > No answer so far either. > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Anthony Towns: What I did today
Hi AJ, On Friday, 13 Jan 2006, you wrote: > Things I did today: > > 2. Removed the empty SuperH architecture from the archive (binary-sh). > > Coincidence? You decide. > > URL: http://azure.humbug.org.au/~aj/blog/2006/01/13#2006-01-13-sh-irts Nice you have done this, but Planet is definitely not the correct place to document changes like this. I would find it more appropriate to inform fellow DDs either via debian-devel@ or [EMAIL PROTECTED] Not all developers read planet.debian.org. To get that clear, i don't want to criticize you removed unneeded SuperH architecture from the archive, but where you document changes like this. Greetings Martin PS: CC'ed -devel to get fellow developers informed about your changes. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Anthony Towns: What I did today
Hi Anthony, On Saturday, 14 Jan 2006, you wrote: > On Fri, Jan 13, 2006 at 04:22:50PM +0100, Martin Zobel-Helas wrote: > > On Friday, 13 Jan 2006, you wrote: > > > Things I did today: > > > 2. Removed the empty SuperH architecture from the archive (binary-sh). > > > Coincidence? You decide. > > > URL: http://azure.humbug.org.au/~aj/blog/2006/01/13#2006-01-13-sh-irts > > Nice you have done this, but Planet is definitely not the correct place > > to document changes like this. I would find it more appropriate to > > inform fellow DDs either via debian-devel@ or [EMAIL PROTECTED] Not all > > developers read planet.debian.org. > > I think you'll find the correct place is the -sh list, which was notified: > > http://lists.debian.org/debian-superh/2002/04/msg00010.html > > The "sh" arch in unstable has consisted of "Architecture: all" packages only > since then. Even so you informed the porters it would have been nice to just drop a mail on -devel? Where is the problem in writing a mail to -devel? Going this way everybody would be informed and noone can complain afterwards. Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how to link 2 bug reports ?
Hi Marc, On Sunday, 29 Jan 2006, you wrote: > Hi all, > > i've done the bug report #350119 last week (providing a patch) and just > seen that this patch fixes #342008. Is it a way to 'link' them in the > BTS? (as i'm not a DD) mail to "[EMAIL PROTECTED]" and sent in the body: merge 350119 342008 thanks Greetings Martin PS: http://www.debian.org/Bugs/server-control -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: timezone data packaged separately and in volatile?
Hi Daniel, On Monday, 06 Feb 2006, you wrote: > On Tue, Feb 07, 2006 at 02:30:01PM +1100, Anand Kumria wrote: > > But that doesn't mean that we can issue an update to a stable package. > > > > Currently they are mainly done for security purposes -- but stable updates > > should not be confined to only that. They should be done to keep the > > system functional. > > > > I also think volatile is precisely the wrong place to put this kind of > > data -- it isn't part of the default apt.sources for one thing; and it > > places an extra burden on the maintainer(s) (who know have to track > > three different upgrade paths, etc.). > > > > It would be good to hear from the glibc maintainers if there are any > > issues addressing bugs such as: 345479, 351049 with an update for > > stable. > > It's not us, but the stable maintainer, that you'd have to talk to; > he has traditionally not been interested in these sorts of updates to > stable as far as I know. I talked to Joey another day, and he said, we should mail him about, and he will decide if this could go in via a point release. I hearby mail him (CC). Lets see what happens. Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Propose exim4 for debian-volatile (Was: exim4_4.50-8sarge1)
Hi, [ CC'ing debian-devel, as more people might catch it up there ] On Thursday, 02 Mar 2006, Andreas Barth wrote: > Hi, > > I propose to accept exim4_4.50-8sarge1 into volatile. This version is > already accepted into the next point release, and I would put the > binary-idential packages into volatile. so why put it into volatile if it will be included into the next stable point release? > The change fixes one problem that became more and more problematic with > the more and more widener deployment of ipv6 - if only some addresses > are in the additional section of the answer of the query for the > mx-record, only those addresses are tried. Especially, if only ipv6 > addresses are there, but no ipv4 ones, and the host doesn't have ipv6, > the mail may be delayed or even bounce. The patch just ignores these > additional sections now, and always asks for all addresses by an extra > dns query. True, this has been reported several times on the debian-devel mailing list. > I think it matches into volatile, as: > | acceptance rules > > | * volatile is not "just another place" for backports, but should > | only contain changes to stable programs that are necessary to keep > | them functional; > the new version contains exactly one changeset. This changeset is > necessary to keep exim4 operational towards hosts having ipv4 and ipv6 > records. As more and more hosts get ipv6 records, this is necessary. > (Basically like the newer postgrey daemon - no protocol changes, just > the whitelist increased as the maintainer knows now more hosts that need > to be in that list.) yeah, but the postgrey whitelist contains so called "volatile data" which i can't find in exim4. > | * It should allow any administrator to "just use" volatile, as they > | "just use" security.d.o, and they should be confident that nothing > | is broken by that; > > yes, done. As it is part of the next point release, that already needs > to be ensured. > > | * the upgrade path from volatile to the next stable release needs to > | be at least as easy as from the current stable release; means e.g. > | that the version in volatile must not be higher than in testing > > same. (I deleted some items, which are trivially also ok.) I don't see any reason accepting packages into debian-volatile, when they contain no volatile data. Also if the package will be in the next stable point-release i don't see any reason why to put it into volatile... Just to have it in an archive earlier than in the next point-release? Sorry, i don't count that as a reason. I currently disagree with that proposal, but will accpet it if a) the users want to have it into volatile and/or b) if you can convince me that it makes sense to have it in volatile. Thus i ask you folks (on debian-devel) to give more input on that. [ removed the patch, can be found in previous mail in the archives] Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Propose exim4 for debian-volatile (Was: exim4_4.50-8sarge1)
Hi Andi, On Sunday, 05 Mar 2006, you wrote: > The plan is to make s-p-u such a place, but until it happens, I think > volatile can have such packages as an exception, if the bug is severe > enough. sorry, but i disagree with you on that. For me volatile is handling packages with volatile data, not for handling packages the stable release manager denys to take into a stable release. Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Buildd howto
Hi Soumyadip, On Thursday, 27 Jan 2005, Soumyadip Modak <[EMAIL PROTECTED]> wrote: > However I couldn't find any documentation on how to setup buildds. Can > anyone please provide pointers http://www.debian.org/devel/buildd/ or http://people.debian.org/~aba/buildd/ Greetings Martin -- The human race never solves any of its problems. It merely outlives them. -- David Gerrold -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#292831: udev: udev prevents X from beeing started
Hi Marco, On Sunday, 30 Jan 2005, Marco d'Itri <[EMAIL PROTECTED]> wrote: > On Jan 30, Martin Zobel-Helas <[EMAIL PROTECTED]> wrote: > > > installing udev results in X not able to start. > RTFM README.Debian. > As written, i installed sarge via linux26, than did a apt-get install x-window-system X runs perfect. Now i did apt-get install gnome which installs udev and will result in /dev/psaux being not present after a reboot. This breaks unrelated stuff here, so please fix it. Every 0-8-15 user will do exactly the same as i did. It is your package package breaking a perfectly running X here. Greetings Martin -- Renning's Maxim: Man is the highest animal. Man does the classifying. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Accepted valknut 0.3.7-1 (i386 source)
Hi Pasi, On Saturday, 19 Mar 2005, you wrote: > Kirjoitit viestissäsi (lähetysaika lauantai, 19. maaliskuuta 2005 02:53): > > On Friday, 18 Mar 2005, you wrote: > > > Changes: > > > valknut (0.3.7-1) unstable; urgency=high > > > . > > >* New upstream release (Closes: #289643, #269952, #265284, #270096, > > > #286234) > > > > is there any reason for not giving some more explanation, when closing > > bugs with urgency=high and only listing "New upstream release" as > > only changelog entry. > > > > I would like to have some more explanation for this in the changelog. > > > hello Martin, > There really isn't any more to say. There is nothing else changed in package > than new source so I don't really know what else I could say. priority High > is since dcgui-qt is totally unusable with new libxml AND if one tries to > start dcgui-qt with new libxml it destroys ones dcqui-qt config file. But > again nothing changed in package. just recompile against new libxml would > remove those unusability issues. oh, one thing I should had said was that I > updated man page to match new name, but I forgot it because I made it when I > was working with 0.3.3. please don't take my last eMail as offence. Let me explain a little bit: i am reading debian-devel-changes, so i saw your upload. And i was a little bit irritated, when i saw "urgency=high", but the only changelog-entry was "New upstream version" with some "Closes" in it. As reader, it was not clear for me why a new upstream version justifies "urgency=high", so i had to look in the BTS. I just took a quick look and didn't find any serious or grave bugs fixed, which irritated me even more. Lets imagine we are already in freeze and your package would have been uploaded to testing-proposed-updates(t-p-u). As all packages on t-p-u will be reviewed before letting in, it is easier for the reviewer, if the changelog says something like that: valknut (0.3.7-1) unstable; urgency=high * New Upstream version - fixes random data loss (Closes: 12345), therefore urgency high - fixes foo - fixes bar The reviewer sees within the first two lines of the changelog the essential data: a) it is new upstream b) it fixes something very important, which justifies the urgency. Hope that helps and i hope i annoied you not too much. Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: More DDTP problems
Hi Martin, On Monday, 04 Apr 2005, you wrote: > [EMAIL PROTECTED] wrote: > > > > The questions below were posted at long time in the DDTP-Coors list, but > > weren't replied :((( > > > > IMHO the ddts code needs a revision to correct bugs, I am wrong? This > > revision is possible? I can help. > > It needs a thorough source code review before it can be reactivated > again. I am currently on that (started last weekend). Jeroen sent me the CVS tarball. I hoped to finished it at the weekend but it's more than expected and i did not yet understand all code. Perhaps it is also a good idea if some more people could go over the code, as many eyes see more than two eyes do. Joey, would it be okay for you if i/we think that the code is okay, i/we send you a signed mail including the md5sum of every file? Or is the md5sum of the tarball enough? Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: More DDTP problems
Hi all, On Monday, 04 Apr 2005, you wrote: > On Apr 4, 2005 4:04 PM, Martin Zobel-Helas <[EMAIL PROTECTED]> wrote: > > > I am currently on that (started last weekend). Jeroen sent me the CVS > > tarball. I hoped to finished it at the weekend but it's more than > > expected and i did not yet understand all code. > > > > Perhaps it is also a good idea if some more people could go over the > > code, as many eyes see more than two eyes do. > > We've been talking about this with other people involved and I even > asked Michael Bramer independently (hadn't seen your message). It > would be a great thing if DDTP code could be put in alioth, so that > all of us who want to make it better have access to it. > > Michael said it was ok with him. Could you start the alioth project > with the code Jeroen sent you? sorry for beeing a little bit quite last week. I was on vacation and had some personal things to do. I registered a alioth project today, which hopefully will be aprooved soon. I also CCed grisu in this mail, perhaps he can also give us some helping hands with the DDTP. So how do we want to proceed further? I think a good idea might be as soon as we have the alioth project to upload the tar.gz Jeroen send me. Then every file which has been checked for trojanisation (and is negative) could be checked in individualy into the CVS. Or should we have branch the CVS? This way we might be able to restore old CVS log messages. Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: More DDTP problems
Hi all, On Tuesday, 19 Apr 2005, I wrote: > I registered a alioth project today, which hopefully will be aprooved > soon. FYI project approoved. https://alioth.debian.org/projects/ddtp/ is our friend. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: More DDTP problems
Hi Otavio, On Tuesday, 19 Apr 2005, you wrote: > > I think is best move all there, convert to subversion, and then we oh no. It is CVS now, and we should'nt move it to something different for now. Another one might like arch more, even an otherone might like to use even another version control system. I prefer to use the method Jeroen suggested. > start to look file by file. To "Sign" a file, we can commit > another fine and then we write a small script to check against it. I set mail-follow-up to -i18n so lets discuss there further. Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: And now for something completely different... etch!
Hi, On Tuesday, 07 Jun 2005, you wrote: > Feel free to add some new items or add (hopefully new) information to the > ones I list below: > - A lot of programms use tcpwrapper which I appreciate a lot. However, it is quite often not too easy to find out what to write in hosts.allow to allow access to exactly that program. Frankly speaking, having that information always in the manpage seems a good idea to me. (i would like to see that as recommondation for packages in etch) - IPv6 Readyness packages in etch should be able to handle IPv6. There are still a bunch of packages which are not able to handle IPv6. - packages in base or packages up to priority standard must not use savelog. There is at least one package in base i know off which uses savelog to rotate logfiles. Using logrotate is a more save way, as it gives the user the possibility to configure more easyly when logfiles are rotated. I would like to see 5(j) of etch release-policy adjusted or best, to say, all packages must use logrotate. Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Orphan party
Hi Josselin, On Sun, Oct 15, 2006 at 02:56:52AM +0200, Josselin Mouette <[EMAIL PROTECTED]> wrote: > I'm orphaning the following packages. I'm no longer interested in > maintaining them unless the project pays me for it. > > * h5utils > * hdf5 - very useful tool for finding ICEs in gcc. Otherwise, > fragile library which implies working around bugs introduced by > incompetent upstream developers hiding behind a help desk for > any interaction. > * libctl > * libpng - nightmare of the security team. Upstream developers > seem to have recently understood some packaging issues, but with > their erratic behavior and stupid things libpng-using > applications do, it is likely to break at each new upstream > release. Anyone sane should consider reimplementing it from > scratch instead of packaging it. > * mpb > * sdl-mixer1.2 what about python-support? Greeetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#393411: Source package contains non-free IETF RFC/I-D's
Hi Simon, On Mon, Oct 16, 2006 at 01:48:50PM +0200, Simon Josefsson <[EMAIL PROTECTED]> wrote: > Andreas Barth <[EMAIL PROTECTED]> writes: > > > * Simon Josefsson ([EMAIL PROTECTED]) [061016 13:19]: > >> I went over many packages looking for names of likely non-free files, > >> and there may be false positives. If this is the case for your > >> package, I'm sorry for the noise. > > > > Sorry, but that is unacceptable behaviour. > > Do you have suggestions to improve the situation? Reading and understanding 7.1.1 of the Developer's Reference. There it says: | If you report more than 10 bugs on the same topic at once, it is | recommended that you send a message to debian-devel@lists.debian.org | describing your intention before submitting the report, and mentioning | the fact in the subject of your mail. Common understanding of this is, that the Subject of an E-Mail should contain the the words "Mass Bug Filing". Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian Archive Automatic Signing Key (4.0/etch)?
On Tue Nov 21, 2006 at 21:23:48 +0100, Hendrik Sattler wrote: > Hi, > > I tried to "apt-get update" from a testing mirro today but apt told me? > W: There are no public key available for the following key IDs: > A70DAF536070D3A1 > > OK, maybe a new key, let's look at debian-archive-keyring: > gpg --no-default-keyring --keyring > /usr/share/keyrings/debian-archive-keyring.gpg --list-keys > /usr/share/keyrings/debian-archive-keyring.gpg > -- > pub 1024R/1DB114E0 2004-01-15 [expired: 2005-01-27] > uid Debian Archive Automatic Signing Key (2004) > <[EMAIL PROTECTED]> > > pub 1024D/4F368D5D 2005-01-31 [expired: 2006-01-31] > uid Debian Archive Automatic Signing Key (2005) > <[EMAIL PROTECTED]> > > pub 1024D/B5F5BBED 2005-04-24 > uid Debian AMD64 Archive Key > sub 2048g/34FC6FE5 2005-04-24 > > pub 1024D/2D230C5F 2006-01-03 [expires: 2007-02-07] > uid Debian Archive Automatic Signing Key (2006) > <[EMAIL PROTECTED]> > > Hmm, maybe I missed an update? Let's take a look: > # apt-cache policy debian-archive-keyring > debian-archive-keyring: > Installed: 2006.01.18 > Candidate: 2006.01.18 > Version table: > *** 2006.01.18 0 > 500 http://ftp2.de.debian.org testing/main Packages > -10 http://ftp2.de.debian.org unstable/main Packages > 100 /var/lib/dpkg/status > > Nope, not there. How can I verify that key if the pacakge that it should be > in > is not updated in time? > > BTW: during all that time, it is still not documented, HOW EXACTLY I add a > key. And I mean the whole procedure and _command_ _line_ _examples_! The > apt-key and apt-secure manpages do not mention the FORMAT that they accept > (and how to export from gpg to make apt-key accept it from stdin). gpg --recv-keys A70DAF536070D3A1 && (gpg --export -a A70DAF536070D3A1 | apt-key add -) Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: out-of-date non-free packages
On Wed Nov 29, 2006 at 16:40:30 +0100, Stefano Zacchiroli wrote: > On Wed, Nov 29, 2006 at 04:28:24PM +0100, Andreas Barth wrote: > > If you are maintainer of a non-free-package falling into this category (i.e. > > after careful review of the license that it can be autobuild), please: > > Are you interested in having those information also for Arch: all > packages? Arch: all Packages do not get build on a buildd. This announcement is for Arch: any packages. Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[Call-for-Testing] open-iscsi from experimental
Hi, as the open-iscsi interface in kernel 2.6.18 changed we will need a newer version of open-iscsi in testing as soon as 2.6.18 hit testing. I recently NMUed open-iscsi to close two RC bugs and needed to use a new major upstream version, to get it proper working with kernel 2.6.18. I therefor uploaded my NMU to experimental to not break anything hard for now. Andreas Barth asked me now to reupload to unstable. Before i am going to do that, i would like to ask around if there are persons around, willing to also test the current version in experimental before i reupload to unstable. Changes: open-iscsi (2.0.730-0.1) experimental; urgency=low . * The "I need to NMU my own applicant" version: + NMU + New Upstream Release (Closes: #397636) + Made /var/lib/open-iscsi 0700 (Closes: #398733) + change #define INITIATOR_NAME_FILE to /etc/initiatorname.iscsi in usr/initiator.h + Fix package description (Closes: #380162) Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: x86 buildd for experimental ?
Hi, On Fri Jan 05, 2007 at 19:01:31 +0100, Mike Hommey wrote: > Hi, > > As a lot of gnome 2.16 currently in experimental has been uploaded for > amd64, there's a lot of it not built for x86 yet. > > I heard several times people claim experimental was autobuilt, but are > there any x86 autobuilder set up for experimental ? yes. For more info please contact Marc 'HE' Brockschmidt. Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Australian timezone (australasia) update for this weekend
Hi Martijn, On Friday, 24 Mar 2006, you wrote: > On 3/23/06, Aníbal Monsalve Salazar <[EMAIL PROTECTED]> wrote: > > Hello, > > > > The Australian timezone change is a couple of days away. If you are > > running servers depending on acurrate time, you will need to check > > or update them. > > Quick question: If there's an update to the stable libc due a security > issue, will it have the update or will all our machines revert back to > the wrong behaviour? yes, this might happen. Anyways, there is a new libc in the queue for Debian Sarge 3.1r2 which has a timeszone update. Thanks to Aurelien for that. Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gcc 4.1 or not
Hi Andi, On Wednesday, 10 May 2006, you wrote: > there were some requests, e.g. by Martin Michlmayr to the release team > whether we could switch gcc to 4.1 or not for etch. As we're heading to I know, tbm tried to build all packages on mips*. It would be intersting to know, how other architectures behave. Also i have not seen any comments from doko yet. Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sun Java available from non-free
Hi Michael, On Friday, 19 May 2006, you wrote: > > > As a final note, did anyone from Debian who usually examines licences > > > actually examine this one? > > > > Yes. > > I take it you were too busy to elaborate on this when you wrote this > email. So you will probably give us the name of this person later on, > right? Or even better this person may stand up now and speak > for himself and share his reasoning. i hope it is just due to the lag of bandwidth, so AJ is just trying to use as little bandwidth as possible, to leave the rest for us, watching the videostream from outside. ;) Gruss Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sun Java available from non-free
Hi AJ, On Monday, 22 May 2006, Anthony Towns wrote: > On Sun, May 21, 2006 at 06:14:51PM +0200, Michael Meskes wrote: > > On Sat, May 20, 2006 at 04:18:44PM -0500, Anthony Towns wrote: > > Right, but again, why bringing the package with a bad license into the > > archive first? > > Because non-free is for "bad" licenses in the sense that they don't meet > the DFSG, and because the Sun license is not "bad" in the sense that it > causes any problems that we cannot deal with. "Bad" as in "undistributable"? Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cgiirc Hijacking
Hi Florian, On Wed, Jun 21, 2006 at 07:34:49PM +0200, Florian Weimer <[EMAIL PROTECTED]> wrote: > * Mario Holbe: > > > We did. 0.5.4-6sarge1 was on s.d.o as soon as possible. Since there were > > no newer version in unstable, the version on s.d.o should have had > > automatically override even the unstable version. Of course, if you > > don't source in s.d.o, you don't get security updates :) > > In this case, the security update should have been propagated to > testing and unstable automatically. For a few months, dak behaved > that way. I don't know what has changed. For proposed-updates is a new queue-handling in place [1]. This means that all packages which get uploaded to security.debian.org get into this new proposed-update queue, before they get accepted into the real proposed-update queue. For dak packages in the new proposed-update queue are just as _not being uploaded at all_ before they are accepted by the stable release team members. cgiirc was a special case as version in sid and version in sarge were the same. Packages from security.d.o still get synced to ftpmaster.d.o, but into the new proposed-queue, which needs interaction by the stable release managers. We are aware of this, and it should be solved (hopefully) by the next dinstall run. Greetings Martin [1] http://lists.debian.org/debian-devel-announce/2006/06/msg7.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: buildd logs for experimental
Hi Drew, On Fri, Jul 28, 2006 at 03:28:13PM +1000, Drew Parsons <[EMAIL PROTECTED]> wrote: > As I understand it, buildds (or is it a separate set of servers?) are > now autocompiling packages in experimental. Where are the logs for > these builds? http://experimental.debian.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Release-critical Bugreport for August 19, 2005
Hi Piotr, On Friday, 19 Aug 2005, you wrote: > I don't like these reports. They should be available at the web only. Could > anybody turn off the mailing? I would like to see the > [EMAIL PROTECTED] only for really important messages. bash:# man procmail -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Release-critical Bugreport for August 19, 2005
Hi Piotr, On Friday, 19 Aug 2005, you wrote: > On Friday 19 of August 2005 17:01, Martin Zobel-Helas wrote: > > Hi Piotr, > > > > On Friday, 19 Aug 2005, you wrote: > > > I don't like these reports. They should be available at the web only. > > > Could anybody turn off the mailing? I would like to see the > > > [EMAIL PROTECTED] only for really important messages. > > > > bash:# man procmail > > The WNPP messages was dropped. The RC report are the only messages generated > automatically and flooding debian-devel-announces list. So where would you like to go it to? /dev/null ? I think having this mailing once per week is quite okay, as it gives us an overview on how many bugs are still open. As this is part of our quality assurance, and i think anyone should do a minimum of quality assurance, i would not like to get this mailing switched off. As already said, if you don't like them, use a filter like procmail to filter them away. Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Work-needing packages report for Aug 19, 2005
Hi Roberto, On Friday, 19 Aug 2005, you wrote: > On Fri, Aug 19, 2005 at 12:25:07AM -0600, [EMAIL PROTECTED] wrote: > > > > The following packages have been orphaned: > > >mindterm (#323802), orphaned today > > Description: java ssh client that can be used as a web applet > > > > > Can we just have this removed? It is ancient (the new versions are > non-free) and only implements SSH1, which is probably not a good thing > to use anyways. > Just file a bug against ftp.debian.org asking for removal. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
SSL Root Ceritficate
Hi, as nm.debian.org is now using https i would like to know, where i could find the public part of the SSL root certificate of spi-inc.org online. Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: i386 requalification for etch
Hi Nathanael, On Saturday, 08 Oct 2005, you wrote: > Anyone working on assembling the information for this? > > It ought to be a slam dunk, but I'd hate to see it not happen because > nobody bothered to collect the information. do you mean i*3*86 or ia-32? i*3*86 died already before sarge release. Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sources of dak ?
Hi, On Sun Jan 27, 2008 at 16:53:59 +0900, Charles Plessy wrote: > Dear Developpers, > > I wanted to check if dak was case-sensitive when parsing the > DM-Upload-Allowed field, but I did not find this string in the sources > that I got from `apt-get source dak'. I then checked debian/copyright, > that pointed me to http://cvs.debian.org/?cvsroot=dak, in which I did > not find anything either. Are there more recent sources available to > non-DDs? http://ftp-master.debian.org/bzr/ -- Martin Zobel-Helas <[EMAIL PROTECTED]> | Debian Release Team Member Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mass ITPs
Hi, On Fri Feb 29, 2008 at 21:59:58 +0900, Paul Wise wrote: > Hi Rafael, all, > > Perhaps in future mass ITPs could be mostly filed with only one to > [EMAIL PROTECTED] and the rest to [EMAIL PROTECTED] instead? And/or creating a new mailing list, debian-itp, debian-devel-itp or whatever might be a good idea. Quite a big number of mails to the debian-devel mailing list are ITPs. Greetings Martin -- Martin Zobel-Helas <[EMAIL PROTECTED]> | Debian Release Team Member Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Steffen Joeris (white@) is wanted ;)
Hi, On Wed Mar 12, 2008 at 11:39:10 +0300, Dmitry E. Oboukhov wrote: > Does anybody know where Steffen Joeris is? > > He has not answered my mails for a month+ already. > Is everything OK with him? IIRC: Broken laptop and no Internet connection somewhere in .au. Last time a had active smoke signs from him was IIRC around XMAS, though i could contact his parents if needed. Greetings Martin -- Martin Zobel-Helas <[EMAIL PROTECTED]> | Debian Release Team Member Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bits from the armel porters
Hi, On Fri Mar 07, 2008 at 12:31:23 +0100, Marc 'HE' Brockschmidt wrote: > Riku Voipio <[EMAIL PROTECTED]> writes: > > For the second point, armel must keep up-to-date and must not have > > build failures affecting armel. The current buildds are struggling to > > keep upto date, so 4 new Thecus machines have now been ordered to be set > > up as normal/testing/security buildds and porter machines in the near > > future. > > The machines have now arrived. After the fitting disks and memory > modules have been delivered, these boxes will get installed and shipped > to their final hosting locations. This should take about one or two > weeks. After that, DSA can do the debian.org setup and leave them to the > buildd admins. Debian Developer accessible machine in place now. For details see: http://lists.debian.org/debian-infrastructure-announce/2008/03/msg3.html Greetings Martin -- Martin Zobel-Helas <[EMAIL PROTECTED]> | Debian Release Team Member Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rejected: epcr_2.3.9-1.dsc: sha1 check failed
Hi, On Thu Apr 17, 2008 at 10:38:38 +0200, Raphael Hertzog wrote: > On Thu, 17 Apr 2008, Adam D. Barratt wrote: > >> Will the devscripts in stable be updated to handle this? If so, when? > >> If not, why not? > > > > (If you're looking for an answer from the maintainers of a package it's > > probably safer to ask them directly rather than assuming they read every > > post on debian-devel; admittedly several of us do, but... :-) > > > > I'm not convinced it meets the SRM team's criteria for a stable update, > > as laid out in http://release.debian.org/stable/4.0/4.0r3/ et al. > > It doesn't hurt to ask however. Ubuntu is also rushing a last-minute > update in hardy to avoid this problem. I don't see anything which warrants a stable upload here. Greetings Martin -- Martin Zobel-Helas <[EMAIL PROTECTED]> | Debian Release Team Member Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Should we improve our (internal) communication?
Hi, On Thu Jul 16, 2009 at 20:16:06 +0100, Ben Hutchings wrote: > On Thu, 2009-07-16 at 20:25 +0200, Sandro Tosi wrote: > > Hi all, > > today ries (aka ftp-master) was down due to a scheduled maintenance > > activity. > > > > Now, scheduled means programmed, and suddenly this question comes to > > me: should the project be notified of such core activities? should we > > only relay on #debian-devel irc channel topic to know this? > [...] > > This is what debian-infrastructure-announce is for (though > debian-devel-announce might be appropriate in some cases). But there > was no announcement in this case. There was minimal time between the announcement DSA got and the shutdown. I added "scheduled" to the topic of #debian-devel to indicated it didn't broke randomly but was cleanly shut down by DSA. My fault for not sending a mail to d-i-a, sorry for that. If we would had got a more timely announcement from the hoster, i would had surely send a mail to d-i-a. If you think we (DSA) are doing a bad job, please feel free to attand DSA BoF on DC9 and lets talk about it there. Greetings Martin -- Martin Zobel-Helas | Debian System Administrator Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Should we improve our (internal) communication?
Hi, On Thu Jul 16, 2009 at 15:22:44 -0500, John Goerzen wrote: > Martin Zobel-Helas wrote: > > If you think we (DSA) are doing a bad job, please feel free to attand > > DSA BoF on DC9 and lets talk about it there. > > That implies to me that this is the only way to discuss the issue. Is > that what you meant to imply? > > I hope not; there are many people that can contribute to this project > that can't necessarily make it to DebConf. I didn't wanted to imply that the only way to discuss issues like this is at DebConf. I just learned that discussing stuff from face-to-face is sometimes much more easy. Greetings Martin -- Martin Zobel-Helas | Debian System Administrator Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Should we improve our (internal) communication?
Hi, On Fri Jul 17, 2009 at 12:51:34 +0200, Sandro Tosi wrote: > On Fri, Jul 17, 2009 at 12:32, Joerg Jaspert wrote: > > > >>> http://lists.debian.org/debian-devel-announce/2008/09/msg6.html > >> Thanks for the pointer, but I'm referring to > >>> the upload queue, is pointed elsewhere during that time, > >> not to the general reorganization of upload queues announced with that > >> email. > > > > It is *exactly* the point of host-independent names for the upload queue > > to NOT announce when they point to a different host. So do not expect > > such an announcement, ever (except for when the ssh queue moves, due to > > changed hostkey behind it). > > Fine, but it doesn't change that much the point of the original > message: the proposal/encourage to use d-i-a for infra operations, and > not #-devel topic. we understood that now. EOD, PLEASE! I also already appologized for it. Martin -- Martin Zobel-Helas | Debian System Administrator Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Archive signing key for 2007?
Hi, On Fri Jan 19, 2007 at 13:01:45 +0100, Goswin von Brederlow wrote: > Anthony Towns writes: > > > On Thu, Jan 11, 2007 at 11:51:21PM +0100, Javier Fern?ndez-Sanguino Pe?a > > wrote: > >> I thought that the 2007 key was (based on [1]) supposed to be available > >> early in January and available in the debian-archive-keyring package. Which > >> doesn't seem to be the case. > > > > The key we'll be using (and indeed are already using) is available as: > > > > http://ftp-master.debian.org/archive-key-4.0.asc > > > > It's expected to be valid until sometime after lenny is released. > > > > If you've upgraded a testing/unstable system in the past month or two, > > you'll find that key has been automatically added to your apt key list, > > after being verified by the normal trust path for upgraded packages -- > > namely the current archive key you've been using, then the sha1sum of > > the Packages file and finally the md5sum of the apt package containing > > the updated key. > > > > Debian developers can obtain the key from merkel over ssh, by looking > > in /srv/ftp.debian.org/web/archive-key-4.0.asc. The key id is 6070D3A1 > > which can be obtained from the key servers with signatures from both me > > and Steve Langasek. > > > > Cheers, > > aj > > Does that mean etch will not be signed by an offline key? Was stable > ever signed with an offline key? > > I think signing stable with an online key without passphrase is a > serious loss/lack of trustiness in it. It means that if the archive > gets compromised then stable package can be replaced without apt > noticing. Stable will be signed by both, online and offline key. Also every point release will be signed by both keys. Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Archive signing key for 2007?
Hi, On Sat Jan 20, 2007 at 13:51:49 +0100, Goswin von Brederlow wrote: > Martin Zobel-Helas <[EMAIL PROTECTED]> writes: > > > Stable will be signed by both, online and offline key. Also every point > > release will be signed by both keys. > > > > Greetings > > Martin > > Ok, then where is the "Debian Archive offline Signing Key (4.0/etch) > <[EMAIL PROTECTED]>"? > > Isn't is high time to create it and add it do the debian-archive-keyring? It is allready created, Andi is working on it's integration into debian-archive-keyring. Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: x86 buildd for experimental ?
Hi, On Tue Jan 23, 2007 at 20:51:27 +0100, Mike Hommey wrote: > On Tue, Jan 09, 2007 at 01:12:09AM +0100, Marc 'HE' Brockschmidt <[EMAIL > PROTECTED]> wrote: > > Mike Hommey <[EMAIL PROTECTED]> writes: > > > As a lot of gnome 2.16 currently in experimental has been uploaded for > > > amd64, there's a lot of it not built for x86 yet. > > > > > > I heard several times people claim experimental was autobuilt, but are > > > there any x86 autobuilder set up for experimental ? > > > > There was no i386 autobuilder in the last few weeks. This has changed > > now, Joerg Jaspert provided a Xen instance on one of his servers, which > > I set up as buildd tonight and is now happily building packages. The > > first few experimental gnome packages are already uploaded, rest should > > follow in the next few days. > > (More than a few days later, it seems like still nothing is > happening...) i can see a couple of logs signed by Marc, so what do you complain about exactly? Marc is working on all packages from experimental, though it might take a while to build all packages in the right order do get all packages (like gnome 2.10) compiled in the right order. Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: update on binary upload restrictions
Hi, On Thu Jan 25, 2007 at 01:23:35 +, James Troup wrote: > Hi, > > Summary > === > > I've done some work in dak to improve the binary upload restrictions > that are currently in place to hopefully reduce some of the collateral > damage that resulted from the initial implementation. Binary upload > restrictions are now per-suite/component/architecture which means that > uploads to experimental and/or non-free should no longer be affected. > The current restrictions are listed below[1] for reference. Thanks for doing so, this way we can build experimental and non-free again. Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Timezone update for sarge
Hi, On Thu Feb 08, 2007 at 07:15:06 +0100, Aurelien Jarno wrote: > The problem is fixed in sarge-proposed-update with glibc version > 2.3.2.ds1-22sarge5 since the end of November. > I would like to know if the stable release team is planning to do > something to update the glibc in Sarge. Yes. -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Handling of (inactive) Debian Accounts
Hi, On Sat Feb 10, 2007 at 11:57:14 +0100, Pierre Habouzit wrote: > On Sat, Feb 10, 2007 at 02:34:39AM +0100, Joerg Jaspert wrote: > > Hi > > > > as Debian gets more and more accounts it is only natural that we have > > more and more unused accounts. People get MIA, find different interests > > or simply lost interest in Debian but did not follow the normal > > procedure of retiring.[1] > > I wholeheartedly welcome that decision ! > > > To get into the Emeritus state you voluntarily retire from the project, > > following [1] or by replying to a WaT mail. > > > > [...] > > > > People in this stage can get their DD status back with a reduced NM > > process. > > What is a "reduced" NM process exactly ? Is that just a matter of > saying "hey I'm kicking and alive" ? Will the account reactivation > immediate ? Or would it suffer from the same delays as NM ? > > I mean, I'm sure many DD's fear the Emeritus state because they just > fear the length and complexity of getting their account back. IIRC they do not need to answer any question like a NM needs to do, but rather a very selected count of questions like eg. "What is frozen" and so on. There might be a coule of things that changed since they retired from the project. Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#411591: RFA: devscripts -- Scripts to make the life of a Debian Package maintainer easier
Hi, > > I request an adopter for the devscripts package. I have had very > little time over recent months (years, even), and this package really > demands far more active maintenance than I am able to give it. I would be willing to addopt that package, but team maintainance would be very much appreciated. As i side note: i spoke to Christoph Berg (myon), and he would also be willing to help. Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ITA/RFS: libspf2 -- Sender Policy Framework library, written in C
Hi, I am a bit irritated by the following sentence in README.Debian-source: | It's completely out of date anyway. Could you please explain? Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alerts for uploads to stable-proposed-updates and tpu
Hi, On Sun Apr 01, 2007 at 11:37:06 +0200, Florian Weimer wrote: > * Andreas Barth: > > > For t-p-u, [EMAIL PROTECTED] > > Ah, thanks. Pretty obvious in retrospect. > > > For proposed-updates, I fear the mails are only sent upon approval, > > but I'm not sure (it would be debian-changes@lists.debian.org). Packages approved by SRM are currently not producing a mail to [EMAIL PROTECTED], but i am currently working on a fix for that. Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: merkel.debian.org down?
Hi, On Sat Apr 07, 2007 at 17:29:48 -0400, Bryan Donlan wrote: > Hi, > > Is there any news on the merkel.debian.org downtime? This also stalls > apt-listbugs for a while on every package upgrade attempt. I tried > searching the list archives for d-d and d-d-a, but saw nothing about > it. Yes, merkel down til tomorrow evening. -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: spam from bugs.debian.org
Hi, On Wed Apr 25, 2007 at 01:08:32 -0700, Don Armstrong wrote: > On Wed, 25 Apr 2007, Kamaraju S Kusumanchi wrote: > > Of late, I have been seeing a lot of spam from bugs.debian.org . I never got > > this many spam emails from BTS. Has something changed? > > Not really; it's just the continuing battle between spammers and Blars > (and to a lesser extent, the rest of us with owner@ hats). Rules are > put in place to block spam that gets through. [Just to give you an > idea of how much spam we do block; every day the BTS discards around > 4G of non-duplicate spam; I've no idea how much in total we ditch.] > > > How does everyone deal with this (I mean other than filtering)? > > If anyone is doing a substantially better job of filtering than the > bts is, let [EMAIL PROTECTED] know; but in general you should just > see the few spammers who end up being successful. Same for lists.debian.org. Just to give an impression from yesterdays statistics: 94108 delivery attempts (incoming) 51598 messages received (in total) rest blocked by whatever RBL 10426 messages feed to spam search software rest already cought by static filtering 1523 messages tagged as "no spam" === ~1% of delivery attempts (incoming) is still send out to the lists If we now say, that out of these 1523 mails, ~150 mails are still spam, this makes a 0.1% rate of spam that is still deleivired to the lists. I belive that a rate of 0.1% is quite an acceptable rate, but we permanently try to lower that. Perhaps we should really propose a "Day of No Spam-Filtering" on lists.d.o. ;-) Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Building packages twice in a row
Hi, as a QA effort the whole archive was rebuilt yesterday to catch build-failures, whether a package can be build twice in a row (unpack, build, clean, build). We found about 400 packages not having a sane clean target. To cite http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules clean This must undo any effects that the build and binary targets may have had, except that it should leave alone any output files created in the parent directory by a run of a binary target. We started filing bugs to each effected package with severity important, those can be found at http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED];tag=qa-doublebuild Building twice is not yet a requirement, but will (hopefully) become release goal for Lenny. Greetings Martin signature.asc Description: Digital signature
Re: Building packages twice in a row
Hi, On Wed May 16, 2007 at 10:11:55 +0200, Stefano Zacchiroli wrote: > On Wed, May 16, 2007 at 08:10:44AM +0200, Martin Zobel-Helas wrote: > > as a QA effort the whole archive was rebuilt yesterday to catch > > build-failures, whether a package can be build twice in a row (unpack, > > build, clean, build). We found about 400 packages not having a sane > > clean target. > > Wow, thanks for the effort! > > > To cite > > http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules > > > > clean > > > > This must undo any effects that the build and binary targets may > > have had, except that it should leave alone any output files created > > in the parent directory by a run of a binary target. > > Isn't "twice building" too coarse grained to spot actual violation of > this rule? I mean, packages that fail to build the second time have for > sure garbage left around after the former invocation of "clean". But it > is not granted that packages with garbage left around will fail to > build. ack. > Wouldn't it be better to unpack a package twice in two different > directories, build and clean in one dir and then compare the obtained > tree with the tree available in the other dir? That would surely be the better solution to catch this policy violation. But the way we did it now was the fastest and easiest solution for now, and showed already how many packages have no correct working clean targets. We will need to patch sbuild for the changes you suggested. Feel free to send patches for that. > I know, that's cheap talk while you actually provided facts :-), just > take this as a curiosity of mine / suggestion for future tests. If you provide a patch for sbuild, Lucas will surely hand you the build-logs for all packages. Happy bug filing then. > Many thanks again for this! nP. QA is work everyone of the project can do. Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Filing FTBFS bugs and packages in NEW
Hi, On Fri Jun 01, 2007 at 12:59:14 +0300, Kari Pahula wrote: > I'd like to file a wishlist bug on people who file FTBFS bugs. > > It would be nice if you checked first whether there's a package > pending in NEW or incoming and see if that might resolve the issue > already. This could be realized by patching helena[1], eg. to produce a RSS like output, so an automated parsing of PackageName and PackageVersion in NEW could be done. I will have a look into that during the weekend. Should be mostly trivial. Greetings Martin [1] helena (or better, her successor) produces http://ftp-master.debian.org/new.html -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Filing FTBFS bugs and packages in NEW
Hi, On Sat Jun 02, 2007 at 11:18:00 +0200, Joerg Jaspert wrote: > On 11037 March 1977, Martin Zobel-Helas wrote: > > > This could be realized by patching helena[1], eg. to produce a RSS like > > output, so an automated parsing of PackageName and PackageVersion in NEW > > could be done. I will have a look into that during the weekend. Should > > be mostly trivial. > > There are already RSS feeds for NEW. where? it is not linked from new.html -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFH: arm machines needed for experimental buildd network
Hi, for the current experimental buildd network we have a need of arm machines. The current machine we have is maintained by Kenshi Muto and works perfect, but we currently try to set up some redundancy on machines running for our network. So if you have a machine which meets the follwing criteria, please contact either me or Marc Brockschmidt: ARM with at least 64MB Ram 20 GB HDD, better 40-60. 24/7 Network connectivity static IP (v6 also okay) Greetings Martin signature.asc Description: Digital signature
Re: Authentication with LP for DD's using gnupg
Hi, On Fri Aug 01, 2008 at 10:42:52 +0100, Neil Williams wrote: > > On Sun, Jul 27, 2008 at 03:58:57PM +0100, Neil Williams wrote: > > > > > * Reinhard Tartler [Wed, Jul 23 2008, 04:36:39PM]: > > > > > > >> > How about activating it the first time they send a gpg-signed > > mail to > > > > >> > the mail interface? > > > > > How about simply allowing any DD to send gpg-signed email to add > > ^^ > > > > That requires LP to know who is or isn't a DD. Currently it has no it does or at least it may. rsync keyring.debian.org::keyrings/keyrings/debian-keyring.gpg can be synced publicly -- Martin Zobel-Helas <[EMAIL PROTECTED]> | Debian Release Team Member Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: transfering files between *.debian.org hosts
Hi, On Sat Aug 30, 2008 at 18:17:27 -0700, Russ Allbery wrote: > A bigger problem at the kernel level is that the kernel APIs change > constantly and have not infrequently had various GPL-only tags added that > force OpenAFS into annoying workarounds (it is released under the IBM > Public License, another DFSG-free license that isn't quite > GPL-compatible). However, for systems that run stable, the corresponding > stable release of OpenAFS should continue to work fine. This mostly is a > problem if one runs a backported kernel, in which case you'll need a > backported OpenAFS as well. > > I'd certainly be happy to answer questions and help with AFS setup as I > have time. I'd love to have a Debian OpenAFS cell. Most Debian Machines run no stable kernels, thus we would run into that problem. Also many machines running with static kernels. Would that be a problem for OpenAFS? -- Martin Zobel-Helas <[EMAIL PROTECTED]> | Debian Release Team Member Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Backports now appearing on debian.org package listings?
Hi, On Sun Sep 02, 2007 at 17:46:56 -0400, Tim Hull wrote: > Does this mean anything with regards to how backports will operate? I'm > just curious, as you probably know from my past posts that I'm quite > interested in stable release updates beyond simple security updates... As member of the Stable release team i can tell you we are still working on stable release updates. 3.1r7 and 4.0r2 are in the queue, and will be hopefully published soon. Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: packages.debian.org updated
Hi, On Tue Sep 04, 2007 at 12:54:41 +0200, Frank Lichtenheld wrote: > On Tue, Sep 04, 2007 at 07:34:34AM +0200, Lionel Elie Mamane wrote: > > (Please CC me on replies; thanks.) > > > > On Sun, Sep 02, 2007 at 10:58:12PM +0200, Frank Lichtenheld wrote: > > > > > packages.debian.org was finally updated to the new code base that > > > was already available some time from packages.debian.net. > > > > What are "similar packages"? I'm trying wrap my head around the fact > > it finds x-window-system-core similar to exim4, but not vice-versa. > > Similar packages are found by using the Description and the Debtags > information of the package, doing a full text search with that and > return the best hits. I have no real idea why x-window-system-core > is considered a good hit for exim4 (But I guess it might have something > to do with the fact that the exim4 Description doesn't talk much about > what the package does and that it doesn't have any Debtags information). > > The Debtags information is very influential in this search > (for reasons I'm too lazy to explain right now), so in this case where > one package has it and the other one not, the lists can look very different. There was some idea from Enrico and me earlier this year (i think it was around FOSDEM) where he showed me how to use Debtags, Popcon and and a small ruby(?) skript and produce a very nice output from it: "People who installed X also have packages Y, Z and T installed" Any ideas how and if that can be integrated into p.d.o? Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: US mirror troubles
Hi, On Wed Sep 05, 2007 at 20:41:51 -0500, John Goerzen wrote: > Hi, > > 35.9.37.225, in http.us.debian.org, and ftp.us.debian.org, has been > unreachable on port 80 from all the networks I have access to for days. > > This is ftp.egr.msu.edu. created as RT#171 -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: X-Virus-Scanned: at lists.debian.org with p-bank en-ht
Hi, On Sun Sep 09, 2007 at 22:41:16 +0200, Elimar Riesebieter wrote: > > Hi all, > > since today I noticed the above mail header. Could one enlight me > what p-bank is? I can't find something similar in the pkg databse. p-bank means policy bank. that can also be found in the debian package. en-ht means "english, high traffic". That helps us for setting per list policies in the spamfilter. We grouped together several debian mailing lists. All of group en-ht should now have the same settings in SA and amavis. > All mails I receive coming from lists.debian.org do have this > header. Yes, and this will stay this way. Greetings Martin, having a hat on, guess which. -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: X-Virus-Scanned: at lists.debian.org with p-bank en-ht
Hi,
On Sun Sep 09, 2007 at 23:09:38 +0200, Elimar Riesebieter wrote:
> On Sun, 09 Sep 2007 the mental interface of
> Martin Zobel-Helas told:
>
> [...]
> > p-bank means policy bank. that can also be found in the debian package.
>
> In which one?
amavisd-new.
The following is taken from the amavisd example conf file:
# $policy_bank{'ALT'} = {
# log_level => 3,
# syslog_ident => 'alt-amavis',
# syslog_facility => 'LOCAL3',
# inet_acl => [qw( 10.0.1.14 )],
# final_spam_destiny => D_PASS, final_bad_header_destiny => D_PASS,
# forward_method => 'smtp:*:*',
# notify_method => 'smtp:[127.0.0.1]:10025',
# virus_admin_maps => "[EMAIL PROTECTED]",
# spam_lovers_maps => [EMAIL PROTECTED], [qw( [EMAIL PROTECTED] )]],
# spam_tag_level_maps => 2.1,
# spam_tag2_level_maps => 6.32,
# spam_kill_level_maps => 6.72,
# spam_dsn_cutoff_level_maps => 8,
# defang_spam => 1,
# local_client_bind_address => '10.11.12.13',
# localhost_name => 'amavis.example.com',
# smtpd_greeting_banner =>
# '${helo-name} ${protocol} ${product} ${version-id}
# (${version-date}) TEST service ready';
# auth_mech_avail => [qw(PLAIN LOGIN)],
# auth_required_inp => 1,
# auth_required_out => 1,
# amavis_auth_user => 'amavisd', amavis_auth_pass = 'tOpsecretX',
# av_scanners => [ # provide only 'free' scanners
# ['ClamAV-clamd',
# \&ask_daemon, ["CONTSCAN {}\n", "/var/run/clamav/clamd"],
# qr/\bOK$/, qr/\bFOUND$/,
# qr/^.*?: (?!Infected Archive)(.*) FOUND$/,
# ],
# ],
# av_scanners_backup => [
# ['ClamAV-clamscan', 'clamscan',
# "--stdout --disable-summary -r --tempdir=$TEMPBASE {}", [0],
# [1],
# qr/^.*?: (?!Infected Archive)(.*) FOUND$/,
# ],
# ],
# };
> > en-ht means "english, high traffic". That helps us for setting per list
> > policies in the spamfilter. We grouped together several debian mailing
> > lists. All of group en-ht should now have the same settings in SA and
> > amavis.
>
> Sounds reasonable ;) But should be announced to ldo subsribers?
as soon as we have the 'bits from listmaster' ready not having
"DRAFT, FIXME" in front of each paragraph. We worked quite hard this
weekend, with nearly no sleep at all, give us some time to rest before
do the announcement.
> > > All mails I receive coming from lists.debian.org do have this
> > > header.
> >
> > Yes, and this will stay this way.
>
> OK
>
> > Greetings
> > Martin, having a hat on, guess which.
>
> A red one?
no, a listmaster one.
--
[EMAIL PROTECTED] /root]# man real-life
No manual entry for real-life
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian's Linux kernel continues to regress on freedom
Hi, On Wed Sep 12, 2007 at 14:39:09 +0200, Joerg Jaspert wrote: > > Non-free material is being included in main for the benefit of *precisely > > zero* > > users. There's no two ways about this: this is a Social Contract violation. > > Oh well, the kernel team just lost its trust, which means new uploads of > kernel-team packages dont get their old way of fasttracking in NEW, as I > now need to check all of their uploads for such cases. > > Thank you, "kernel-team", for that useless amount of extra work. :( *applause* Very well done, "kernel team". That will slow down the release process quite a bit. Greetings Martin, who still waits for a fix for the sparc kernel[1] [1] #433187 that is. -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
Hi Piotr, On Tue Sep 25, 2007 at 14:10:58 +0200, Piotr Roszatycki wrote: > The Debian volatile archive is the place for packages that expires > before new Debian release. The description perfectly fits for my > package libdatetime-timezone-perl. > > I prepared a few weeks ago new releases for sarge and etch. The > release is based on old packages which have refreshed just timezone > data, based on Olson Database. The API is not change so it fits to > Debian's philosophy of backporting changes to prevent breaking > compability. > > I uploaded them a week ago and... nothing. > how about answering to my mail[1]? Greetings Martin [1] http://lists.debian.org/debian-volatile/2007/09/msg5.html [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
Hi, On Tue Sep 25, 2007 at 14:55:47 +0200, Piotr Roszatycki wrote: > Ah... Do you mean this mail? > > > am I missing something completely here? > > > > [EMAIL PROTECTED]:~/debian/packages$ diff -rNu > > libdatetime-timezone-perl-0.42-before-dv/ > libdatetime-timezone-perl-0.42 > > | diffstat > > changelog|9 > > control |4 > > packages |2 > > patches/001-AKST9AKDT_timezone.patch | 11 > > patches/010-tzdata2007g.patch|38814 > > +++ > > patches/012-tzdata2007g-tests.patch | 21 > > patches/020-AKST9AKDT_timezone.patch | 11 > > rules|4 > > update-tzdata.sh | 30 > > 9 files changed, 38890 insertions(+), 16 deletions(-) > > What is your question exactly? Do you mean, the patch is too large or > what? Can you clarify, what do you really want to ask? > > The package is perfectly correct and the only difference is updated > timezone database plus the shell script debian/update-tzdata.sh which > I used for updating plus updated test units for new database. I don't understand why there is a patch of 38k lines needed to fix ONE SINGE timezone. Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
Hi, On Tue Sep 25, 2007 at 17:36:03 +0200, Piotr Roszatycki wrote: > It is simple analogy for tzdata package. You should also ask, why the > tzdata package has so many changes and why don't simply update only > one timezone? [EMAIL PROTECTED]:~% diff -rNu tzdata-2007b tzdata-2007f | diffstat africa | 16 asia | 56 +--- australasia| 24 +-- debian/changelog |9 ++ europe | 62 ++ leapseconds| 16 ++-- northamerica | 177 ++--- southamerica | 17 +++-- zone.tab | 10 +- 9 files changed, 289 insertions(+), 98 deletions(-) So where are 38k lines here, which changed? In general i have no problem to accept a package into volatile, if one can give me GOOD reasons, why all these changes are necessary. What i do not understand is, why tzdata has about 300 lines changed, while your package needs 38k lines changed to achive the same effect. Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
Hi, On Wed Sep 26, 2007 at 00:20:10 +0200, Piotr Roszatycki wrote: > You made a subtle mistake. You checked the source package for tzdata > and the changes are really small. Then you checked the differences for > libdatetime-timezone-perl package, but this source package is already > compiled. You should check the difference between binary packages for > tzdata. > > The real source data for DateTime::TimeZone is the same as for tzdata > source package. Then, the data is precompiled into Perl source. It > makes a Debian source package. Accepted now. For the future: i would have been much easier, if you would have said: be warned, the patch is huge, but if you don't look at the compiled version of it, it is these number of lines... Both of us would have had much less trouble. Greetings Martin PS: It might take me a day or so to prepare a VUA, unless someone drafts one for me. -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
Hi, On Wed Sep 26, 2007 at 14:46:16 +0200, Piotr Roszatycki wrote: > 2007/9/26, Martin Zobel-Helas <[EMAIL PROTECTED]>: > > Accepted now. > > Thank you very much. > > > For the future: i would have been much easier, if you would have said: > > be warned, the patch is huge, but if you don't look at the compiled > > version of it, it is these number of lines... > > > > Both of us would have had much less trouble. > > I think we could communicate better if you read the patch, not just > statistics about it. By the way, the patch itself does not contain the > real source data - the Olson database. I understand that it might be will that cause dfsg problems? > not clear for someone who didn't use this library and know nothing > about complexity of timezones support in computing systems. It is > really hard piece of technology. -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: seeking: Ian Jackson
Hi, On Tue Oct 09, 2007 at 19:36:49 +0100, martin f krafft wrote: > [EMAIL PROTECTED] expands to a greenend.org.uk address, and the mx for that > domain refuses to accept my mail. > > : host > mx-relay.chiark.greenend.org.uk[212.13.197.229] said: 550 > invalid MAIL-FROM: Error during DNS MX lookup for > lapse.madduck.net: DNS alias found where canonical name wanted > [Irritated] (in reply to RCPT TO command) > > Yes, lapse.madduck.net is a CNAME (*c*anonical *name*) to an MX RR, > and that's RFC-compliant ttbomk. If it is not, I would appreciate if > someone shoved the relevant sections into my face. > > In the mean time, I'd be grateful if Ian gave me a means to > communicate with him. Or if someone would offer to relay a message > to him. > > The spammers have long won if people put such boulders in the way of > communication. Oh wait, I doubt spammers use CNAMEs... how about sending mails from master.debian.org with either [EMAIL PROTECTED] or [EMAIL PROTECTED] :) Greetings Martin PS: i know, that solution is too simple... :) -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: parsing/using *.dsc *.changes, *.deb etc., from Python
Hi, On Mon Oct 29, 2007 at 01:18:27 +0100, Ondrej Certik wrote: > Hi, > > when writing scripts to manage Debian repository, many people > including me use Python. Is there some "official" way of doing it? It > seems to me everyone is writing his own parsers. I know about of at > least 5 different projects doing it: See if http://ftp-master.debian.org/bzr/debian-archive-kit/ helps you. Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#448879: ITP: isns -- iSNS Internet Storage Naming Service
Package: wnpp Severity: wishlist Owner: "Martin Zobel-Helas" <[EMAIL PROTECTED]> * Package name: isns Version : 2.1-01 Upstream Author : Nishan Systems, Inc * URL : http://sourceforge.net/projects/linuxisns * License : BSD Programming Lang: C Description : iSNS Internet Storage Naming Service The internet storage name service (iSNS) is used to register iSCSI and iFCP storage devices in the network. The iSNS allows dynamic discovery of available storage targets by storage initiators. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[proposal] Documenting which revision is installed
Hi, i would like to propose that we change /etc/debian_version with beginning of lenny to also show which revision of a release is installed. Rational: We do regular updates to stable releases (called point releases) from time to time but you can't tell from installed files which revision (point release) is installed on a machine without knowing the exact versions of packages in a debian revision. The only way to determine which revision might be in use is to parse /var/lib/apt/lists/$mirror_$path_dists_$release_Release which sucks. My idea would be to have /etc/debian_version updated with every point release to reflect the current revision. There are different opinions out there (i spoke to several DDs already) on how to reflect this in /etc/debian_version, thus i would like to get consensus on this list first, before we start implementing it. Here comes some ideas: Lets say we have major version 4.0 (etch) and point release 2: Idea 1: 4.0.2 Idea 2: 4.0r2 Idea 3: 4.0 r2 I personaly prefere Idea 1 over 3 over 2, but as said, i want to have an consensus and i already heard several other ideas and/or complains. Please flame^Wdiscuss now i threw the fish into the ring. Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bug #561324: asking questions in postinst
Hi, On Tue Dec 29, 2009 at 15:13:54 +0100, Patrick Schoenfeld wrote: > Hi, > > On Tue, Dec 29, 2009 at 02:38:46PM +0100, Lionel Elie Mamane wrote: > > On Mon, Dec 28, 2009 at 07:44:56PM +0100, Reinier Haasjes wrote: > > > > >> Why? Is it really required to have _all_ questions in the postinst? > > > > > No, not all. There are 4 questions asked. > > > 1) brokers list, the list is received by the package-binary and the user > > > selects te broker he wants to use. For this I can use a dns-query (type > > > TXT) but dig and host are both not essential packages, so this still has > > > to go to the postinst. > > > > Well, this could be solved by a pre-depends on dnsutils | > > bind9-host. Pre-depends are often frowned upon, what do others think > > of this for this case? > > I've discussed this issue here with Martin Zobel-Helas and > he and I agree that in this limited case it could be a good solution: > > - It solves the problem in question (without a code duplication) > - A pre-depend loop is highely unlikely. After all we should slap > anybody pre-depending on aiccu very hard. > - A Pre-Depend on utilities that are likely to be installed anyway > seems like a not so great risk to avoid it. Nevertheless there should be an extra thread on debian-de...@l.d.o that announces the intend to add a Pre-Depends for this package. Martin -- Martin Zobel-Helas | Debian System Administrator Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: GPL-licensed software linked against libssl on buildds!
Hi Neil, On Tue Jan 19, 2010 at 22:29:25 +, Neil McGovern wrote: > On Tue, Jan 19, 2010 at 11:59:35AM -0800, Russ Allbery wrote: > > This is a bug in the netatalk Debian packaging. You cannot assume the > > package will be built in a clean chroot; among other things, the buildd > > software explicitly does not guarantee that all packages will be removed. > > > > Would it be time to start looking at LVM snapshops + sbuild perhaps? we already have two or three buildds doing that... The buildd team (esp. HE) working on that and if it works out to be stable enough, we can see if we can roll out it to all buildds. Greetings Martin -- Martin Zobel-Helas | Debian System Administrator Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Misc developer news (#21)
Hi, On Fri Feb 19, 2010 at 18:51:11 +0100, Raphael Hertzog wrote: > On Fri, 19 Feb 2010, Marc Haber wrote: > > On Fri, Feb 19, 2010 at 12:08:16PM +0100, Raphael Hertzog wrote: > > > * More than 1000 source packages[4] are already using the new source > > > formats "3.0 (quilt)" and "3.0 (native)". Have you updated your own > > > packages already? > > > > Why should I? > > http://wiki.debian.org/Projects/DebSrc3.0#WhyshouldIconvertmypackageto3.0.28quilt.29format.3F This wiki page still misses a "Disadvantages of new format" section. Greetings Martin -- Martin Zobel-Helas | Debian System Administrator Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100220112658.ga23...@ftbfs.de
Re: Bits from the Release Team: What should go into squeeze?
Hi, On Sun Mar 14, 2010 at 21:57:49 +0100, Mikael Djurfeldt wrote: > On Sun, Mar 14, 2010 at 21:42, Philipp Kern wrote: > > From a current point of view squeeze will release with kernel 2.6.32 > > Would it be possible to, instead, release with kernel 2.6.33? > > I see at least two improvements from 2.6.32 to 2.6.33 that will matter > a lot to certain subsets of users: > > * The TRIM command has been included in the block layer, allowing > efficient long-term use of SSD drives. > > * EDAC on the amd64 platform has had many fixes, allowing monitoring > and control of EEC ram. Pre-2.6.33 kernels don't support EDAC at all > on many common systems. * MIPS subarch octeon got added. ... There are always good points to go for newer kernels. On the other hand, 2.6.32 will get long-term support and most other distributions will also ship 2.6.32 kernels, which makes eg. security support much easier. Greetings Martin PS: My personal opinion? I would really like to see octeon support for Debian Squeeze... ;-) -- Martin Zobel-Helas | Debian System Administrator Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100314215125.gi23...@ftbfs.de
Re: Hardware trouble ries.debian.org - ftpmaster.debian.org / release.d.o services disabled
Hi, On Fri Mar 26, 2010 at 17:18:14 +0100, Alexander Reichle-Schmehl wrote: > Hi! > > Joerg Jaspert schrieb: > >> just a short notice for everyone out there who wants to upload or waits >> for a package migration to testing: >> >> ries.debian.org, the host behind ftp-master.debian.org, has hardware >> trouble, a failed memory module keeps resetting the machine at random >> intervals. > > A small update: Thanks to our DSAs ries seems to be working again, but *cough* well, 2 DIMMs are now taken out of the machine, which we hope have caused that problem, but we will see There will be a further downtime when the replacement DIMMs arrive. Greetings Martin -- Martin Zobel-Helas | Debian System Administrator Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100326162721.ga18...@ftbfs.de
Re: no updates since three days?
Hi, On Mon Mar 29, 2010 at 19:56:27 +0900, Norbert Preining wrote: > Is it possible that in the last three days nothing has been updated > or uploaded, or did I miss some important announcement? (was off > for some time in the moutains) > > Since several days aptitude does not show any updates at all. you should read debian-devel-announce an it's follow-ups on this list. http://lists.debian.org/debian-devel-announce/2010/03/msg00010.html -- Martin Zobel-Helas | Debian System Administrator Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100329105923.gg18...@ftbfs.de
Bug#577044: ITP: libmath-polygon-perl -- Polygon calculations
Package: wnpp Severity: wishlist Owner: "Martin Zobel-Helas" Owner: "Martin Zobel-Helas" * Package name: libmath-polygon-perl Version : 1.01 Upstream Author : Mark Overmeer * URL : http://search.cpan.org/dist/Math- Polygon/ * License : GPL, Artistic Programming Lang: Perl Description : Polygon calculations -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100409063959.19282.98668.report...@marra.vpn.ftbfs.de
Proposed changes to the Debian Machine Usage Policy (DMUP)
Hi,
the Debian Project Leader recently asked DSA in his delegation[1] to fix
a flaw in the current version of the DMUP, the fact that expulsions are
DAM's domain, and not our's.
I took the opportunity to also fix some other minor stuff in the current
version of the document. Please note that this is a first draft, not the
final version, which needs to be announced as per delegation to
debian-devel-announce.
Summary of changes: The Debian Systems Administration Team will do
whatever is necessary to keep all machines and services running.
Or to say it with someone else's words from IRC:
"DSA has to look after this crap, so please don't be a dick."
Find attached my proposed changes as commit log, as diff to the current
version and as full text of the new version.
I started mainaining the new version in git on
http://db.debian.org/git/DMUP.git, copied over frequently to
http://git.debian.org/?p=mirror/DMUP.git;a=summary (gitweb frontend).
Cheers,
Martin
[1] http://lists.debian.org/debian-devel-announce/2010/04/msg00016.html
--
Martin Zobel-Helas | Debian System Administrator
Debian & GNU/Linux Developer | Debian Listmaster
Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870
GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870
commit 6fe8c48ea05d8c2f5280aeff330c998b9a103ef7
Author: Martin Zobel-Helas
Date: Sun May 2 16:24:17 2010 +0200
Better wording for §0
Signed-off-by: Martin Zobel-Helas
commit f473e656a58efa062b44bca68c6b6d38f9886fd5
Author: Martin Zobel-Helas
Date: Sun May 2 16:10:09 2010 +0200
expulsions are DAM's domain
Signed-off-by: Martin Zobel-Helas
commit abcc73391e77840da60a5d9fcee81ec8fb05e1b6
Author: Martin Zobel-Helas
Date: Sun May 2 15:38:12 2010 +0200
Add a stanza about the intention of this document and DSA
Signed-off-by: Martin Zobel-Helas
commit 9965a489dcf11d3b0b6182a15b380e5caef19481
Author: Martin Zobel-Helas
Date: Sun May 2 15:03:55 2010 +0200
s/DSA's/DSA/
Signed-off-by: Martin Zobel-Helas
commit a704b18213b3ecfa2ac69fef522af9f1f7032d7b
Author: Martin Zobel-Helas
Date: Sun May 2 14:43:59 2010 +0200
Avoid first/second person wherever possible
commit 84fdb6be7c271fb03a051faee4def6a8f5302535
Author: Martin Zobel-Helas
Date: Sun May 2 14:31:37 2010 +0200
Move 2.4 to 2.1, as used abbreviations should be mentioned before being used
Signed-off-by: Martin Zobel-Helas
commit b249343ade59410dd4a2d515b6f70f69d03cd54d
Author: Martin Zobel-Helas
Date: Sun May 2 13:46:11 2010 +0200
Add a stanza about the version of this document.
Rational: Newer versions need to be announced as per DSA delegation stated
in http://lists.debian.org/debian-devel-announce/2010/04/msg00016.html
We also want that prior versions of that document become invalid when the
new version becomes valid.
Signed-off-by: Martin Zobel-Helas
commit eb4a1e7215b535bda6a447d72a7769bfc4f7
Author: Martin Zobel-Helas
Date: Sun May 2 13:33:50 2010 +0200
start new version of DMUP
commit ce85a966ae8e0c3476cc6309a35fbcccabdd90c7
Author: Martin Zobel-Helas
Date: Sun May 2 13:18:36 2010 +0200
initial version taken from cvs.d.o, Revision 1.7
diff --git a/DMUP b/DMUP
index 73312cf..8aba26e 100644
--- a/DMUP
+++ b/DMUP
@@ -1,10 +1,16 @@
Debian Machine Usage Policies
- Version 1.1.1
+ Version 1.1.2
+0. This version of the Debian Machine Usage Policies becomes effective
+ on $DATE1 and supersedes all previous versions. It was announced on
+ $DATE2
1. Introduction
This document describes the policies for using Debian machines
and all rules surrounding those.
In short:
+ + The Debian Systems Administration Team will do whatever is
+necessary to keep all machines and services working and
+running in a secure fashion.
+ Don't by any wilful, deliberate, reckless or unlawful act
interfere with the work of another developer or jeopardize the
integrity of data networks, computing equipment, systems
@@ -20,23 +26,24 @@ Debian Machine Usage Policies
guidelines specify rules that may be violated if necessary but we
would rather one did not.
2. General statements
- 1. Privilege
+ 1. Used abbreviations
+ o DSA - Debian Systems Administration Team
+ o DMUP - Debian Machine Usage Policy (this document)
+ o DPL - Debian Project Leader
+ o DAM - Debian Account Managers
+ 2. Privilege
Access to Debian Facilities is a privilege, not a right or a
-commercial service, and we reserve the right to revoke this
+commercial service, and DSA reserves the right to revoke this
privilege at any time, without prior notice. An expla
Re: Proposed changes to the Debian Machine Usage Policy (DMUP)
Hi, i just applied the following patch from Stefano Zacchiroli. 3b5a642da4b800dfde386df835e57b5d86f4 diff --git a/DMUP b/DMUP index 8aba26e..ced6cd0 100644 --- a/DMUP +++ b/DMUP @@ -55,9 +55,9 @@ Debian Machine Usage Policies Systems Administration and convince DSA that there will be no further breaches of the DMUP by the offender. 3. If the offender fails to contact DSA within 14 days, DSA - will propose this account to DAM to be terminated and the - offender expelled from the Debian project. If the offender - has announced they will be on vacation in this time frame + will suspend the corresponding account and propose to DAM the + expulsion of the offender from the Debian project. If the offender + has announced they will be on vacation in this time frame, this period will be extended with the announced duration of the vacation. 4. If the offender is expelled from the project they can @@ -65,8 +65,8 @@ Debian Machine Usage Policies month. The offense will remain on record. 2. Second offense 1. The offenders accounts will be suspended immediately and - DSA will propose this account to DAM to be terminated - immediately. + DSA will propose to DAM the expulsion of the offender from + the Debian project. 2. If the offender does not file for an appeal within the designated time frame the account is terminated. 3. The offender is prohibited from registering as a Debian -- Martin Zobel-Helas | Debian System Administrator Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100502164508.ga1...@ftbfs.de
Re: Work-needing packages report for Oct 22, 2010
Hi, On Fri Oct 22, 2010 at 00:25:44 +, w...@debian.org wrote: > The following is a listing of packages for which help has been requested > through the WNPP (Work-Needing and Prospective Packages) system in the > last week. > > Total number of orphaned packages: 0 (new: 0) > Total number of packages offered up for adoption: 0 (new: 0) > Total number of packages requested help for: 0 (new: 0) > > Please refer to http://www.debian.org/devel/wnpp/ for more information. I disabled that cronjob for now, it misses the bts2ldap part on quantz. Cheers Martin -- Martin Zobel-Helas | Debian System Administrator Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101022142644.gd6...@ftbfs.de
Re: A request for those attending key signing parties
Hi, a more theoretical question quite related to this: If one plans to have the key replaced in the keyring, and we have a fellow DD in the keyring who's only trust path to other Debian Developers goes via that key (this might become a real scenario when we do a bigger round of key replacements) will that key replacement really happen? Thus CCing keyring maintainers. Cheers, Martin -- Martin Zobel-Helas | Debian System Administrator Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110131201818.gk13...@ftbfs.de
Re: [DEP9] inet-superserver configuration by maintainer scripts
Hi, On Mon Feb 28, 2011 at 17:53:53 +0100, Serafeim Zanikolas wrote: > [M-F-T set to -devel and my email] > > Hi, > > I claim DEP-9 for a proposal on inetd.conf updates by maintainer scripts. This and > URL: http://dep.debian.net/deps/dep8 ^ Cheers Martin -- Martin Zobel-Helas | Debian System Administrator Debian & GNU/Linux Developer | Debian Listmaster GPG key http://go.debian.net/B11B627B | GPG Fingerprint: 6B18 5642 8E41 EC89 3D5D BDBB 53B1 AC6D B11B 627B -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110228171251.gj13...@ftbfs.de
Re: cdn.debian.net as a project service?
Hi, On Thu Mar 10, 2011 at 10:22:29 +0100, Peter Palfrader wrote: > On Thu, 10 Mar 2011, Lars Wirzenius wrote: > I'd really like to see support for sane mirror selection in apt itself, > possibly with archive support (i.e. list of mirrors somewhere on > ftp.d.o). That would allow apt to for instance retry on a different > server if the first one it tried does not work for some reason, and > maybe even report the problem to a central mirror. some information about this might be outdated by now, but the idea still stands: http://wiki.debian.org/RedirectProposal Maybe make this a GSoC2011 project? Cheers, Martin -- Martin Zobel-Helas | Debian System Administrator Debian & GNU/Linux Developer | Debian Listmaster GPG key http://go.debian.net/B11B627B | GPG Fingerprint: 6B18 5642 8E41 EC89 3D5D BDBB 53B1 AC6D B11B 627B -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110310103637.gh18...@ftbfs.de
Re: cdn.debian.net as a project service?
Hi, On Thu Mar 10, 2011 at 12:09:32 +, Philipp Kern wrote: > On 2011-03-10, Mike Hommey wrote: > > On Thu, Mar 10, 2011 at 08:58:55AM +, Lars Wirzenius wrote: > >> What would it take to get cdn.debian.net become a service provided by > >> the project? In other words, cdn.debian.org, instead of cdn.debian.net. > >> If we had cdn.debian.org, we could make it into a default mirror (which > >> could potentially skip one question in the installer), debmirror, > >> pbuilder, piuparts, and other tools that need to have a mirror > >> specified, making it easier to use the tools. It would also be a boon > >> for those who travel a lot. > > Isn't ftp.debian.org resolving to different addresses depending on your > > geolocalization nowadays ? > > security is, ftp.debian.org isn't. It's even special as it's a mirror > that's synced pretty early. our automatism though check if ftp.d.o is to be shutdown for reboot and itself points ftp.d.o to another host in the mirror network. So yes, from time to time ftp.d.o does not point to kassia. Cheers, Martin -- Martin Zobel-Helas | Debian System Administrator Debian & GNU/Linux Developer | Debian Listmaster GPG key http://go.debian.net/B11B627B | GPG Fingerprint: 6B18 5642 8E41 EC89 3D5D BDBB 53B1 AC6D B11B 627B -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110310125612.gi18...@ftbfs.de
