- Arch-dev-public - lists.archlinux.org

[arch-dev-public] Arch project management?
by Jason Chu 20 Apr '07

20 Apr '07

A lot of people have been saying that quality control in Arch has gone down the crapper (gotten worse, for the non-native english speakers). Obviously we can't test everything on everyone's machine or even test all the features of all of our packages, so what can we do? Someone suggested that we have someone who manages quality control. I don't like thinking of it as a procedural problem, so I'm going to phrase it differently. I think we need someone who makes sure that things don't get forgotten, by the developers and by the community. Someone to prod the devs and the community to test things and make sure things don't get lost. Roman already does this very very well for the bug tracker. Since we hired a bug hunter, bugs get addressed^H^H^H^H^H^H^H^H^Hassigned very quickly. What if we had the same thing for the larger/more important packages, like kernel26, glibc, apache, everything in core? The idea isn't to just throw process at the problem, but to be a little more organized in our package verification. I don't care how the organizer does it either, just as long as they make sure that people are happy with changes before they go into current/extra. I'm not suggesting any of the developers do this either, we need someone new who isn't maintaining packages, already busy with Arch developer stuff, and is active in the community. Everyone has 1 week to get their comments in before I start looking. Jason

5 6

[arch-dev-public] very outdated mirror(s)
by Roman Kyrylych 20 Apr '07

20 Apr '07

Hi! I'd like to discuss issues with mirrors being very out-of-date. ftp://ftp.nethat.com/pub/linux/archlinux/ was last updated on 2007-03-27 Can there be some way to make tracking such things easier? For example, Ukrainian mirror has {current,extra,unstable,testing,community}.lastsync files with content like: community synced at: 04/20/07 01:10 -- Roman Kyrylych (Роман Кирилич)

2 1

Re: [arch-dev-public] [Fwd: Fw: OpenSSL 0.9.8e has serious bug]
by Tom K 20 Apr '07

20 Apr '07

Valient Gough wrote: > > Hi Tom, > > I don't know if there is any tracking of OpenSSL bugs. While testing > out user reports of 0.9.8e incompatibility, I narrowed it down to an > OpenSSL problem and sent a simple test case to the OpenSSL mailing list. > > http://www.mail-archive.com/openssl-users@openssl.org/msg48671.html > > I haven't dug through OpenSSL to determine the entire extent of the > problem. I believe it causes Blowfish to use 128-bit encryption no > matter what key length you specify. > > Valient > Thanks for getting back to me. I would be grateful if you could test my patched build, available here: http://www.archlinux.org/~tom/packages/openssl-0.9.8e-3.pkg.tar.gz PKGBUILD and patch here: http://www.archlinux.org/~tom/packages/openssl/ T. P.S. I've already posted this on our public dev list, but as you may not be a subscriber, I'm sending it to you directly also.

1 0

[arch-dev-public] Consensus on network scripts
by James 20 Apr '07

20 Apr '07

Hey, http://wiki.archlinux.org/index.php/Network_Scripts I've been pushing these repeatedly, with only meager interest shown by others. Given a little bit of documentation, I think they're almost ready for me to unleash and publicise for further testing. That said.... before I put the time into writing the docs, closing some known bugs, and publicising them more, I'd like to know what everyone thinks and get some 'approval' for them. Some sort of OK, we'll adopt and implement these given A, B and C are done. I don't know what the process is for this, nor do I think we've ever had/needed one as discussion should be fine, so bear with me. I realise that not everyone wants to install these and try them, so I'll just outline the major outward changes in order of what might cause debate. New features and improvements are listed on the wiki. - All network scripts moved from 'initscripts' to 'network', a separate package - /etc/rc.d/network retains ALL functionality that it has had previously, except it's wireless. - /etc/rc.conf network syntax remains, except it's wireless. - All wireless functionality now exists within the profiles. - /etc/network-profiles is no more, moved to /etc/network.d - profile syntax has changed, now using an ini format. See wiki for examples. - completely rewritten and cleaned up netcfg - netcfg menu support separated out from netcfg - network profiles moved from /etc/rc.d/network to /etc/rc.d/net-profiles Beyond that.... the changes are internal. Some minor cleanups and bugfixes in /etc/rc.d/network, and the rest of the changes are within netcfg and the Arch profile system. If you're interested in testing... there's details on the wiki, i've got a repo up in my public_html on archlinux.org. Feel free to put bugs on the tracker, or send via email. Patches to latest git are always welcome. Anything to say, add, suggest, please do, +1's great, +>1's better, -1's only with a good fair explanation. Thanks! James -- iphitus // Arch Developer // kernel26beyond // iphitus.loudas.com

5 8

[arch-dev-public] Updating base /etc files
by Aaron Griffin 20 Apr '07

20 Apr '07

