headers
甘露 | 1 Nov 2004 02:49
Picon

Re:new kdebase and kdelibs in testing repo, please test it

>Added an Arch Menu in K-Menu for quicklinks on Arch services on Homepage
I do like it, but how about gnome? Does that work to only write some archlinux.desktop files? Anyway we need
such a functional package.

-----原始邮件-----
发件人: arch-admin <at> archlinux.org [mailto:arch-admin <at> archlinux.org]代表
Tobias Powalowski
发送时间: 2004年10月31日 15:52
收件人: arch <at> archlinux.org
主题: [arch] new kdebase and kdelibs in testing repo, please test it

hi
i uploaded these two packages to testing and here are the new features:

Added Arch Artwork to kde:
new default background
new default logout picture
new kdm look

Added new Defaults:
new kdm defaults
new Fonts setup 
(changed ugly helvetica to Bitstream Vera and antialiasing is enabled by 
default)
Cups is now default printing system

Finally:
Added an Arch Menu in K-Menu for quicklinks on Arch services on Homepage

If you get problems while installing:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tomasz Bakiera | 1 Nov 2004 10:07
Picon
Favicon

Re: kde-i18n-pl

> ||  ||  > I installed kde-i18n-pl-3.3.1 and I didn't saw polish characters
> ||  ||  > correctly most of them are showing as squares.
> ||  ||  > Polish chracter set is ISO-8859-2, I got this fonts (gnome and
> ||  ||  > xfce works good with polish menu). Locale set to polish too.
> ||  ||  > I think it is a bad character codepage in KDE. But I don't know
> ||  ||  > how to change it to ISO-8859-2. Does anybody know where is
> ||  ||  > coresponding config file ?
> ||  ||  I think the problem is that default fonts in KDE are Bitstream
> ||  || (AFAIR). Try setting to another font and check then.
> ||  ||  These (Bitstream) does not include polish chars. Try search for
> ||  || Hunky Fonts in Google. They're Bitstream fonts with polish chars.
> It ( dejavu ) is now availably in my repo:
> [verwilst]
> Server=http://arch.verwilst.be
> ( in /etc/pacman.conf )
> then pacman -S dejavu-fonts

Thanks, it works. The worst thing is I need to start every program
and change default fonts :-(

I submit a bug.

http://bugs.archlinux.org/index.php?do=details&id=1711

BTW. Please do not use "topposting". If lot of persons will ansfer for
message it will look unreadable.

> I would like to have my repo into the TUR's... Would that be possible?
It will be good, but you must ask Judd for this (I think)
(Continue reading)

Permalink | Reply | 0 comments |
headers
RedShift | 1 Nov 2004 10:12
Picon

Re: 0.7-beta2 ISO Released

Judd Vinet wrote:
> There's a beta2 iso up on the servers now, new n' improved with a 2.6.9
> kernel and a couple small fixes. If nothing explodes, the beta2 iso will
> likely graduate to 0.7-final.
> 
> - J

Where is the changelog? What about Release Candidates? :-D
Permalink | Reply | 0 comments |
headers
Aaron Griffin | 1 Nov 2004 16:21
Picon

Re: Wireless support in init scripts

On Sun, 31 Oct 2004 13:41:05 -0600, Michael Baehr <mbaehr <at> gmail.com> wrote:
> On Sun, 31 Oct 2004 12:45:06 -0600, Aaron Griffin
> 
> 
> <aaronmgriffin <at> gmail.com> wrote:
> > Check the wiki here: http://wiki.archlinux.org/index.php/Wireless%20setup
> > I have made wireless init scripts already.  The difference is this:
> > In order for changes to be made to the main network scripts which
> > include wireless, it requires at least iwconfig (part of the
> > wireless_tools package) - therefore everyone running arch is now
> > required to have the wireless_tools package, even if they dont have
> > wireless.
> >
> > In addition, common wireless usage uses the same interface with
> > different ESSIDs (home/school/starbucks/whatever).  The scripts I have
> > created use the concept of profiles (thanks BoomN) - you make one
> > profile for home, another for school.  In rc.conf you can add a
> > WIRELESS_PROFILES array, or simply call /etc/rc.d/wireless profile
> > home to start wireless.
> > Profiles are named, so as to make it more clear as to what's going on.
> >  In addition, this makes switching from the home to school network
> > much easier.  Take your laptop to starbucks under a non-profile based
> > script and you have to change config files, switch the ESSID, and then
> > restart the network script, which most likely contains eth0 as well
> > and sits there and hangs for a bit until it realizes that theres no
> > cable plugged in.
> >
> >
> 
> I like your scripts, but I think they require way too many values to
(Continue reading)

Permalink | Reply | 0 comments |
headers
Essien Ita Essien | 1 Nov 2004 17:32

makepkg -T (distilling packages from installed packages or making packages from already installed packages)


Hi guys... now this is a very interesting one.

I have this patch to Makepkg, that allows you to create a package from
an already installed package. 

I also have attached a screenshot of makepkg -T in action. Note the
first makepkg command was the unpatched one in /usr/bin/makepkg, the
second one, is the patched one, in the current directory.

Huh?

Okay... One weekend, i was broke, and couldn't go to a cyber cafe to
browse and get packages. I had cleared my /var/cache/packman/pkg and i
needed mawk,  and some other package to work on creating an ALE target
for colinux (umm... ALE is not dead, just reallly dragging b/cos of
work :( )

I wanted to pull out my hair when i discovered that i knew almost all
Pacman did, and how it worked, and i had Mawk already installed on my
system. So theoritcally, i could create the mawk-X.Y-Z.pkg.tar.gz from
the current installation using a series of (suprise suprise!!) pacman
-Ql and pacman -Qi

So off i went and I got a nice package. My only problem is that some
information, is not ALWAYS included or available from pacman -Qi

Check the ISSUES attachment for some issues i have (ummm... Judd, could
you implement the second point? :) )
(Continue reading)

Permalink | Reply | 10 comments |
headers
Essien Ita Essien | 1 Nov 2004 17:51

Re: makepkg -T (distilling packages from installed packages or making packages from already installed packages)

Oops.. forgot the attachments. Here they are now :)

