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

[arch-dev-public] 2007.10 ISO release on saturday 6th october?
by Tobias Powalowski 04 Oct '07

04 Oct '07

Hi i moved in the 0.3 test isos to ftp/iso directory. If no real showstopper is reported till Saturday i would suggest to announce them officially, and remove the other old ISOs from ftp. Your thoughts on it? Announcement on homepage: --- start Hi Arch community, Arch Linux Don't Panic 2007.10 ISO release I changed everything to fit to the new core repository, 2 ISOs left ftp ISO and core ISO. Changelog: GENERAL: - kernel 2.6.22.9 usage - disabled arch_addons hook by default, it is now triggered by arch-addons boot parameter In order to boot and install successfully, the new RAM recommendations: - RAM usage increased to 256 MB (FTP-ISO,CORE-ISO arch boot image) - RAM usage 96 MB (CORE-ISO lowmem boot image) FIXES: - fixed the nasty /dev mount bug - fixed the /dev/ttyS0 errors if no serial port is installed in the system - fixed repositories in install environment to fit to both architectures - fixed km to not show broken chars after exit - fixed grub installing with xfs filesystem - fixed package clearing if setup option was chosen NEW STUFF: - added pptpclient to install environment - added sdparm to install environment - added all free wireless drivers to install environment - added intel wireless drivers to install environment which will be activated by intel-wireless boot parameter - added hosts.deny and hosts.allow to config editing dialog - added licenses to install environment - added new lowmem boot image to core iso stripped everything out that is not necessary for installation As usual check md5sum before using the images and also be aware of the new RAM recommendations the images have. Have fun greetings tpowa --- end have fun in testing and report issues immediatly, thanks greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

11 19

[arch-dev-public] GIT Daemon up on projects.archlinux.org
by Dan McGee 04 Oct '07

04 Oct '07

For all out there that may not be aware, we now have a subdomain at http://projects.archlinux.org where we host some of our internal Arch projects. We have been moving a lot of our projects from other version control systems to GIT as of late, and currently have quite a bunch of these projects hosted, as you can see here: http://projects.archlinux.org/git/ For those interested in helping out with these projects or just following along with the code, we now have a git daemon up and running. All of these projects can still be fetched over http if need be, but using the GIT native protocol is much more efficient. The following two examples should get you started on cloning one of our projects: (Over HTTP) git clone http://projects.archlinux.org/git/namcap.git namcap (Over GIT) git clone git://projects.archlinux.org/pacman.git pacman Note the slight difference in URLs- for cloning over GIT, no /git directory is used. Happy git-cloning, and we'd really like to see some community participation with these projects if you have something to contribute! Patches always welcome on the mailing lists. -Dan

1 0

[arch-dev-public] A big baad idea: ArchCon 2009
by Tom K 03 Oct '07

03 Oct '07

High concept: "What do you think would happen if as many Arch people as possible gathered in the same place at the same time?" Audience breakdown: All members of the dev team (well, duh) TU-selected members of the TU team Other Archers fanatical enough to attend People off the street Program: Hacking Talking Bonding (aww....) Drinking (woohoo!) etc TBC: Continent Country City Venue Menu Activities Restrooms Size of Mugs Imperial or Metric Yadda Yadda etc Teaser: one particular member of the dev team will volunteer to organise the whole shebang! I'm posting this here, because if the devs aren't interested, well... All the best Tom.

13 17

[arch-dev-public] Test Isos 2007.10-0.3 with core repository and 96MB RAM image
by Tobias Powalowski 03 Oct '07

03 Oct '07