This is split from the "iputils and traceroute" discussion on arch-dev, moving it to the public list, and splitting things out. The issue is that our stock /etc/services and /etc/protocols files suck. Here's what I'd like to do - rip these files out of the iputils package and stick them in the 'filesystem' package. We can then grab updated files from NetBSD: http://cvsweb.netbsd.org/bsdweb.cgi/src/etc/ As proposed in this bug report: http://bugs.archlinux.org/task/6194 I would also like to suggest one more file be updated, but am unsure if it should be part of the filesystem package: /etc/mailcap mailcap is actually really useful for things like firefox, which falls back to there if some of those goofy gnome services aren't running (I don't use them, so it cripples firefox here unless I use a ~/.mailcap) There is a huge problem with this, though, and that would be the fact that we'd have to add/remove entries to it to do things successfully... however, if we don't want to do this, we could at least provide entries for all out base packages (for instance, less and tar). - Aaron

4 10

[arch-dev-public] new screen with pty group set
by Aaron Griffin 20 Apr '07

20 Apr '07

Hey all, just a "heads up" The screen package in testing has the "pty group" set to 5, which is our "tty" group in /etc/group This was requested via IRC, but i don't know if it would have a greater impact I'm unaware of, so I pushed it to testing for the time being. Please let me know if it all works for you.

1 0

Re: [arch-dev-public] Fw: OpenSSL 0.9.8e has serious bug
by Tom K 20 Apr '07

20 Apr '07

David Rosenstrauch wrote: > Tom, > > I use EncFS pretty extensively, so I can assist you with testing if you > need. > > DR > Thanks David. Get it here for now: http://www.archlinux.org/~tom/packages/openssl-0.9.8e-3.pkg.tar.gz PKGBUILD and patch here: http://www.archlinux.org/~tom/packages/openssl/ I've asked the original reporter for details on the known OpenSSL/Blowfish problem, for inclusion in Arch News etc. T.

1 0

