Re: Downtime for some debian.org machines (people, db, buildd, etc.)
On Fri, 24 Mar 2006, James Troup wrote: > This Saturday (2006-03-25) between 13:00 - 21:00 UTC, the debian.org > machines hosted by HP are going down due to maintenance in their cage > on the power systems. The following machines and services are > affected: > > o gluck - people.d.o, planet.d.o, cvs.d.o, lintian.d.o, etc. > o raff - buildd.d.o > o merkel - qa.d.o, nm.d.o > o samosa - db.d.o > o merulo - ia64 porter box > o paer - hppa porter box > o peri - hppa 2nd buildd And haydn - alioth.debian.org ! Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Moving GFDL documentation to non-free
Manoj Srivastava <[EMAIL PROTECTED]> writes: > > I was told unequivocally that just shipping the whole tarball > for make, which is 1.5MB large, would not be acceptable. I ended up I was suspecting this. > having to create two new .orig.tar.gz files, with minimal overlap in > contents, (remove docs from one, and the sources from the other, and > leave some build infrastructure in both) and uploading that. OK. It sounds sane to me. > I also called these source packages make-dfsg and > make-doc-non-dfsg, but I think others have let the package in main be > still called foo (despite removing non-free bits from it), and just > append .dfsg to the upstream version number. I was not comfortable > with that, but your mileage may vary. Well, appending .dfsg to the upstream version would probably be less confusing for users, but as you said YMMV. Thank you very much for your feedback. -- Jérôme Marant
Re: Moving GFDL documentation to non-free
On 10604 March 1977, Jérôme Marant wrote: > The simplest way I can see is to take the pristine tarball and rename > to foo-non-free of foo-non-dfsg, and to just install what was removed > from the modified tarball in main. However, the Emacs tarball is > 18 megs big so I'm not sure ftp masters would allow it in the archive. Rebuild the tarball. You need to do that anyways for main, so build a new one for non-free too, containing only the rest and what may be needed to built it. Dont rename the source package for main too. Was allowed for make, but its better to not rename. -- bye Joerg [http://www.youam.net/stuff/info...-hosting.de/server-info.php] "[...] und der Arbeitsspeicher recht schnell und hoch ist." (Wie hoch? 2cm, 4cm? Am besten an die Decke nageln, was? pgpqfF6zFFAFF.pgp Description: PGP signature
Re: etch before vista
Kevin Mark wrote: > On Fri, Mar 24, 2006 at 09:28:47PM -0500, Benjamin Seidenberg wrote: > >> Kevin Mark wrote: >> >>> Hi *, >>> I noticed on occassion on -devel and planet that folks mention in passing >>> that "I'll be in MN in US from MAR 01 thru 05" and I'd like to have a >>> beer and do keysigning. Would it be worthwhile to create a list like >>> 'debian-meetup' (or debian-beer-meetup x-))that would allow folks to >>> give this info on what would be a low-volume list. I love to meetup with >>> floss folks who have a flight stop-over or will be in town for a day or >>> so. I guess some issue maybe the idea of personal security and >>> privacy--- people knowing where you will be and providing contact >>> info--but the messages as specific as people want and the basic info >>> could be state and email contact address with a month/week given. >>> Cheers, >>> Kev >>> ps. I recall folks saying that debian-private has 'holiday info' or >>> people whereabouts. This would be voluntary and would not include that >>> info. >>> >>> >> I think a wiki would be more effective. That way you could have people >> in those areas say "I'd love to meet any DD passing through" and >> actually be noticed. It could be organized with separate pages for >> various regions, etc. >> > Hi Ben, > so instead of DD-post->ML-sent->readers, you'd say > readers-post->wiki-read->DD-sent->readers? > > so if r(0)+r(1)+...r(n)=R all people in regions > then the mailing list would be sent to R people while with your approach > the DD(x) would send mail to r(x) people where DD(x) would be the DD > going to region(x) and r(x) would be the people in that region? So that > would mean that less people would be emailed and be 'more efficient'? > > I think that approach requires more 'effort' because the people have to > find the right page on the wiki, figure out how to add their name and > then the DD has to find the right page on the wiki also and then extract > the list and then mail them. Whereas, my idea for the readers to just > subscribe to the list and the DD's to post to the list. > > Cheers, > Kev > I was thinking more about how easy it is to access old data. Lets say I'm going to Boston, and also want to see who's in town. I would have to go searching through the past month or so on the mailing list archives to find who else is going. I also wouldn't be able to see people who live there. While I could email the list, that requires every person who is going to Boston or lives there to email me back. They'd also have to email every other person. Compare this to the wiki, where they simply go to the Boston page, update it with their details once, and it's set. HTH, Benjamin signature.asc Description: OpenPGP digital signature
Keysignings and other "meetups" (Was: etch before vista)
On Sat, 2006-03-25 at 11:53 -0500, Benjamin Seidenberg wrote: > Kevin Mark wrote: > > On Fri, Mar 24, 2006 at 09:28:47PM -0500, Benjamin Seidenberg wrote: > > > >> Kevin Mark wrote: > >> > >>> Hi *, > >>> I noticed on occassion on -devel and planet that folks mention in passing > >>> that "I'll be in MN in US from MAR 01 thru 05" and I'd like to have a > >>> beer and do keysigning. Would it be worthwhile to create a list like > >>> 'debian-meetup' (or debian-beer-meetup x-))that would allow folks to > >>> give this info on what would be a low-volume list. [..] > I was thinking more about how easy it is to access old data. You might want to check https://www.biglumber.com/ which contains already a very nice interface for all of this. Greets, Jeroen signature.asc Description: This is a digitally signed message part
Re: GFDL question
On Wed, 2006-03-15 at 14:06 -0800, Thomas Bushnell BSG wrote: > Norbert Preining <[EMAIL PROTECTED]> writes: > > > Ok, there are no invariant sections, but there is (a short) front and > > back cover text. > > > > How do we proceed with these documents? > > The resolution which passed excludes documentation with front cover > texts. Read it. I re-read it, and it states: | This means that works that don't include any Invariant Sections, Cover | Texts, Acknowledgements, and Dedications (or that do, but permission | to remove them is explicitly granted), are suitable for the main | component of our distribution. -- -- arthur - [EMAIL PROTECTED] - http://people.debian.org/~adejong -- signature.asc Description: This is a digitally signed message part
Re: Moving GFDL documentation to non-free
Joerg Jaspert <[EMAIL PROTECTED]> writes: > On 10604 March 1977, Jérôme Marant wrote: > >> The simplest way I can see is to take the pristine tarball and rename >> to foo-non-free of foo-non-dfsg, and to just install what was removed >> from the modified tarball in main. However, the Emacs tarball is >> 18 megs big so I'm not sure ftp masters would allow it in the archive. > > Rebuild the tarball. You need to do that anyways for main, so build a > new one for non-free too, containing only the rest and what may be > needed to built it. > Dont rename the source package for main too. Was allowed for make, but > its better to not rename. I intend to do that. Thanks. -- Jérôme Marant
Bug#358979: ITP: pyvnc2swf -- Pyvnc2swf is a cross-platform screen recording tool
Package: wnpp Severity: wishlist Owner: Bastian Venthur <[EMAIL PROTECTED]> * Package name: pyvnc2swf Version : 0.8.2 Upstream Author : Yusuke Shinyam <[EMAIL PROTECTED]> * URL : http://www.unixuser.org/~euske/vnc2swf/ * License : GPL Description : Pyvnc2swf is a cross-platform screen recording tool Pyvnc2swf captures screen motion through VNC protocol and generates a Shockwave Flash (SWF) movie. In contrast to vnc2swf, pyvnc2swf runs on more platforms (Linux, BSD, Solaris, Mac OS X and Windows), has more functions and is beeing actively developed. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686-smp Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Keysignings and other "meetups" (Was: etch before vista)
Jeroen Massar wrote: > On Sat, 2006-03-25 at 11:53 -0500, Benjamin Seidenberg wrote: > >>Kevin Mark wrote: >> >>>On Fri, Mar 24, 2006 at 09:28:47PM -0500, Benjamin Seidenberg wrote: >>> >>> Kevin Mark wrote: >Hi *, >I noticed on occassion on -devel and planet that folks mention in passing >that "I'll be in MN in US from MAR 01 thru 05" and I'd like to have a >beer and do keysigning. Would it be worthwhile to create a list like >'debian-meetup' (or debian-beer-meetup x-))that would allow folks to >give this info on what would be a low-volume list. > > [..] > > >>I was thinking more about how easy it is to access old data. > > > You might want to check https://www.biglumber.com/ which contains > already a very nice interface for all of this. Or you might want to use https://nm.debian.org/gpg_offer.php. Have a look at https://nm.debian.org/gpg.php if you want to be listed... Cheers Luk -- Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D Fingerprint: D5AF 25FB 316B 53BB 08E7 F999 E544 DE07 9B7C 328D signature.asc Description: OpenPGP digital signature
[NOD32: deleted] hello
Mail transaction failed. Partial message is available. Notification from NOD32 Warning: NOD32 Antivirus System for Linux Mail Server found the following infiltrations in this message: file.zip - Win32/Mytob.Y worm - unable to clean - deleted http://www.nod32.com
Re: Keysignings and other "meetups" (Was: etch before vista)
Luk Claes wrote: > Jeroen Massar wrote: > >> On Sat, 2006-03-25 at 11:53 -0500, Benjamin Seidenberg wrote: >> >> >>> Kevin Mark wrote: >>> >>> On Fri, Mar 24, 2006 at 09:28:47PM -0500, Benjamin Seidenberg wrote: > Kevin Mark wrote: > > > >> Hi *, >> I noticed on occassion on -devel and planet that folks mention in passing >> that "I'll be in MN in US from MAR 01 thru 05" and I'd like to have a >> beer and do keysigning. Would it be worthwhile to create a list like >> 'debian-meetup' (or debian-beer-meetup x-))that would allow folks to >> give this info on what would be a low-volume list. >> >> [..] >> >> >> >>> I was thinking more about how easy it is to access old data. >>> >> You might want to check https://www.biglumber.com/ which contains >> already a very nice interface for all of this. >> > > Or you might want to use https://nm.debian.org/gpg_offer.php. Have a > look at https://nm.debian.org/gpg.php if you want to be listed... > > Cheers > > Luk > > (For those who tried to access it, that service is currently down due to a planned outage at HP). That's what I was thinking of when I suggested a wiki. The problem with the NM one is it is hard to change, and often out of date. A wiki would allow anyone to change it, without the bottleneck of going through whoever is in charge of it (Front Desk I assume). Benjamin signature.asc Description: OpenPGP digital signature
Re: Keysignings and other "meetups" (Was: etch before vista)
On Sat, Mar 25, 2006 at 01:16:16PM -0500, Benjamin Seidenberg wrote: > Luk Claes wrote: > > Jeroen Massar wrote: > >> On Sat, 2006-03-25 at 11:53 -0500, Benjamin Seidenberg wrote: > >>> Kevin Mark wrote: > On Fri, Mar 24, 2006 at 09:28:47PM -0500, Benjamin Seidenberg wrote: > > > Kevin Mark wrote: > > > >> Hi *, > >> I noticed on occassion on -devel and planet that folks mention in > >> passing > >> that "I'll be in MN in US from MAR 01 thru 05" and I'd like to have a > >> beer and do keysigning. Would it be worthwhile to create a list like > >> 'debian-meetup' (or debian-beer-meetup x-))that would allow folks to > >> give this info on what would be a low-volume list. > >> > >> [..] > >> > >>> I was thinking more about how easy it is to access old data. > >>> > >> You might want to check https://www.biglumber.com/ which contains > >> already a very nice interface for all of this. > > > > Or you might want to use https://nm.debian.org/gpg_offer.php. Have a > > look at https://nm.debian.org/gpg.php if you want to be listed... > > > > Cheers > > > > Luk > > > (For those who tried to access it, that service is currently down due to > a planned outage at HP). > That's what I was thinking of when I suggested a wiki. The problem with > the NM one is it is hard to change, and often out of date. A wiki would > allow anyone to change it, without the bottleneck of going through > whoever is in charge of it (Front Desk I assume). Gentlemen, there is nothing development-related about this, please take these kinds of discussions to debian-project to enhance debian-devel's signal-to-noise ratio with respect to development. thanks, Michael -- Michael Banck Debian Developer [EMAIL PROTECTED] http://www.advogato.org/person/mbanck/diary.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
idea for project machines
Howdy, Suppose you're a debian developer with limited time each week for Debian. You get a bug report because your package fails to build on architecture X. When you have your 2 hour window to sit down and fix things, you log in to one of the project machines of the appropriate architecture, apt-get your sources, chroot into sid, and discover that one of the build-dependencies is missing. There's no way to debug the build problem: by the time you find the right address to email about adding the build-dependency, your time window is up and the issue is forgotten for another week or month. Wouldn't it be nice if you could simply "sudo apt-get install " yourself? Is it feasible to have at least some of the sid chroots allow this? Alternatively, how about "sudo pbuilder login ..."? Comments? -Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: idea for project machines
On Sat, 2006-03-25 at 15:01 -0500, Steve M. Robbins wrote: > [...] apt-get your sources, chroot into sid, and discover that > one of the build-dependencies is missing. There's no way to debug the > build problem: by the time you find the right address to email about > adding the build-dependency, your time window is up and the issue is > forgotten for another week or month. > > Wouldn't it be nice if you could simply "sudo apt-get install " > yourself? Is it feasible to have at least some of the sid chroots > allow this? Alternatively, how about "sudo pbuilder login ..."? I was in this situation some time already. But it isn't a solution to get sudo apt-get install rights. Someone who may have a build-conflict with your build-depends won't be happy if you install that package(s). Also your build-depends may conflict with others build-depends and those would be removed. Again a someone is not happy situation. Regards, Laszlo/GCS signature.asc Description: This is a digitally signed message part
Building the whole Debian archive with GCC 4.1: a summary
Over the last 2.5 weeks I have built the complete Debian archive on a quad-core MIPS machine donated by Broadcom using the recently released version 4.1 of GCC. In parallel, I have done the same on an EM64T box donated to Debian by Intel and hosted by Stephen Frost. The purpose of this exercise was three-fold: - Find out about compiler problems in GCC 4.1 itself as well as in packages that may fail with the new version *before* GCC 4.1 is uploaded to unstable. GCC, in particular G++, is becoming stricter regarding adherence to standards and packages may fail to build with 4.1 due to invalid code that was accepted previously. - Find out about MIPS specific problems in GCC 4.1 and to answer Matthias Klose's question [1] as to which platforms can move to GCC 4.1 as the default compiler once it is uploaded to unstable. - Find MIPS specific assembler warnings and create a list of all users of xgot (a MIPS specific toolchain problem). Executive summary - GCC 4.1 itself appears to be very stable, both on MIPS and AMD64. There are, however, a large number of packages using code (especially C++) which GCC 4.1 treats as errors. Fortunately, most of them are trivial to fix. By compiling about 6200 packages, over 500 new bugs have been discovered and submitted, 280 of which are specific to the increased strictness of GCC 4.1. Patches for 2/3 of those GCC 4.1 specific bugs have been submitted. Based on my findings, Ben Hutchings has prepared a summary of the most common C++ syntax errors (that weren't treated as such before G++ 4.1): http://womble.decadentplace.org.uk/c++/syntax-errors.html Methodology --- I generated a list of package that are "Architecture: any" or "mips", sorted by upload (old packages first). I then started compiling these packages, and after the mirror pulse I would update my packages list again (excluding packages which had no new version). What I explicitly did *not* do was to exclude packages which have known build failures because I wanted to see if they might have GCC 4.1 issues too. Another thing I did on MIPS which the official build machines would not do is to compile as "mips64" rather than "mips" (using a 64-bit kerneel but 32-bit userland, uname -m shows "mips64"; this can be changed by using the linux32 program). The aim of this was to identify mips64 specific problems. I compiled every packages that failed with "mips64" using "mips" too, though. In total, 6192 individual packages were compiled on MIPS, with 6761 compilations (because of new versions uploaded to the archive during those two weeks). A listing is available from [2] and all build logs from MIPS from [3]. On AMD64, the number of individual packages compiled was 5862. This number is lower than the one for MIPS because I started with MIPS first and then ignored packages on AMD64 with known build errors. Detailed summary of bugs found -- While I've tried to keep count of the different errors, some of the numbers are slightly off, partly because you do make some errors when keeping track of so many bugs and partly because the classification below is quite arbitrary and I slightly changed it over time. (Normally, you'd go back and classify each bug again, but I didn't do that because this was not a scientific study.) 1. New bugs I have filed in the BTS - gcc/g++ 4.1 strictness: 277 (see [4] for a list] - failures due to the new version of make: 4 - old or missing build-dependencies: 50 - host type cannot be recognized: - config.* out of date: 26 - other method (mips64): 7 - other method (amd64): 1 - architecture specific bugs: - mips: 9 - amd64: 7 - GCC 4.1 compiler bugs: 6 - packages that could (but don't) support mips: 5 - non-i386 brokenness: 4 - 64-bit brokenness: 2 - a cast loses precision: 2 - not using PIC: 1 - .orig.tar.gz missing from archive: 1 - other/generic: 50 2. The build is "successful" but there is a bug if you look closely I tried to look at successful build logs but with over 6000 packages I could obviously not do so in great detail. Therefore, I'm sure there are other bugs in "successful" builds I missed. - "Architecture" is "any" but should be "all": 45 - package contains nothing useful (no binary, no headers, etc): 1 - package contains no binary on !i386: 1 - build doesn't show what commands are run (wishlist bug): 2 - test suite not run (wrong command): 1 3. Bugs which I saw but which have already been reported - gcc/g++ 4.1 strictness: 2 - gcc/g++ 3.4/4.0 strictness: 17 - failures due to the new version of make: 6 - old or missing build-dependencies: 66 - host type cannot be recognized: - config.* out of date: 42 - architecture specific bugs: - mips: 2 - amd64: didn't count but there some - non-i386 brokenness: 27 - 64-bit brokenness: 3 - a cast loses precision: 2 - not using PIC: 2 - the "Architecture" is "any" but should be "all": 2
Re: idea for project machines
Laszlo Boszormenyi <[EMAIL PROTECTED]> writes: > On Sat, 2006-03-25 at 15:01 -0500, Steve M. Robbins wrote: >> [...] apt-get your sources, chroot into sid, and discover that >> one of the build-dependencies is missing. There's no way to debug the >> build problem: by the time you find the right address to email about >> adding the build-dependency, your time window is up and the issue is >> forgotten for another week or month. >> >> Wouldn't it be nice if you could simply "sudo apt-get install " >> yourself? Is it feasible to have at least some of the sid chroots >> allow this? Alternatively, how about "sudo pbuilder login ..."? > I was in this situation some time already. But it isn't a solution to > get sudo apt-get install rights. Someone who may have a build-conflict > with your build-depends won't be happy if you install that package(s). > Also your build-depends may conflict with others build-depends and those > would be removed. Again a someone is not happy situation. > > Regards, > Laszlo/GCS Create a new custom chroot with the packages preinstalled on demand. Let the command have an option for how long the chroot should remain after logout and after that time remove it. That way there shouldn't be too many chroots at any one time. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Debian Packages for XaraLX
Hi everybody, on http://people.debian.org/~nomeata/xaralx/, you can find debian source and binary (i386) packages for XaraLX[1], the recently GPL-freed vector drawing application. The packages are there for public review of both the program itself and the packaging work. Please note that until XaraLX can be uploaded to debian, two things have to happen: The CDraw library (currently included as a binary) has to be freed, and wxwidgets 2.6.3 has to be uploaded to debian. The current package is built with version 2.6.1 of wxwidgets, which is in Debian, but causes some slider problems. Also, the current packages does not have any sensible build-depends yet. I will figure them out later, but if you happen to compile it on your machine, I'll be glad to accept hints that shorten my trial-and-error-using-pbuilder time :-) Also, there is no manpage for XaraLX yet. Debian requires a manpage for every binary, so some short descriptive manpage should be created. @XaraLX-developers: Are you going to do that some time? Then I can skip that step. The package description is not yet perfect. Currently, it contains too much MarketSpeak, I'd prefer a more objective description. Suggestions are very welcome. Of course, any kind of comment, criticism and contribution is welcome. Greetings, Joachim [1] http://www.xaraxtreme.org/ -- Joachim "nomeata" Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: idea for project machines
On Sun, 2006-03-26 at 00:22 +0100, Goswin von Brederlow wrote: > Create a new custom chroot with the packages preinstalled on demand. Sounds like a use-case for combining pbuilder and cowdancer (or lvm snapshots). No time-consuming tarball extraction, disk usage is reduced and the original chroot is untouched. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: idea for project machines
Laszlo said: > On Sat, 2006-03-25 at 15:01 -0500, Steve M. Robbins wrote: > > Wouldn't it be nice if you could simply "sudo apt-get install " > > yourself? Is it feasible to have at least some of the sid chroots > > allow this? Alternatively, how about "sudo pbuilder login ..."? > > I was in this situation some time already. But it isn't a solution to > get sudo apt-get install rights. Someone who may have a build-conflict > with your build-depends won't be happy if you install that package(s). > Also your build-depends may conflict with others build-depends and those > would be removed. Again a someone is not happy situation. All true. But the current situation is similar. I may ask Mr. build-machine-admin to install package X that conflicts with package Y that someone else needs. If Mr. admin is not aware that Y is currently in use, someone is unhappy. My suspicion is that this won't happen often enough to worry about. Once it does happen often enough, a more complex solution -- perhaps involving pbuilder -- could be instituted. Regards, -Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