Hi here the changelog: i changed everything to fit to new core repository, 2 isos left ftp iso and core iso, the rest was setup/archboot changes to achieve this. - I cleaned up our documentation, to fit to those stuff please read it and tell me what is missing or wrong. GENERAL: - disabled arch_addons hook by default, it is triggered by arch-addons boot parameter - Ram usage increased to 256MB (FTP-ISO,CORE-ISO arch boot image) - Ram usage 96 MB (CORE-ISO lowmem boot image) FIXES: - fixed the nasty /dev mount bug - fixed the /dev/ttyS0 errors if no serial port is installed in the system - fixed repositories in install environment to fit to both architectures - fixed km to not show broken chars after exit - fixed grub installing with xfs filesystem - fixed packages are now cleared if setup option was chosen NEW STUFF: - added pptpclient to install environment - added sdparm to install environment - added all free wireless drivers to install environment - added intel wireless drivers to install environment which will be activated by intel-wireless boot parameter - added hosts.deny and hosts.allow to config dialog - added licenses to install environment - added new lowmem boot image to core iso stripped everything out that is not necessary for installation TODO: - nothing from my side, it's nearly perfect :) you can download i686 Isos here: http://www.archlinux.org/~tpowa/rc-iso/686 you can download x86_64 Isos here: http://www.archlinux.org/~tpowa/rc-iso/x86_64 About memory usage: It's a pacman bug that it increased to 256MB and 96MB so don't blame me on it ;) http://bugs.archlinux.org/task/8155 We should really replace our current Isos with them soon, the old ones are all a bit bugged and ftp is broken on them anyway. so removing old isos from server and place those ones instead is highly recommenden from my side. Your thoughts on it? have fun in testing and report issues immediatly, thanks greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

1 0

[arch-dev-public] namcap status
by Jason Chu 03 Oct '07

03 Oct '07

Since I emailed out about devtools and pacbuild, here's the last email about namcap. Development on namcap is moving along nicely now that I've had help from Jesse Young and JJDaNiMoTh. I only have one thing left on my todo list related to namcap: updated licensepkg code. I want to actually inspect the packages and verify that they have the custom licenses distributed with them that they say they do. After I make that update, I plan on releasing namcap 2.0. Since namcap is hosted on projects now, where should the tarballs go? ftp/other or somewhere else? I don't think anyone's thought about this yet... Jason

3 2

[arch-dev-public] Moving forward [was: Cleanup/Orphans]
by Aaron Griffin 03 Oct '07

03 Oct '07

On 10/2/07, Andreas Radke <a.radke(a)arcor.de> wrote: > Hm. Your words are sounding more polite. True. > > But don't you get the same feeling that some of our developers lost > their interest/time in maintaining packages? Some were even hired to do > other jobs. Who else should do it? We had a decision to not give away > the packaging process to the community. So we have too do it our best. Oh yes, don't get me wrong, I agree with you. But I think _demanding_ the drive back is not the right way to do it. In fact, while you criticized me (us?) for it - I strongly feel that the thread discussing what we do in our free time is _critical_ to us moving forward. See. Here's the thing. This isn't a job. This is a hobby. And a lot of us have started treating it like a job. We're all serious and stoic. Acting like we _must_ do things this way, etc etc. That's not going to cut it. That's the fastest way to defeat if we're not getting any sort of compensation. The compensation is our enjoyment. We should be having fun here. This shouldn't be a chore. It needs to be rewarding. > I just don't want to fall back into the time when Jan, Tobias and me > were doing the majority of packaging almost alone again. And now we have > to take about two architectures. Let's spread it over all our shoulders. See now again, it's important to point out that everyone has other duties here. Writing code is just as time intensive as packaging. And in the end, it's beneficial to _you_ too. If someone improves our packaging tools, streamlines the process, it makes everyone's job easier. > Let's improve our infrastructure step by step but don't forget our > daily work of packaging. We have become famous for our good compromise > of bleading edge and quality. We should try to keep this alive. Everyone has daily work. But I need to emphasize something that I feel is overlooked - pacman, devtools, the web site, gerolde maintenance - these are all AS important. > One possible way it to force a dev to also maintain all dependencies > for his packages. But what about the rest? I actually like this idea, and I will use it to autoassign packages at the end of the week - if you maintain a package and one of the dependencies is an orphan, I'll assign that to you - it just makes sense that way. Thanks Andy!

3 3

[arch-dev-public] Social?
by Aaron Griffin 02 Oct '07