[arch-dev-public] [Fwd: [drotschm@linuxtag.org: [LT07-Pro-Announce] Infomail #3, April 19, 2007]]
by Alexander Baldeck 19 Apr '07

19 Apr '07

News from Linuxtag! :) -------- Original Message -------- Subject: [drotschm(a)linuxtag.org: [LT07-Pro-Announce] Infomail #3, April 19, 2007] Date: Thu, 19 Apr 2007 15:11:07 +0200 From: Christoph Neuroth <christoph.neuroth(a)gmx.net> To: Alexaner Baldeck <kth5(a)archlinuxppc.org> Gute Neuigkeiten! Zu Punkt 1: Wir haben einen 24m^2 Stand zusammen mit T2SDE (fork von ROCK Linux) und mandrivauser.de chris ----- Forwarded message from Wolfgang Drotschmann <drotschm(a)linuxtag.org> ----- Date: Thu, 19 Apr 2007 11:03:12 +0200 From: Wolfgang Drotschmann <drotschm(a)linuxtag.org> To: projects-announce(a)linuxtag.org Subject: [LT07-Pro-Announce] Infomail #3, April 19, 2007 Dear Projects, this is probably the most awaited mail you'll have received this week ;-) We would like to inform you about: o Booth Size, Layout and Equipment o Completion of vCC Record o Insurance o Beverages o Exhibitor Passes o Project Workshops o Banners for Your Website So you see, it's a lot of stuff. 1. Boot Size, Layout and Equipment This year we will try some new concepts and ideas for the free software project exhibition. The main idea is to get rid of the 5-10 sqm sized booths and to create an open, communicative ambience. Therefore we merged thematically related projects to a bigger booth - we occasionally use the word 'island' here :-) We talked to a number of you in the last days. If you share your booth with other projects, you can find them in the vCC [1]. To get the equipment for each booth planned, we urge you to check for your vCC entry regarding equipment you'll bring with you. Please updated the 'Equipment' field as soon as possible. Which brings us to... 2. Completion of vCC Record One advantage of a central data source is... well, you can get all the data you need from there. LinuxTag's source is the vCC. We use the information you fed into it to automagically generate the bits of information the visitor wants to know. Which are: o Project Title o Descriptions {en,de} x {long,short} Please complete or proof-read your vCC record! 3. Insurance LinuxTag cannot apply for an additional insurance to cover all projects and their equipment. Therefore, you should be very careful with the equipment you are going to use. If breaks, it's broken. You should also not leave small parts of value at the booth if there are no staff members at the booth, or when you are outside the exhibition (i. e. during the evening and morning). It should be sufficient to place movable parts in a box at the back of the booth. You should also not place larger items (like monitors and boxes) in the front of the booth in a way so that they can be carried away easily. Obeying to these basic rules should help you not loose any of your equipment. 4. Beverages If your project plans to hand visitors fluids of one kind or another, please ensure that this doesn't turn your booth into a beverages bar. This would actually cause a lot of problems because there's a default caterer and that company is the only one that is allowed to sell beverages at the exhibition center. They will get angry and try legal tricks (like asking for Korbgeld, see Wikipedia.de [2]) if they feel somebody is poaching in their territory. It is no problem to provide a cup of coffee or a glass of water to visitors inside the booth when talking to you and staff. Things just shouldn't spread. 5. Exhibitor Passes The exhibitor passes for project booth members will continue to be free of cost for a reasonable amount of booth personnel. However, they are not meant as a means for regular visitors to save the entrance-fee. Hence, please don't abuse this, and don't add random visitors as booth staff if they don't belong to your booth. For this matter we'll receive some eTickets later on. You can now order the exhibitor passes for each accepted project using the vCC. Please login at the virtual Conference Center and click in the Main menu on "Project" and then in submenu on "Projects". Each accepted project will find a button "Order exhibitor passes". After you ordered the passes, we will have a look at the list and approve them. Otherwise you will get an email from us. You'll need either normal entrance tickets or exhibitor passes for entering LinuxTag. You can get exhibitor passes on Tuesday at the LinuxTag office for the registered project staff. You can either get a single pass for your own, or the whole bunch for the entire project (or a mixture). If you fetch the passes for the entire project, please make sure that the other project members know this and know a way to get to the passes after the show has opened. Since our office is located behind the regular entrance, this won't work the same way when the show is going on. If you arrive after LinuxTag has already started, you'll have to either get a normal entrance ticket or ask your colleagues to provide you with an exhibitor pass from the inside. 6. Project Workshops Like last year we wait for your suggestions for project workshops! We'll reserve a number of rooms for this. It was well received by visitors in 2006, and most probably, because it will be on display for visitors again, will have a good number in audience this year, too. With you we'll use this "Workshop Rooms" to jointly organise a "projects to projects programme" or "developer to developer programme". Main purpose for these rooms is to provide attending projects an opportunity to talk to other developers (not necessarily from the same project) and to go into detail for a larger group than what would be possible at the booth. Please note: all workshops will be open to the public and will be announced so. In special cases we can make an exception, but we would like to discuss this in detail with you, if you think a session should be non-public. LinuxTag provides presentation equipment and probably Internet connectivity for all rooms. Normally a slot is 60 Minutes (don't forget to reserve some minutes at the end so the next workshop can be prepared!), if your workshop takes longer leave us a note within your abstract. Also do so, if you have a preference for a certain day. You can neglect the licence because it is not planned to distribute your submission (like a paper for the conference programme). But please do not forget to choose the language for your workshop submission. English may be your language of choice, but it is a valuable information for an interested visitor. Submissions can be placed -guess what!- in our vCC, please use your vCC account, and please choose category "Project Workshop" for your proposal here. Deadline is the April 27, 2007. 7. Banners for Your Website If you want to show your commitment to this years LinuxTag, or point visitors of your website to your booth, why not use a banner we prepared already for you? Please choose from the items over here: http://www.linuxtag.org/2007/de/expo/banner.html Please send us a short notice including links to the pages where you have placed the banners. Next Infomail will discuss... o ...how to provide us with your logo in an open vector format (PDF or EPS or SVG) and bitmap (JPG or PNG), o ...the whereabouts of deliveries, o ...booth security, storage for your equipment and luggage, o ...the size of the infopoints, and o ...accomodation. Please stay tuned! Regards, Susanne Pfeifer, Wolfgang Drotschmann, Marko Jung & Martin Schulte Project Committee LinuxTag 2007 [1] http://www.linuxtag.org/vcc/cc.pl?rm=projects [2] http://de.wikipedia.org/wiki/Korbgeld ----- End forwarded message -----

2 1

[arch-dev-public] 2.6.21-rc6-git2 please test!
by Tobias Powalowski 19 Apr '07

19 Apr '07

Hi just to inform all developers, the new kernel can be downloaded from this adress: http://www.archlinux.org/~tpowa/2.6.21/ or as repo [kernel] http://www.archlinux.org/~tpowa/2.6.21/ All developers that have modules and hardware are invited to test the already provided ones. I need your feedback on this task, to avoid broken modules in the future. Only broken one is ivtv at the moment and i haven'T build the unstable modules. If you find a fix for ivtv don't hesitate to put it here. Known to work: fcpci,fcpcmcia,intel-536ep, nvidia-9x and nvidia-71x thanks greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

5 5

[arch-dev-public] List of public rsyncable mirrors
by Jason Chu 18 Apr '07

18 Apr '07

I've had a couple of people ask now about what rsync servers they should use. I don't remember there being a public list so now I'm asking. Can we create a public list of mirrors people should be syncing from organized by country? Jason

4 5