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

[arch-dev-public] Corrupted DBs
by Aaron Griffin 07 Oct '07

07 Oct '07

http://bugs.archlinux.org/task/8241 It appears some packages built for x86_64 were pushed to the i686 repos. I've manually fixed what I could. Please let me know if any more crop up, and please be more careful in the future. This is the exact reason I'd prefer automated tools for this process - to prevent human error. The following packages were affected: ngrep ntop ssldump tcptraceroute

2 2

[arch-dev-public] AUR New Package Notify -- unsubscribe
by James Rayner 07 Oct '07

07 Oct '07

Hey, Unsubscribed from the AUR New Package notification yesterday, but I still got it today. Double checked, and it's unsubscribed on the aur frontend, anyone able to fix this? Address is the one on this mail. Thanks, James

3 4

[arch-dev-public] Cleanup / Orphans - the list
by Andreas Radke 07 Oct '07

07 Oct '07

I've started to workout our internal list for possible cleanups. https://www.archlinux.org/wiki/Repo%20Cleanup/ I've taken packages form the public wiki cleanup list and then many not that important packages from our dashboard marked with "orphaned". We still have to expand the list to have each pkg listed we want to remove. If you want to keep a pkg in our repos hurry up to adopt it. On the other side we have packages nobody wants for various reasons but we essentially need, e.g. apache and all packages from core repo. Make sure you adopt also some of these *unwanted* packages. We can still work all together maintaining/improving/updating them. We have to review the remaining packages in the cleanup list for packages beeing a dependency or beeing essential for some reason. Everything else will soon be removed completly from the extra repo. TUs and users might pick them up later again for community repo/AUR. I think one week should be enough from now on to sort things out. We will see if we need more time. Keep in mind that our goal is to _clean up_ the extra repo now! So better orphan more packages that are not very important(games, science, multimedia, packages where we have alternatives, ...) and adopt some essential packages! Andy

5 5

[arch-dev-public] adopted more stuff
by Varun Acharya 06 Oct '07

06 Oct '07

also adopted 'd4x' & 'firestarter' Varun

1 0

[arch-dev-public] firestarter
by Varun Acharya 06 Oct '07

06 Oct '07

I've adopted firestarter, let me know if you have objections. Also, I build only for x86_64, so I presume I have to alert a dev to update for i686 correct? Thanks, Varun

1 0

[arch-dev-public] Cleanup/Orphans - a BIG warning!
by Andreas Radke 06 Oct '07

06 Oct '07

Am Mon, 1 Oct 2007 17:17:17 -0500 schrieb "Aaron Griffin" <aaronmgriffin(a)gmail.com>: > == 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? I will help out with the cleanup. We had asked all developers to readopt their packages after the repo shuffle. We have a very bad situation right now! Still 916 packages orphaned. 6 developers listed on the dev website have 0 packages. Some other maintain only a few packages. Look what is orphaned: apache, bind, cvs, mono, python, freetype1/2, nspr/nss, pango, gimp, mutt, cdrkit, several desktops, bash, bzip2, gcc-libs, kernel26 and many more! We were talking about our intention to have more than one maintainer per package. But we do not act like that. Having so important packages unmaintained means nobody follows the projects mailing lists. No quick updates, bug fixes, no security fixes... So get your ass up and adopt packages you want to keep in our distribution! DEADLINE for adopting packages should be this coming weekend. Then the cleanup will start. 2 all devs: Isn't that more important than telling something about how much alcohol we drink? -Andy

6 9

[arch-dev-public] back after long break
by Varun Acharya 05 Oct '07

05 Oct '07

Hi devs, The mammoth event which I was busy with is finally over, and it turned out to be a huge success. Will get back to arch work in a few days. I've been following the ML regularly, but forgive me if I ask a stupid question once in a while. Its good to be back :) Varun

3 3

[arch-dev-public] pending devtools issues
by Andreas Radke 04 Oct '07

04 Oct '07

Whenever I had tried out the devtools I had these issues: - I always set a certain pkgdest in makepkg.conf. So (old and) new packages are stored centralized. This breaks checkpkg and {foo-repo}pkg as they expect old and new pkg in the current directory. Correct me if I missed any option to solve that. - As I only have poor bandwidth and like to keep working while down-/uploading I want to have a bandwidth-limit option for filetransfer. At least for uploading. Afaik the scripts use scp. Man scp tells me there's -l limit - Limits the used bandwidth, specified in Kbit/s. Yes I like the idea to "force" all devs using devtools to reduce unneeded mistakes and issues. Forcing us with an integrated namcap run is something I would like to see. But we should still be able to do everything by hand. There always might appear some reason why the tools get broken and we need to fix something manually. Andy

7 31

[arch-dev-public] archlinux water
by Damir Perisa 04 Oct '07

04 Oct '07

just got a nice picture remembering me on archlinux: http://lux.perisa.ch/tmp/ img_6366_uxga.jpg enjoy! if i'm running over similar pictures and have enough, i'm considering making a arch gallery :) - D -- .·´¯`·.¸.·´¯`·.¸¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸¸.·´ ° ° ° ° ° ° ><((((º> ° ° ° ° ° <º)))>< <º)))><

3 4

[arch-dev-public] critical: fakeroot broken again, breaks makepkg
by Thomas Bächler 04 Oct '07

04 Oct '07

Oops, this should have gone to the public list directly, so I'll repost it here: I saw this problem a while ago already, but didn't really investigate it. When building a package, you would often end up with non-world-readable /usr/man/manX directories. This happens whenever this code in makepkg is executed: # move /usr/share/man files to /usr/man if [ -d $startdir/pkg/usr/share/man ]; then cd "$startdir" mkdir -p pkg/usr/man cp -a pkg/usr/share/man/* pkg/usr/man/ rm -rf pkg/usr/share/man fi This can be reproduced easily: [09:29:39][thomas@artin shm]$ fakeroot bash-3.2# mkdir -p foo/ab bar bash-3.2# ls -al foo/ bar/ bar/: total 0 drwxr-xr-x 2 root root 40 Jul 12 09:29 . drwxrwxrwt 4 root root 100 Jul 12 09:29 .. foo/: total 0 drwxr-xr-x 3 root root 60 Jul 12 09:29 . drwxrwxrwt 4 root root 100 Jul 12 09:29 .. drwxr-xr-x 2 root root 40 Jul 12 09:29 ab bash-3.2# cp -a foo/* bar/ bash-3.2# ls -al foo/ bar/ bar/: total 0 drwxr-xr-x 3 root root 60 Jul 12 09:29 . drwxrwxrwt 4 root root 100 Jul 12 09:29 .. drwx------ 2 root root 40 Jul 12 09:29 ab foo/: total 0 drwxr-xr-x 3 root root 60 Jul 12 09:29 . drwxrwxrwt 4 root root 100 Jul 12 09:29 .. drwxr-xr-x 2 root root 40 Jul 12 09:29 ab bash-3.2# I can't find out exactly what's causing this, so if anyone has an idea, feel free to share it. This should definitely be fixed quickly, as it prevents me from updating several packages.

4 6