02 Oct '07

Ok ok.... let me preface this a tad. One of the things I think we've lost in arch, is a bit of the good ol' fun we used to have. Maybe it was just me having fun, but hey, I'm not the only one who got excited when skoal came back to the forums. So let's try and have some fun here, I'm sure we all have other things in common besides just Arch, right? This is the land of Web3.9 - there's no sense in me actually TELLING you guys what I like, because I can just paste links.... so here's some: music http://last.fm/user/phrakture movies http://www.netflix.com/Profile?prid=258042279 (sorry this one is most likely US only, as netflix probably doesn't ship overseas yet) random http://twitter.com/phrakture And you all got my previous text related (oops) spam, I'm sure. And there's much much more - for instance I own the entire set of Stargate SG1, Battlestar Galactica, Firefly, Farscape, and am closing in on the full set of Star Trek: TNG. So what about you all? A lot of us know very little about each other. So what do *YOU* do in your free time (besides the copious amounts of beer, heh)?

11 26

[arch-dev-public] pacbuild status
by Jason Chu 02 Oct '07

02 Oct '07

Ok, I missed sending this out last week. I really need to put more time into pacbuild. It has a todo list now of the things I think it needs to be used in production. It's in the git repo, but I'll repost it here. I'll explain some of the points better - Better logging in apple * There have been lots of requests for more logging in general. I'm trying to get the python logging module working with apple and strawberry. - Automatic chroot rebuilding (either triggered by apple or a "no update since" timer) * I wanted to see what Aaron's chroot building code looked like, it's possible I'd want to replace waka with it. - Unionfs * This is all in the chroot building as well. These days my package cache is so big and my free space is so small that unionfs will be the only way I can keep testing. * Simo has a patch or two that started adding unionfs but it needed more testing. Again, I'm waiting on Aaron's mkarchroot. - Dependency handling (know what packages other packages depend on) - Repo contents knowledge - Apple will have to know all the versions of all the packages in all the repos for all the architectures - New status -- inrepo - When a package moves from built to in the repo, we need to know its the one we can access and no others - New status -- depwait - When a package can't be built because another package isn't built yet * These are the meat of the delay. I need to change some of the architecture of pacbuild's db. I learned a lot reading about debian's dbuild. * I may even get rid of the multiple architectures in a single apple db decision. I originally put them all together because I wanted arches to be able to build the same packages, but I eventually realized that the apple daemon isn't the right place for that. - Update pacman python module (because the one with namcap currently sucks) * This one will be easy. I already rewrote the namcap pacman module, now I just have to use the new module when implementing the "Dependency handling" task. There's my pacbuild status. I'm trying to devote a handful of hours to arch development on saturdays when my girlfriend is studying, so I'm hoping to at least move forward on these things soon. Jason

1 0

[arch-dev-public] Problem with X?
by Jason Chu 01 Oct '07

01 Oct '07

I've got this weird problem that I think is caused by X. I've been following testing for a while now (so I have gnome, db, and heimdal). Every so often, and apparently randomly, X will stop taking any input except for mouse movement. But the mouse movement doesn't even trigger the focus follows mouse. The panel will still update and so will windows, but my input just totally doesn't work. The only thing that I can do to fix it seems to be sshing in and killing X. I run xfce4 so it might be the gnome/gtk updates that aren't working well with it... Has anyone heard anything about problems with X or is it just me? Jason

7 8

[arch-dev-public] Status Report 2007-10-01
by Aaron Griffin 01 Oct '07

01 Oct '07

