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

[arch-dev-public] Tool tarball location
by Aaron Griffin 08 Oct '07

08 Oct '07

On 10/2/07, Jason Chu <jason(a)archlinux.org> wrote: > 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... Yeah, let's use ftp/other/<toolname>/ for all our official stuff like pacman, devtools, etc etc.

10 18

[arch-dev-public] Find-deps script (was: hidden dependencies)
by Travis Willard 07 Oct '07

07 Oct '07

> This is what I use for checking the deps: > > [andyrtr@workstation64 cvs]$ grep -l libpcap `find . -name PKGBUILD` A while ago I posted a script to this ML that does this, but gives more concise output, finding _only_ deps and makedeps, and not random comments and such. Jurgen reworked it a bit for speed and because his bash is leet. I've reattached it here - I suggest you use it. -- Travis

4 6

[arch-dev-public] Testing policy
by Aaron Griffin 07 Oct '07

07 Oct '07

Time for the "big hat" We had some oopses today. Problems that were brought up less than 3 months ago, which reoccurred. In the past, Judd had a problem with saying that every package needs to go to testing. I don't. Going forward, every single [core] package MUST go to testing, and MUST be OKed by at least one other developer. The term here is "independent verification" - we want someone else, that is not you, to tell you this works. While we have no formal tools in place for this, eventually I'd like to have a way to "sign off" that a package in testing works. Just to clarify: This is not a request. This is not a discussion. The core repository is critical to ArchLinux systems and should never be broken like this. All core packages MUST go to testing and MUST be verified by another developer. Feel free to do this on the ML, or on IRC - just somewhere where we can look back on the logs if there are issues. -- Aaron

2 2

Re: [arch-dev-public] [arch-commits] CVS update of core/base/libpcap (PKGBUILD)
by Jan de Groot 07 Oct '07

07 Oct '07

On Sun, 2007-10-07 at 07:42 -0400, Thomas Baechler wrote: > Date: Sunday, October 7, 2007 @ 07:42:13 > Author: thomas > Path: /home/cvs-core/core/base/libpcap > > +# This package has a strict SONAME that changes in EVERY MINOR > +# release. Whenever you feel like updating this package, DON'T, > +# it will break a number of essential system tools. > +# Again, for dummies: IF YOU UPDATE THIS PACKAGE DIRECTLY TO CORE, > +# I WILL PERSONALLY CHOP YOUR HEAD OFF! Morning Mr Head Chopper... I looked at this package yesterday, it seems something is plain wrong with the soname versioning. I took a look at the debian package, where we retrieved the shared library patch from 2 years ago (yes, libpcap was one of the first packages I changed when I had current access). It seems they keep track whether a release is API/ABI stable and keep the soname the same. FYI: They have libpcap.so.0.9.8 and libpcap.so.0.8, as the 0.9.x versions share the same ABI as the 0.8 versions. They update their patches to keep things working. I'm thinking about two solutions here: - Make sure apps stop linking against the .so.0.9.x library, apps should link to the normal soname that doesn't change on minor version bumps - remove the patch completely and continue to use the static library as the libpcap project does upstream Solution 1 looks hard, but all it takes is updating the shared lib patch and adjust it to not look at the debian changelog to generate its sonames.

2 1

[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