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

[arch-dev-public] [draft] QT-4 and QT3 moved to [extra]
by Pierre Schmitz 20 Jan '08

20 Jan '08

As announced last year* and after a longer period of testing, QT in version 4 and 3 was moved to [extra]. At least until the final release of KDE4 there are plenty of packages which still use version 3 of QT. Therefore a new package called qt3 was introduced. The dependencies of all packages are updated according to this change. The update should be quite smooth. Pacman only notfies about replacing qt by qt3 and qt4 by qt. If you don't want to have qt-4 installed just remove it with "pacman -Rc qt" after the update. If you are using any third party repositories like KDEmod please wait until they have updated their packages, too. Do not force any updates! If there are still any issues, please report them at http://bugs.archlinux.org. *) http://archlinux.org/pipermail/arch-dev-public/2007-November/002910.html -- http://www.archlinux.de

3 4

[arch-dev-public] [draft] QT-4 and QT3 moved to [extra]
by Pierre Schmitz 20 Jan '08

20 Jan '08

As announced last year* and after a longer period of testing, QT versions 3 and 4 have now been moved to [extra]. At least until the final release of KDE4 there are plenty of packages which still use version 3 of QT. Therefore a new package called qt3 was introduced. The dependencies of all packages are updated according to this change. The update should be quite smooth. Pacman only notifies about replacing qt by qt3 and qt4 by qt. If you don't want to have QT version 4 installed just remove it with "pacman -Rc qt" after the update. If you are using any third party repositories like KDEmod please wait until they have updated their packages, too. Do not force any updates! If there are still any issues, please report them at http://bugs.archlinux.org. Community packages may not be updated with the new versioning scheme of QT, so give your TUs some time to make the required changes. *) http://archlinux.org/pipermail/arch-dev-public/2007-November/002910.html -- http://www.archlinux.de

1 0

[arch-dev-public] [signoff] wpa_supplicant
by Pierre Schmitz 20 Jan '08

20 Jan '08

Hi, it seems I have missed the fact that wpa_supplicant_gui I moved from testing to extra forces wpa_supplicant to be moved from testing to core, too. So please signoff to fix this issue. I have tested it on i686. -- http://www.archlinux.de

3 4

[arch-dev-public] [signoff] e2fsprogs 1.40.4-1
by Tom K 19 Jan '08

19 Jan '08

Hi all. In testing now, for both arches. Release notes: http://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.40.4 T.

3 2

[arch-dev-public] [signoff] vi, vim and gvim 7.1.228 for both architectures
by Tobias Kieslich 18 Jan '08

18 Jan '08

Hi, please sign at least vi off for both architectures. Thank you eric for building it for x64. -T

5 7

[arch-dev-public] Away for weekend
by Travis Willard 18 Jan '08

18 Jan '08

I'll be out of touch this weekend, until sometime Monday. Have a good one fellas!

1 0

[arch-dev-public] build transmission for i686
by Varun Acharya 18 Jan '08

18 Jan '08

Hi guys, Would appreciate if someone builds transmission-1.01 for i686 for me, because my Virtualbox install is kernel panicking and I don't have time for a few days to figure it out. Simple pkgbump, nothing funky.(x86_64 is done).Hey tpowa, andy tells me you have the day off ; ) ;) Thanks, Varun

3 2

[arch-dev-public] [Fwd: New nvidia legacy package needed]
by Thomas Bächler 18 Jan '08

18 Jan '08

I just received this E-Mail from a user. This needs, instead of 2, we now need 3 nvidia legacy packages for i686. Can anyone find a source for this? -------- Original-Nachricht -------- Betreff: New nvidia legacy package needed Datum: Fri, 18 Jan 2008 01:57:39 +0100 Von: Andrea Cimitan <andrea.cimitan(a)gmail.com> An: thomas(a)archlinux.org I've just pointed out that 100.14.xx will be the latest nvidia drivers to support non-SSE cpu (so like Athlon Thunderbird, Classic, AMD Duron, Pentium III, etc etc). http://www.nvnews.net/vbulletin/showpost.php?p=1522860&postcount=10 This is why the driver in testing (169.07) is making my pc crash/freeze :) (it is nvidia fault not yours...) So a new -legacy driver is needed before killing PCs with 167.xx drivers series :D Regards

2 1

[arch-dev-public] Versioned Provisions
by Aaron Griffin 18 Jan '08

18 Jan '08

This is a little "heads up" email to all the package maintainers out there. Pacman 3.1 has support for versioned provisions. But what this also means is that there's going to be some breakages in packages. Let me explain by way of example: package foo depends=(bar>=1.2) package omg provides=(bar) In the past, you could install both foo and omg at the same time and everything would be satisfied. Not now. Now, the provision of "omg" will fail, because it's not providing the right version. What does this mean? Well, a few things. First and foremost, versioned provisions are a little broken in 3.1.0, but 3.1.1 will fix all this py allowing you to say: provides=(bar=1.2) Did I get this right? Dan, Xavier?

4 7

Re: [arch-dev-public] reimplementation of the new design (Pierre Schmitz)
by thayer 17 Jan '08

17 Jan '08

On Jan 17, 2008 9:00 AM PST, Pierre Schmitz <pierre(a)archlinux.de> wrote: > Hi all, > > the last few days I have been working on implementation of the new design for > archlinux.de. This might be interesting for some of you; especially for those > who maintain other arch sites. > > I have simplified the css and html code. There were some strange and useless > parts (like the background image to draw those two bars at the top) Good job, I know it needs it. I am not going to worry about this for now, because there are "changes in the works" that may make this irrelevant. > I have modified the logo: I removed the hard to read TM (isn't this useless > anyway) and change the font from liberation to dejavu because of hinting > errors. Furthermore I used Gimp instead of Inkscape to create the png which > results in a much sharper output. Finally I used optipng to make all pngs > smaller. :-) I will stay clear of the trademark debate, but with respect to the sub-text under the logo, this is simply a matter of preference. The old logo did not use antialiasing, while the new one does. Some may argue that means the new logo is broken--I disagree. Most professional logos use antialiased fonts for text. I agree that Inkscape's font rendering isn't the best, but personally I don't care for the ultra-crisp version at the DE site either, but to each their own. > I created the MediaWiki theme from scratch. Its based on the monobook theme > but I left the original css files untouched. Instead I wrote a new > archlinux.css which just overrides some box positions and colours to our > needs. This should make upstream updates much easier. In the past some > updates were a lot of work because of many changes to the css code. And of > course: Its much easier to maintain only the changes in a separate file. The work you did on the wiki looks great...if I could offer one suggestion it would be to make sure the links are not the same colour as the headings. > I have changed some colours compared to the theme from archlinux.org (grey > boxes on the start page and using grey and blue for the wiki) Overall, I think you have some great ideas about separating the styles from the upstream content/themes--we plan to do the same for the official site. The current state of the official site is definitely in transition--we mainly want to get the new logo into circulation at this point. The 'refinement' is coming... I think a LOT of css (and even some semantic markup) can be removed from the official Arch sites, but I just came on board and until we have a clear vision as to what we're going to accomplish, I don't want waste what precious the other web devs have. Kudos for doing such a good job on the DE site!

3 2