Hey! Second status report. It's like some sort of milestone! I'm going to keep some of the short and long term tasks in here, until we check them off. ----------------- ArchLinux Status Report, 2007-10-01 == Newsworthy Items == * Some "interesting" front page news. http://archlinux.org/news/350/ It kinda *ahem* speaks for itself. * Damir completed his Master's program I just wanted to send out a public congratulations, here. I've always thought of Damir as "the biology student", but I guess I can't do that anymore. Hooray! == Completed Tasks == * db and heimdal rebuilds These so renames were moved to testing over the weekend. Thanks a lot Andy and anyone else who participated. Relevant forum thread: http://bbs.archlinux.org/viewtopic.php?id=37984 == Pending Tasks, Short Term == * New Round of Package Cleanup Let's try and get this "complete" this week. I'd like to get at least 2 or 3 of us together with Eric to go through these packages and start moving them to community or unsupported. We have an internal list for this here: https://www.archlinux.org/wiki/Repo%20Cleanup/ Please add candidates if you find them. Eric, when is a good time for you? * DVD and Additional Package ISO Lists Previous discussion has pushed us toward a solution, but we need to sit down and define what packages we explicitly want (or, rather, _don't_ want) on these images - that is, * Unified chroot build tools I failed here. Deadlines aren't my strong point. Time to redouble my efforts to get you all some fun chroot building tools! * Use vendor_perl for pacman perl packages We weren't able to get to this last week. If anyone has some free time, I'd appreciate you taking a look at this. If not, I will get to it myself closer to the end of the week. This is an easy bug to fix, it's just tedious. http://bugs.archlinux.org/task/8082 Any takers? Jan, you brought up concern over our perl policy earlier, are you up to the task? * Move all Arch related projects to gerolde Yet another ping here. We're still missing one or two projects which are important - archboot, some of our internal scripts, etc. http://bugs.archlinux.org/task/7789 * Next ISO Release Date We're currently at testing release 0.2 of our next iso. Please test it out, for all of those interested. Tobias, can you approximate a date of release for all of us interested? http://archlinux.org/pipermail/arch-dev-public/2007-September/001849.html * DB Script Rewrite Yup, this one still needs to be done. It's not critical, as we're in one of those not-broke-won't-fix stages. * Devtools updates See this thread: http://archlinux.org/pipermail/arch-dev-public/2007-September/001883.html There are a few complaints with devtools I want to address shortly. If you have any other pending issues, let me know, and I will see what I can do. == Pending Tasks, Long Term == * Pacman 3.1 Release We have a decent amount of issues to be closed in the 3.1 release. Please take a look and see if you have any input. http://bugs.archlinux.org/task/8109 Sadly, my time is (heh) fractured into many different things now, but one of these days Dan and I are gonna sit down and bang out a large chunk of these. * Official pacbuild usage Jason, could we get a "heads up" here - just some sort of direction for people who would be interested * 'Continuous Integration' setup / machine Since the last status report, I got two offers for hardware to run a CI machine, which is great. Volunteers always make us over on this side of the fence happy. Maybe when I get time to breathe, I'll bang out a prelim script... a man can dream, right? * Multiple Maintainers on the Dashboard * Multiple Architectures on the Dashboard Damir lumped these two together and called it "modernizing" our dashboard - which I like. I guess, what we really need, is more people with "their hands in the code". Any volunteers? Who wants to learn Django? * Architecture Independent Repos Relevant thread: http://archlinux.org/pipermail/arch-dev-public/2007-September/001829.html This was discussed and we all seem to agree that it is a good idea to maintain the packages which aren't specific to any one architecture in only one repo, rather than maintaining 2 packages. Still, this needs some coordinated changes to scripts and pacman and the like - fairly minor stuff, but perhaps we can sneak it in in the 3.1 pacman release. * ArchCon 2009: Big Baaad Idea Yep, I'm still riding this one. A big ol' ArchCon would be fun. We're all in totally different parts of the world, so we never get to see each other. http://archlinux.org/pipermail/arch-dev-public/2007-September/001614.html == Bugs and Issues == * X input lockups This relates to the Xorg in testing, and may be XFCE related, but it appears important enough to mention here: http://archlinux.org/pipermail/arch-dev-public/2007-October/001899.html ----------------- So there we go. Status report numero dos down. Lots of this is copied from the last one, and see, that's on purpose. This list will keep growing and growing until we start closing out some of these issues. Thanks for your continued work, guys. -- Aaron

1 0