On Mon, 2004-11-01 at 17:32 +0100, Essien Ita Essien wrote:
> 
> Hi guys... now this is a very interesting one.
> 
> I have this patch to Makepkg, that allows you to create a package from
> an already installed package. 
> 
> I also have attached a screenshot of makepkg -T in action. Note the
> first makepkg command was the unpatched one in /usr/bin/makepkg, the
> second one, is the patched one, in the current directory.
> 
> Huh?
> 
> Okay... One weekend, i was broke, and couldn't go to a cyber cafe to
> browse and get packages. I had cleared my /var/cache/packman/pkg and i
> needed mawk,  and some other package to work on creating an ALE target
> for colinux (umm... ALE is not dead, just reallly dragging b/cos of
> work :( )
> 
> I wanted to pull out my hair when i discovered that i knew almost all
> Pacman did, and how it worked, and i had Mawk already installed on my
> system. So theoritcally, i could create the mawk-X.Y-Z.pkg.tar.gz from
> the current installation using a series of (suprise suprise!!) pacman
> -Ql and pacman -Qi
> 
> So off i went and I got a nice package. My only problem is that some
> information, is not ALWAYS included or available from pacman -Qi
>
(Continue reading)

Permalink | Reply | 7 comments |
headers
Jason Chu | 1 Nov 2004 18:15

Re: Re: makepkg -T (distilling packages from installed packages or making packages from already installed packages)

> -Presently when distilling, the patch doesn't warn you of already existing packages with the same name.
> -The following information is not stored in the database.
> 	1. backup
> 	2. replaces
> 
> I suggest that pacman make this information available so it can be easily gleaned when needed.

Backup is stored in the database... within the files file.

Jason

--

-- 
If you understand, things are just as they are.  If you do not understand,
things are just as they are.

My old gpg key expired, the new one is available from keyservers.  I was
stupid enough not to realize this before it was too late, so I am not
able to sign my new key with my old key.  If this assurance isn't enough,
please contact me.
Permalink | Reply | 6 comments |
headers
Judd Vinet | 1 Nov 2004 19:20

We love DistroWatch

Our humble thanks to DistroWatch.com and LinuxCD.org, who have just
donated $300 to Arch Linux.

As with most open source projects, running costs for servers can eat up
a lot of cash, which primarily flows from the developers' pockets or
their rich ancestors'. Extra money from donations ensures that we can
continue to feed all you bandwidth-hungry --sysupgrade'ers and new
users.

Big thanks to Ladislav Bodnar and the crew at DW and LinuxCD, as well as
all the people that voted us as a worthy project. Your support is
appreciated.

- J
Permalink | Reply | 0 comments |
headers
Essien Ita Essien | 1 Nov 2004 19:55

Re: Re: makepkg -T (distilling packages from installed packages or making packages from already installed packages)

Hmm... interesting... i'm guessing it will be in one
of /var/lib/$repository/$packagename/{desc,depends}

Which one is it really?

Could someone also point me to a package that actually uses backup=

so i can use this to test.

Thnx

On Mon, 2004-11-01 at 09:15 -0800, Jason Chu wrote:
> > -Presently when distilling, the patch doesn't warn you of already existing packages with the same name.
> > -The following information is not stored in the database.
> > 	1. backup
> > 	2. replaces
> > 
> > I suggest that pacman make this information available so it can be easily gleaned when needed.
> 
> Backup is stored in the database... within the files file.
> 
> Jason
> 
--

-- 
Essien Ita Essien <essiene <at> datavibe.net>
Permalink | Reply | 0 comments |
headers
Judd Vinet | 1 Nov 2004 19:56

Re: Re: makepkg -T (distilling packages from installed packages or making packages from already installed packages)

On Mon, Nov 01, 2004 at 09:15:21AM -0800, Jason Chu wrote:
> Backup is stored in the database... within the files file.

Yep, you can see them if you use -Qii instead of -Qi

As for the no-replaces issue, that's because replaces only makes sense
in the sync databases, not your local one.  But it wouldn't hurt
anything (besides adding some size to the local db) to have replaces
stored there.

Your patch is somewhat related to a transaction/rollback system that is
in the "eventually" list for pacman.  With a little more hacking, you
could wrap transaction support around pacman.

Something like...

1. build a backup package from the existing package installation (makepkg -T)
2. pacman -U newpkg
3. if $? != 0 then pacman -U oldpkg and echo "it broke! rolling back"

I'll think about adding replaces to the local db, but it may be a while.
Pacman isn't getting any attention til 0.7 goes out, and there are a few
changes I want to poke at before that happens.

- wireless scripts
- some other rc.d/network additions
- 2.6.10/reiser4

Speaking of which, can anyone confirm that reiser4 will be in 2.6.10?
If it is, then I'll wait on 0.7 til it's released.  Otherwise, I see no
(Continue reading)

Permalink | Reply | 4 comments |

Gmane