From crux at morpheus.net  Thu Dec  1 19:27:08 2005
From: crux at morpheus.net (crux at morpheus.net)
Date: Thu,  1 Dec 2005 13:27:08 -0600
Subject: [clc-devel] [CLC Ticket Notification] contrib/rxvt-unicode update (5.7 -> 5.8)
Message-ID: <20051201192715.5C252173F9@dream.morpheus.net>

Assigned to [clc-devel at lists.berlios.de]

The following CLC ticket (101) has been created or modified:

Description:

download location for v5.7 is no longer correct

Remarks:



Contact: quuuux at googlemail dot com
CLC User: anonymous
Status: new

URL:
	http://clc.morpheus.net:6999/clc/tktview?tn=101



From crux at morpheus.net  Thu Dec  1 21:53:41 2005
From: crux at morpheus.net (crux at morpheus.net)
Date: Thu,  1 Dec 2005 15:53:41 -0600
Subject: [clc-devel] [CLC Ticket Notification] contrib/rxvt-unicode update (5.7 -> 5.8)
Message-ID: <20051201215343.F3982152F0@dream.morpheus.net>

Assigned to [clc-devel at lists.berlios.de]

The following CLC ticket (101) has been created or modified:

Description:

download location for v5.7 is no longer correct

Remarks:

Fixed, thanks

Contact: quuuux at googlemail dot com
CLC User: tilman
Status: fixed

URL:
	http://clc.morpheus.net:6999/clc/tktview?tn=101



From jw at tks6.net  Fri Dec  2 08:24:49 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Fri, 2 Dec 2005 09:24:49 +0100 (CET)
Subject: [clc-devel] Mailing list usage guideline
Message-ID: <18016.193.5.216.100.1133511889.squirrel@hyoid.unibe.ch>

Hi,

There seems to be an increasing number of users who are new to mailing
lists and make the typical errors like top posting [1], including a full
copy of the  original message without relating to the content [2], or
including e-mail addresses in the attribution line(s) [1] which then
appear unobfuscated in web archives.

In order to make the mailing list more pleasant, I've started a 'usage
guideline' section on
  http://crux.nu/cgi-bin/trac.cgi/wiki/MailingLists

Feel free to question and of those "rules", but let's write it down to
make sure it's visible. I also think we should consider writing a similar
document for IRC.

Kind regards, Johannes

References:
  1 http://marc.theaimsgroup.com/?l=crux&m=113350973921921&w=2
  2 http://marc.theaimsgroup.com/?l=crux&m=113327551604693&w=2



From jjasghar at gmail.com  Fri Dec  2 14:30:57 2005
From: jjasghar at gmail.com (Jonathan Asghar)
Date: Fri, 2 Dec 2005 08:30:57 -0600
Subject: [clc-devel] Mailing list usage guideline
In-Reply-To: <18016.193.5.216.100.1133511889.squirrel@hyoid.unibe.ch>
References: <18016.193.5.216.100.1133511889.squirrel@hyoid.unibe.ch>
Message-ID: <57680e350512020630l4acd5254xd3b53c13ac5d3f76@mail.gmail.com>

commie bastards! It's like that guy stew. i want to shove a fork in his eye.

i need a girl...badly.

btw, good call Johannes hopefully people will take it seriously.

Regards,
-j

On 12/2/05, Johannes Winkelmann <jw at tks6.net> wrote:
>
> Hi,
>
> There seems to be an increasing number of users who are new to mailing
> lists and make the typical errors like top posting [1], including a full
> copy of the  original message without relating to the content [2], or
> including e-mail addresses in the attribution line(s) [1] which then
> appear unobfuscated in web archives.
>
> In order to make the mailing list more pleasant, I've started a 'usage
> guideline' section on
>   http://crux.nu/cgi-bin/trac.cgi/wiki/MailingLists
>
> Feel free to question and of those "rules", but let's write it down to
> make sure it's visible. I also think we should consider writing a similar
> document for IRC.
>
> Kind regards, Johannes
>
> References:
>   1 http://marc.theaimsgroup.com/?l=crux&m=113350973921921&w=2
>   2 http://marc.theaimsgroup.com/?l=crux&m=113327551604693&w=2
>
> _______________________________________________
> clc-devel mailing list
> clc-devel at lists.berlios.de
> http://lists.berlios.de/mailman/listinfo/clc-devel
>



--
Jonathan Asghar
phone: 512.619.0722
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20051202/27eb5a04/attachment.html>

From jjasghar at gmail.com  Fri Dec  2 14:34:09 2005
From: jjasghar at gmail.com (Jonathan Asghar)
Date: Fri, 2 Dec 2005 08:34:09 -0600
Subject: [clc-devel] Mailing list usage guideline
In-Reply-To: <57680e350512020630l4acd5254xd3b53c13ac5d3f76@mail.gmail.com>
References: <18016.193.5.216.100.1133511889.squirrel@hyoid.unibe.ch>
	 <57680e350512020630l4acd5254xd3b53c13ac5d3f76@mail.gmail.com>
Message-ID: <57680e350512020634i584faa85y922393fa5fb5c1d0@mail.gmail.com>

...i know i'm breaking a rule here... but something we should keep in mind
about the top posting, gmail doesnt let you not do it.  It's designed that
way unless you erase the whole email.

just and fyi.

-j

On 12/2/05, Jonathan Asghar <jjasghar at gmail.com> wrote:
>
> commie bastards! It's like that guy stew. i want to shove a fork in his
> eye.
>
> i need a girl...badly.
>
> btw, good call Johannes hopefully people will take it seriously.
>
> Regards,
> -j
>
> On 12/2/05, Johannes Winkelmann <jw at tks6.net> wrote:
> >
> > Hi,
> >
> > There seems to be an increasing number of users who are new to mailing
> > lists and make the typical errors like top posting [1], including a full
> > copy of the  original message without relating to the content [2], or
> > including e-mail addresses in the attribution line(s) [1] which then
> > appear unobfuscated in web archives.
> >
> > In order to make the mailing list more pleasant, I've started a 'usage
> > guideline' section on
> >    http://crux.nu/cgi-bin/trac.cgi/wiki/MailingLists
> >
> > Feel free to question and of those "rules", but let's write it down to
> > make sure it's visible. I also think we should consider writing a
> > similar
> > document for IRC.
> >
> > Kind regards, Johannes
> >
> > References:
> >   1 http://marc.theaimsgroup.com/?l=crux&m=113350973921921&w=2
> >   2 http://marc.theaimsgroup.com/?l=crux&m=113327551604693&w=2
> >
> > _______________________________________________
> > clc-devel mailing list
> > clc-devel at lists.berlios.de
> > http://lists.berlios.de/mailman/listinfo/clc-devel
> >
>
>
>
> --
> Jonathan Asghar
> phone: 512.619.0722




--
Jonathan Asghar
phone: 512.619.0722
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20051202/6318d11d/attachment.html>

From jasonthomasdolan at yahoo.com  Fri Dec  2 15:46:33 2005
From: jasonthomasdolan at yahoo.com (Jay Dolan)
Date: Fri, 2 Dec 2005 07:46:33 -0800 (PST)
Subject: [clc-devel] Mailing list usage guideline
In-Reply-To: <18016.193.5.216.100.1133511889.squirrel@hyoid.unibe.ch>
Message-ID: <20051202154633.29433.qmail@web32914.mail.mud.yahoo.com>

--- Johannes Winkelmann wrote:

> References:
> 1
http://marc.theaimsgroup.com/?l=crux&m=113350973921921&w=2
> 2
http://marc.theaimsgroup.com/?l=crux&m=113327551604693&w=2

Cptn, are you picking on poor Stewy?  :)

Seriously, I think it's a good idea to start the usage
guidelines pages, but only so we can point to them
ourselves when yet-another-ignorant-new-user makes the
same mistakes.  I doubt very much these pages would
prevent initial abuse from newbies.  After all, if
they'd taken the time to comb our documentation,
they'd probably answer their question in the first place.

Jay Dolan
Software Engineer, Systems Analyst
Windmill Cycles, Inc.
508.999.4000


		
__________________________________ 
Start your day with Yahoo! - Make it your home page! 
http://www.yahoo.com/r/hs


From jw at tks6.net  Fri Dec  2 15:54:01 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Fri, 2 Dec 2005 16:54:01 +0100
Subject: [clc-devel] Mailing list usage guideline
In-Reply-To: <57680e350512020634i584faa85y922393fa5fb5c1d0@mail.gmail.com>
References: <18016.193.5.216.100.1133511889.squirrel@hyoid.unibe.ch> <57680e350512020630l4acd5254xd3b53c13ac5d3f76@mail.gmail.com> <57680e350512020634i584faa85y922393fa5fb5c1d0@mail.gmail.com>
Message-ID: <20051202155327.GC3667@titanium>

Hi,

On Fri, Dec 02, 2005 at 08:34:09 -0600, Jonathan Asghar wrote:
> ...i know i'm breaking a rule here...
Actually, you broke three: your message also contained my e-mail address
in the attribution line, and you didn't cut the quoted message down to
what you where answering to.

I also added a note to avoid HTML/multipart messages, and to not CC the
original sender since they're on the list anyway.

> but something we should keep in mind about the top posting, gmail
> doesnt let you not do it.  It's designed that way unless you erase the
> whole email.
Actually, that's not that bad; if the gmail user follows the rule to
only quote the relevant parts, you want to go through the message
anyway; starting on top is the easiest way for most human beings.

Regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From jjasghar at gmail.com  Fri Dec  2 16:05:12 2005
From: jjasghar at gmail.com (Jonathan Asghar)
Date: Fri, 2 Dec 2005 10:05:12 -0600
Subject: [clc-devel] Mailing list usage guideline
In-Reply-To: <20051202155327.GC3667@titanium>
References: <18016.193.5.216.100.1133511889.squirrel@hyoid.unibe.ch>
	 <57680e350512020630l4acd5254xd3b53c13ac5d3f76@mail.gmail.com>
	 <57680e350512020634i584faa85y922393fa5fb5c1d0@mail.gmail.com>
	 <20051202155327.GC3667@titanium>
Message-ID: <57680e350512020805v20478514h3c96d996b0a730a1@mail.gmail.com>

On 12/2/05, Johannes Winkelmann <jw at tks6.net> wrote:
> Hi,
>
> On Fri, Dec 02, 2005 at 08:34:09 -0600, Jonathan Asghar wrote:
> > ...i know i'm breaking a rule here...
> Actually, you broke three: your message also contained my e-mail address
> in the attribution line, and you didn't cut the quoted message down to
> what you where answering to.

I'm going to make a concious effort now to make sure i only  post
directly to the  list.  I've always hit "reply all" and never looked
back.

> I also added a note to avoid HTML/multipart messages, and to not CC the
> original sender since they're on the list anyway.

I think i just converted to plain text right now, but i'm not 100% sure...

> > but something we should keep in mind about the top posting, gmail
> > doesnt let you not do it.  It's designed that way unless you erase the
> > whole email.
> Actually, that's not that bad; if the gmail user follows the rule to
> only quote the relevant parts, you want to go through the message
> anyway; starting on top is the easiest way for most human beings.
>
> Regards, Johannes
> --
> Johannes Winkelmann              mailto:jw at tks6.net
> Bern, Switzerland                http://jw.tks6.net
> _______________________________________________
> clc-devel mailing list
> clc-devel at lists.berlios.de
> http://lists.berlios.de/mailman/listinfo/clc-devel
>

Sorry about all this, but i'm going to do  my best now so i dont make
the same mistakes again.

-j



--
Jonathan Asghar
phone: 512.619.0722


From jw at tks6.net  Fri Dec  2 16:09:41 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Fri, 2 Dec 2005 17:09:41 +0100
Subject: [clc-devel] Mailing list usage guideline
In-Reply-To: <20051202154633.29433.qmail@web32914.mail.mud.yahoo.com>
References: <18016.193.5.216.100.1133511889.squirrel@hyoid.unibe.ch> <20051202154633.29433.qmail@web32914.mail.mud.yahoo.com>
Message-ID: <20051202160941.GE3667@titanium>

Hi,

On Fri, Dec 02, 2005 at 07:46:33 -0800, Jay Dolan wrote:
> --- Johannes Winkelmann wrote:
> 
> > References:
> > 1
> http://marc.theaimsgroup.com/?l=crux&m=113350973921921&w=2
> > 2
> http://marc.theaimsgroup.com/?l=crux&m=113327551604693&w=2
> 
> Cptn, are you picking on poor Stewy?  :)
Well... he's a good example. I didn't want to pick on him in particular,
even though I pointed it out to him previously in private mail, which he
seems to have ignored.

> Seriously, I think it's a good idea to start the usage guidelines
> pages, but only so we can point to them ourselves when
> yet-another-ignorant-new-user makes the same mistakes.  I doubt very
> much these pages would prevent initial abuse from newbies. 
Sure. I don't see this page as a "list of sins" or anything. Rather I'd
hope that we can friendly point new users to this page, where they find
a good overview of what we like to see.

We might consider adding it in a mailing list footer, so readers of the
list get a change to click the link and learn about the etiquette.

Regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From jasonthomasdolan at yahoo.com  Fri Dec  2 16:15:29 2005
From: jasonthomasdolan at yahoo.com (Jay Dolan)
Date: Fri, 2 Dec 2005 08:15:29 -0800 (PST)
Subject: [clc-devel] Mailing list usage guideline
In-Reply-To: <20051202160941.GE3667@titanium>
Message-ID: <20051202161529.84689.qmail@web32907.mail.mud.yahoo.com>

--- Johannes Winkelmann wrote:
> We might consider adding it in a mailing list
footer, so readers of the
> list get a change to click the link and learn about
the etiquette.

'Netiquette.  That's a great idea.

Jay Dolan
Software Engineer, Systems Analyst
Windmill Cycles, Inc.
508.999.4000


		
__________________________________________ 
Yahoo! DSL ? Something to write home about. 
Just $16.99/mo. or less. 
dsl.yahoo.com 



From jasonthomasdolan at yahoo.com  Fri Dec  2 16:17:42 2005
From: jasonthomasdolan at yahoo.com (Jay Dolan)
Date: Fri, 2 Dec 2005 08:17:42 -0800 (PST)
Subject: [clc-devel] Mailing list usage guideline
In-Reply-To: <57680e350512020805v20478514h3c96d996b0a730a1@mail.gmail.com>
Message-ID: <20051202161742.69147.qmail@web32903.mail.mud.yahoo.com>

--- Jonathan Asghar wrote:
> Sorry about all this, but i'm going to do  my best
> now so i dont make the same mistakes again.

Not bad.  You still had jw's email address in your
reply, tho.

I only tease ;)  I'm pretty sure I've been guilty of
that on more than one ocassion.

Jay Dolan
Software Engineer, Systems Analyst
Windmill Cycles, Inc.
508.999.4000


		
__________________________________ 
Start your day with Yahoo! - Make it your home page! 
http://www.yahoo.com/r/hs


From jw at tks6.net  Fri Dec  2 17:04:51 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Fri, 2 Dec 2005 18:04:51 +0100
Subject: [clc-devel] Making the switch to svn
In-Reply-To: <438888D6.6050507@varlock.com>
References: <20051126153553.35474.qmail@web32906.mail.mud.yahoo.com> <438888D6.6050507@varlock.com>
Message-ID: <20051202170451.GA1641@titanium>

Hi,

On Sat, Nov 26, 2005 at 17:09:58 +0100, Simone Rota wrote:
[...]
> I'd be more than happy also with a simple solution like making the
> crux.nu server update the svn repo to a local dir every, say, 5
> minutes and serve that dir via rsync (almost the same as with
> contrib-test).
Just for the record: there's another cool property of this setup: it'll
allow us to exchange the VCS if we want to, without the user realizing
it, or requiring any additional changes to the files in /etc/ports.

Thanks Simone :-).

Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From jw at tks6.net  Wed Dec  7 21:37:32 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Wed, 7 Dec 2005 22:37:32 +0100
Subject: [clc-devel] rsync files ready
Message-ID: <20051207213732.GA13683@titanium>

Hi,

If you want to get the rsync ports, you can do the following:

1. install rsync
2. get the ports driver from
http://www.karsikkopuu.net/crux/misc/rsync
3. move the driver to /etc/ports/drivers and make it executable
4. get 
   http://jw.tks6.net/files/crux/core.rsync
   http://jw.tks6.net/files/crux/opt.rsync
   http://jw.tks6.net/files/crux/contrib.rsync
5. mkdir /usr/ports/rsync
6. run ports -u

This should give you tthe latest ports in /usr/ports/rsync.

Regards, Johannes 
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From jjasghar at gmail.com  Wed Dec  7 21:55:01 2005
From: jjasghar at gmail.com (Jonathan Asghar)
Date: Wed, 7 Dec 2005 15:55:01 -0600
Subject: [clc-devel] rsync files ready
In-Reply-To: <20051207213732.GA13683@titanium>
References: <20051207213732.GA13683@titanium>
Message-ID: <57680e350512071355k4e7893bfycffef508cf570fc3@mail.gmail.com>

>
> This should give you tthe latest ports in /usr/ports/rsync.
>

done and done worked great!

--
Jonathan Asghar
phone: 512.619.0722


From jw at tks6.net  Wed Dec  7 21:55:29 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Wed, 7 Dec 2005 22:55:29 +0100
Subject: [clc-devel] Making the switch to svn
In-Reply-To: <20051126135245.GB5386@titanium>
References: <20051126135245.GB5386@titanium>
Message-ID: <20051207215529.GB13683@titanium>

Hi,

On Sat, Nov 26, 2005 at 14:52:46 +0100, Johannes Winkelmann wrote:
> Hi there,
[...]
> To avoid too much duplicate work and further user confusion, I'd suggest
> to switch the ports system to use the SVN repo from crux.nu soon

Here's an update:

* httpup repositories:
 - the httpup repos have to be reactivated on crux.nu, for core, opt and
   contrib (serving the current contrib-test)

> * Switch to svn:
>  - Write a short wiki page to tell the users what this is all about
Started but not finished yet:
  http://crux.nu/cgi-bin/trac.cgi/wiki/ServerMigration

>  - Make sure we have all dependencies
>    - pick up ports from danm
Not sure what the state is here

>    - contact vkd and Rilo Riemer; ask them to join the svn repo
Same here

>  - prepare an update 'ports' port containing core.svup and opt.svup;
>    those can be adapted from http://crux.nu/files/{core,opt}.svn
To be done, for rsync though. Should be really easy; I'd suggest to
prepare it in 'core' and expose it via httpup; this will allow the users
to do 
  $ httpup sync http://../ports/core#ports /tmp/ports
  $ cd /tmp/ports
  $ pkgmk -d -i

to update /etc/ports.

>  - update 'ports' port in CVSUp; 
Per needs to do that. Haven't heard from him in a while

> * contrib:
>  - provide a proper rsync driver for ports(8); I think Jay prepared one
>    already
Driver is there, thanks to Jukka.

>  - reenable the "duplicate view" and statistics in the ports-db on
>    crux.nu
To be done

If you happen to have some time please consider doing any of the missing
tasks. I should have more time again next week to join you.

Thanks, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From daniel at danm.de  Wed Dec  7 22:22:29 2005
From: daniel at danm.de (Daniel Mueller)
Date: Wed, 7 Dec 2005 23:22:29 +0100
Subject: [clc-devel] kdegraphics 3.4.3 - kpdf/xpdf security hole
Message-ID: <200512072322.35941.daniel@danm.de>

Hi Nick,

kdegraphics needs this patch as well:
ftp://ftp.foolabs.com/pub/xpdf/xpdf-3.01pl1.patch

(attached: kdegraphics-3.4.3.patch)

bye, danm

-- 
Daniel Mueller
Berlin, Germany         OpenPGP: 1024D/E4F4383A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kdegraphics-3.4.3.patch
Type: text/x-diff
Size: 4024 bytes
Desc: not available
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20051207/d9a10df4/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20051207/d9a10df4/attachment.asc>

From daniel at danm.de  Wed Dec  7 22:32:39 2005
From: daniel at danm.de (Daniel Mueller)
Date: Wed, 7 Dec 2005 23:32:39 +0100
Subject: [clc-devel] kdegraphics 3.4.3 - kpdf/xpdf security hole
In-Reply-To: <200512072322.35941.daniel@danm.de>
References: <200512072322.35941.daniel@danm.de>
Message-ID: <200512072332.39291.daniel@danm.de>

On Wednesday 07 December 2005 23:22, Daniel Mueller wrote:
> (attached: kdegraphics-3.4.3.patch)

bleh.. forget the attachment - it doesn't work yet ;-(

bye, danm

-- 
Daniel Mueller
Berlin, Germany         OpenPGP: 1024D/E4F4383A


From daniel at danm.de  Wed Dec  7 23:11:23 2005
From: daniel at danm.de (Daniel Mueller)
Date: Thu, 8 Dec 2005 00:11:23 +0100
Subject: [clc-devel] kdegraphics 3.4.3 - kpdf/xpdf security hole
In-Reply-To: <200512072332.39291.daniel@danm.de>
References: <200512072322.35941.daniel@danm.de> <200512072332.39291.daniel@danm.de>
Message-ID: <200512080011.27678.daniel@danm.de>

On Wednesday 07 December 2005 23:32, Daniel Mueller wrote:
> On Wednesday 07 December 2005 23:22, Daniel Mueller wrote:
> > (attached: kdegraphics-3.4.3.patch)
>
> bleh.. forget the attachment [..]

Okay, the second attempt. This time it compiles :-)

Kdegraphics 3.4.3 comes with an older version of xpdf. Unfortunately, this 
version doesn't know the gmallocn() function.

bye, danm

-- 
Daniel Mueller
Berlin, Germany         OpenPGP: 1024D/E4F4383A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kdegraphics-3.4.3.patch
Type: text/x-diff
Size: 5622 bytes
Desc: not available
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20051208/e93cfb0c/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20051208/e93cfb0c/attachment.asc>

From sip at varlock.com  Thu Dec  8 00:41:02 2005
From: sip at varlock.com (Simone Rota)
Date: Thu, 08 Dec 2005 01:41:02 +0100
Subject: [clc-devel] Making the switch to svn
In-Reply-To: <20051207215529.GB13683@titanium>
References: <20051126135245.GB5386@titanium> <20051207215529.GB13683@titanium>
Message-ID: <4397811E.7090004@varlock.com>

On 12/07/05 22:55 Johannes Winkelmann wrote:
>> - Make sure we have all dependencies
>>   - pick up ports from danm
> 
> Not sure what the state is here

Here's the missing deps (one level, there could be
missing subdeps as well)

	faac from ffmpeg
	gst-plugins from amarok
	hicolor-icon-theme from scite
	imlib2 from eterm, ffmpeg, giblib, libast
	iproute2 from vpnc
	kdebase from amarok
	kdelibs from amarok, k3b, kmplayer
	liba52 from libavifile, transcode
	libcdio from vcdimager
	libdevmapper from cryptsetup-luks
	libdvdread from dvdauthor, transcode
	libmikmod from sdl_mixer
	libxslt from docbook-xsl
	libxvid from ffmpeg, libavifile, transcode
	psutils from a2ps
	sdl_image from criticalmass, neverball, wesnoth
	tcl from ppracer
	xine-lib from amarok

> To be done, for rsync though. Should be really easy; I'd suggest to
> prepare it in 'core' and expose it via httpup;

I added an updated 'ports' port into attic containing
the rsync repos and drivers. I also moved Jue's rsync
into core.
Didn't touch the one in core yet since I'm afraid some
maintainer have a parallel setup with the cvsup ports.

Regards,
Simone

-- 
Simone Rota           WEB : http://www.varlock.com
Bergamo, Italy        MAIL: sip at varlock.com


From sip at varlock.com  Thu Dec  8 00:50:33 2005
From: sip at varlock.com (Simone Rota)
Date: Thu, 08 Dec 2005 01:50:33 +0100
Subject: [clc-devel] Making the switch to svn
In-Reply-To: <4397811E.7090004@varlock.com>
References: <20051126135245.GB5386@titanium> <20051207215529.GB13683@titanium> <4397811E.7090004@varlock.com>
Message-ID: <43978359.4000403@varlock.com>

On 12/08/05 01:41 Simone Rota wrote:

I love self replies :)

> I added an updated 'ports' port into attic containing
> the rsync repos and drivers. I also moved Jue's rsync
> into core.

Btw, should the cvsup port remain in core?


-- 
Simone Rota           WEB : http://www.varlock.com
Bergamo, Italy        MAIL: sip at varlock.com


From jasonthomasdolan at yahoo.com  Thu Dec  8 04:14:15 2005
From: jasonthomasdolan at yahoo.com (Jay Dolan)
Date: Wed, 7 Dec 2005 20:14:15 -0800 (PST)
Subject: [clc-devel] Making the switch to svn
In-Reply-To: <4397811E.7090004@varlock.com>
Message-ID: <20051208041415.15355.qmail@web32905.mail.mud.yahoo.com>

--- Simone Rota <sip at varlock.com> wrote:
> 	sdl_image from criticalmass, neverball, wesnoth

I just added sdl_image to opt, as I've been
maintaining it in my repository for quite some time
anyway.


Jay Dolan
Software Engineer, Systems Analyst
Windmill Cycles, Inc.
508.999.4000

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


From jasonthomasdolan at yahoo.com  Thu Dec  8 04:15:18 2005
From: jasonthomasdolan at yahoo.com (Jay Dolan)
Date: Wed, 7 Dec 2005 20:15:18 -0800 (PST)
Subject: [clc-devel] rsync files ready
In-Reply-To: <20051207213732.GA13683@titanium>
Message-ID: <20051208041518.75997.qmail@web32902.mail.mud.yahoo.com>

--- Johannes Winkelmann wrote:
> This should give you tthe latest ports in
> /usr/ports/rsync.

Worked great, and it's very fast.  Nice work, guys.

Sorry for the 2x mail, cptn - I accidentally fired off
my first response to just you ;)

Jay Dolan
Software Engineer, Systems Analyst
Windmill Cycles, Inc.
508.999.4000

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


From jasonthomasdolan at yahoo.com  Thu Dec  8 04:38:06 2005
From: jasonthomasdolan at yahoo.com (Jay Dolan)
Date: Wed, 7 Dec 2005 20:38:06 -0800 (PST)
Subject: [clc-devel] Filling in gaps with the new ports trees
Message-ID: <20051208043806.27077.qmail@web32908.mail.mud.yahoo.com>

Simone's mail had a partially-complete list of missing
deps from ports found in the new trees.  Yet another
issue is top-level ports which are not yet in one of
the new trees.  We really should sure-up the new
repository before plopping users in it.

If you have a moment, try the following:

1.  Edit prt-get.conf to define ONLY the new ports
trees:

prtdir /usr/ports/gnome  #gnome users maybe leave this
one

prtdir /usr/ports/rsync/core
prtdir /usr/ports/rsync/opt
prtdir /usr/ports/rsync/contrib

2.  Issue something like:

for p in $(prt-get listinst); do
  prt-get path $p >/dev/null
done

3.  Hunt down those missing ports and adopt them!


Jay Dolan
Software Engineer, Systems Analyst
Windmill Cycles, Inc.
508.999.4000

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


From jue at jue.li  Thu Dec  8 17:39:51 2005
From: jue at jue.li (Juergen Daubert)
Date: Thu, 8 Dec 2005 18:39:51 +0100
Subject: [clc-devel] Making the switch to svn
In-Reply-To: <4397811E.7090004@varlock.com>
References: <20051126135245.GB5386@titanium> <20051207215529.GB13683@titanium> <4397811E.7090004@varlock.com>
Message-ID: <20051208173951.GA28469@jue.netz>

On Thu, Dec 08, 2005 at 01:41:02AM +0100, Simone Rota wrote:
> On 12/07/05 22:55 Johannes Winkelmann wrote:
> >> - Make sure we have all dependencies
> >>   - pick up ports from danm
> > 
> > Not sure what the state is here
> 
> Here's the missing deps (one level, there could be
> missing subdeps as well)

Simone, thanks for that list.

> 	hicolor-icon-theme from scite

Hmm, that's a problem, because the port vanished into the gnome 
repo. Matt, could you move it back, please ?

> 	psutils from a2ps

Fixed.


Greetings
J?rgen

-- 
Juergen Daubert  |  mailto:jue at jue.li  
Korb, Germany    |  http://jue.li/crux



From viper at hometux.de  Fri Dec  9 13:27:24 2005
From: viper at hometux.de (Simon =?iso-8859-1?Q?Glo=DFner?=)
Date: Fri, 9 Dec 2005 14:27:24 +0100
Subject: [clc-devel] Making the switch to svn
In-Reply-To: <4397811E.7090004@varlock.com>
References: <20051126135245.GB5386@titanium> <20051207215529.GB13683@titanium> <4397811E.7090004@varlock.com>
Message-ID: <20051209132724.GA31594@viper.lan>

On Thu, Dec 08, 2005 at 01:41:02AM +0100, Simone Rota wrote:
> Here's the missing deps (one level, there could be
> missing subdeps as well)
> 
> 	faac from ffmpeg
> 	gst-plugins from amarok
> 	hicolor-icon-theme from scite
> 	imlib2 from eterm, ffmpeg, giblib, libast
> 	iproute2 from vpnc
> 	kdebase from amarok
> 	kdelibs from amarok, k3b, kmplayer
> 	liba52 from libavifile, transcode
> 	libcdio from vcdimager
> 	libdevmapper from cryptsetup-luks
> 	libdvdread from dvdauthor, transcode
> 	libmikmod from sdl_mixer
> 	libxslt from docbook-xsl
> 	libxvid from ffmpeg, libavifile, transcode
> 	psutils from a2ps
> 	sdl_image from criticalmass, neverball, wesnoth
> 	tcl from ppracer
> 	xine-lib from amarok

I will adopt the port libdevmapper. I have checked who is the
maintainer of these ports and mostly Nick is the one. I will send him
a mail if he needs some help because he seems to be very busy at his
study.

Regards Viper


From clc-devel at berlios.de  Fri Dec  9 17:46:47 2005
From: clc-devel at berlios.de (clc-devel at berlios.de)
Date: Fri, 09 Dec 2005 18:46:47 +0100
Subject: [clc-devel] [security] /
Message-ID: <4399c307.q2C6JA79w4+sJNh1%clc-devel@lists.berlios.de>

This is a notification of a security related commit in
/:
 kdjf

Commit information:
  Author: jw
  Date: 2005-12-09 18:46:47 +0100 (Fri, 09 Dec 2005)

  URL http://crux.nu/cgi-bin/trac.cgi/changeset/18


From jjasghar at gmail.com  Fri Dec  9 17:50:49 2005
From: jjasghar at gmail.com (Jonathan Asghar)
Date: Fri, 9 Dec 2005 11:50:49 -0600
Subject: [clc-devel] [security] /
In-Reply-To: <4399c307.q2C6JA79w4+sJNh1%clc-devel@lists.berlios.de>
References: <4399c307.q2C6JA79w4+sJNh1%clc-devel@lists.berlios.de>
Message-ID: <57680e350512090950k54ab5ed5ue832b28a0260d3ca@mail.gmail.com>

> This is a notification of a security related commit in
> /:
>  kdjf
>
> Commit information:
>   Author: jw
>   Date: 2005-12-09 18:46:47 +0100 (Fri, 09 Dec 2005)

Can i say "classic?"
:P

-j


From clc-devel at berlios.de  Fri Dec  9 17:54:15 2005
From: clc-devel at berlios.de (clc-devel at berlios.de)
Date: Fri, 09 Dec 2005 18:54:15 +0100
Subject: [clc-devel] [security] tools/scripts/
Message-ID: <4399c4c7.RXrLdGl3SuZHkqfD%clc-devel@lists.berlios.de>

This is a notification of a security related commit in
tools/scripts/:
 fix a minor bug, and test it again

Commit information:
  Author: jw
  Date: 2005-12-09 18:54:14 +0100 (Fri, 09 Dec 2005)

  URL http://crux.nu/cgi-bin/trac.cgi/changeset/314


From jw at tks6.net  Fri Dec  9 18:00:08 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Fri, 9 Dec 2005 19:00:08 +0100
Subject: [clc-devel] [security] tools/scripts/
In-Reply-To: <4399c4c7.RXrLdGl3SuZHkqfD%clc-devel@lists.berlios.de>
References: <4399c4c7.RXrLdGl3SuZHkqfD%clc-devel@lists.berlios.de>
Message-ID: <20051209180008.GC6186@titanium>

Hi,

On Fri, Dec 09, 2005 at 18:54:15 +0100, clc-devel at berlios.de wrote:
> This is a notification of a security related commit in
> tools/scripts/:
>  fix a minor bug, and test it again
As you see here, notifications for our svn repo work now too; just start
your commit message with "[security]".

Regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From jw at tks6.net  Fri Dec  9 18:12:37 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Fri, 9 Dec 2005 19:12:37 +0100
Subject: [clc-devel] Filling in gaps with the new ports trees
In-Reply-To: <20051208043806.27077.qmail@web32908.mail.mud.yahoo.com>
References: <20051208043806.27077.qmail@web32908.mail.mud.yahoo.com>
Message-ID: <20051209181237.GD6186@titanium>

Hi,

On Wed, Dec 07, 2005 at 20:38:06 -0800, Jay Dolan wrote:
> Simone's mail had a partially-complete list of missing
> deps from ports found in the new trees.  Yet another
> issue is top-level ports which are not yet in one of
> the new trees.  We really should sure-up the new
> repository before plopping users in it.
Here's a list showing the difference between current base/opt/contrib,
and core/opt:
  http://crux.nu/cgi-bin/trac.cgi/wiki/ServerMigrationMissingPorts

Not all ports will have to be imported, obviously.

Regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From sip at varlock.com  Fri Dec  9 18:41:33 2005
From: sip at varlock.com (Simone Rota)
Date: Fri, 09 Dec 2005 19:41:33 +0100
Subject: [clc-devel] Filling in gaps with the new ports trees
In-Reply-To: <20051209181237.GD6186@titanium>
References: <20051208043806.27077.qmail@web32908.mail.mud.yahoo.com> <20051209181237.GD6186@titanium>
Message-ID: <4399CFDD.3060708@varlock.com>

On 12/09/05 19:12 Johannes Winkelmann wrote:
> Here's a list showing the difference between current base/opt/contrib,
> and core/opt:
>   http://crux.nu/cgi-bin/trac.cgi/wiki/ServerMigrationMissingPorts
> 
> Not all ports will have to be imported, obviously.

Thanks for the list;
If you're going to drop maintainership for some port, I think
it's a good idea to import them into attic (minus the maintainer
field).

Regards,
Simone

-- 
Simone Rota           WEB : http://www.varlock.com
Bergamo, Italy        MAIL: sip at varlock.com


From clc-devel at berlios.de  Fri Dec  9 19:09:36 2005
From: clc-devel at berlios.de (clc-devel at berlios.de)
Date: Fri, 09 Dec 2005 20:09:36 +0100
Subject: [clc-devel] [security] crux-2.1/ports/core/perl/
Message-ID: <4399d670.2hrAL63QiikYqwyx%clc-devel@lists.berlios.de>

This is a notification of a security related commit in
crux-2.1/ports/core/perl/:
 perl: updated to version 5.8.7, including a fix for CVE-2005-3962 (http://www.dyadsecurity.com/perl-0002.html)

Commit information:
  Author: jheino
  Date: 2005-12-09 20:09:34 +0100 (Fri, 09 Dec 2005)

  URL http://crux.nu/cgi-bin/trac.cgi/changeset/321


From jw at tks6.net  Fri Dec  9 19:10:36 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Fri, 9 Dec 2005 20:10:36 +0100
Subject: [clc-devel] rsync files ready
In-Reply-To: <20051207213732.GA13683@titanium>
References: <20051207213732.GA13683@titanium>
Message-ID: <20051209191036.GE6186@titanium>

Hi,

Unfortunately, we didn't consider remember to support different versions
of crux in our *.rsync files... changed now.

On Wed, Dec 07, 2005 at 22:37:32 +0100, Johannes Winkelmann wrote:
> Hi,
> 
> If you want to get the rsync ports, you can do the following:
> 
> 1. install rsync
> 2. get the ports driver from
> http://www.karsikkopuu.net/crux/misc/rsync
> 3. move the driver to /etc/ports/drivers and make it executable
> 4. get 
>    http://jw.tks6.net/files/crux/core.rsync
>    http://jw.tks6.net/files/crux/opt.rsync
>    http://jw.tks6.net/files/crux/contrib.sync
I uploaded a new version of those files; please update your local
copies.

Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From jw at tks6.net  Fri Dec  9 19:35:49 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Fri, 9 Dec 2005 20:35:49 +0100
Subject: [clc-devel] rsync files ready
In-Reply-To: <20051209191036.GE6186@titanium>
References: <20051207213732.GA13683@titanium> <20051209191036.GE6186@titanium>
Message-ID: <20051209193547.GF6186@titanium>

Hi,

On Fri, Dec 09, 2005 at 20:10:36 +0100, Johannes Winkelmann wrote:
> Hi,
[...]
> I uploaded a new version of those files; please update your local
> copies.
In addition, there are httpup repos at
  http://www.crux.nu/ports/crux-2.1/core
and
  http://www.crux.nu/ports/crux-2.1/opt

Enjoy, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From viper at hometux.de  Fri Dec  9 23:22:07 2005
From: viper at hometux.de (Simon =?iso-8859-1?Q?Glo=DFner?=)
Date: Sat, 10 Dec 2005 00:22:07 +0100
Subject: [clc-devel] Filling in gaps with the new ports trees
In-Reply-To: <20051209181237.GD6186@titanium>
References: <20051208043806.27077.qmail@web32908.mail.mud.yahoo.com> <20051209181237.GD6186@titanium>
Message-ID: <20051209232207.GA14200@viper.lan>

On Fri, Dec 09, 2005 at 07:12:37PM +0100, Johannes Winkelmann wrote:
> On Wed, Dec 07, 2005 at 20:38:06 -0800, Jay Dolan wrote:
> > Simone's mail had a partially-complete list of missing
> > deps from ports found in the new trees.  Yet another
> > issue is top-level ports which are not yet in one of
> > the new trees.  We really should sure-up the new
> > repository before plopping users in it.
> Here's a list showing the difference between current base/opt/contrib,
> and core/opt:
>   http://crux.nu/cgi-bin/trac.cgi/wiki/ServerMigrationMissingPorts
> 
> Not all ports will have to be imported, obviously.

Thanks for the list. Is any of these maintainers known as inactive
like Damn? Or is this a list of ports which should be adopted?

Regards Viper


From jukka at karsikkopuu.net  Sat Dec 10 05:32:08 2005
From: jukka at karsikkopuu.net (Jukka Heino)
Date: Sat, 10 Dec 2005 07:32:08 +0200
Subject: [clc-devel] Implications of the perl 5.8.7 update
Message-ID: <439A6858.8020409@karsikkopuu.net>

Hi,

The 5.8.7 update for perl I committed last night causes some footprint 
mismatches for the following ports:

cddb_get
gaim
imagemagick
irssi
kdebindings
mod_perl
p5-cgi
p5-html-parser
p5-html-tagset
p5-xml-parser

Fixing them is only a matter of replacing '5.8.6' with '5.8.7' in the 
.footprints, but I think we should also increment the release number in 
order to force recompilation. There are some ports in httpup 
repositories which require similar measures, so this will probably need 
to be announced also on the CRUX mailing list after the switch to the 
new server is complete.

// Jukka


From jw at tks6.net  Sat Dec 10 09:15:22 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Sat, 10 Dec 2005 10:15:22 +0100
Subject: [clc-devel] Implications of the perl 5.8.7 update
In-Reply-To: <439A6858.8020409@karsikkopuu.net>
References: <439A6858.8020409@karsikkopuu.net>
Message-ID: <20051210091522.GG6186@titanium>

Hi,
On Sat, Dec 10, 2005 at 07:32:08 +0200, Jukka Heino wrote:
> Hi,
> 
> The 5.8.7 update for perl I committed last night causes some footprint 
> mismatches for the following ports:
[...]
> Fixing them is only a matter of replacing '5.8.6' with '5.8.7' in the 
> .footprints, but I think we should also increment the release number in 
> order to force recompilation. There are some ports in httpup 
> repositories which require similar measures, so this will probably need 
> to be announced also on the CRUX mailing list after the switch to the 
> new server is complete.
We could consider extending our automated notification for such
situations (updates which require recompilation of dependent packages).
Some special situations might need additional information, but a general
"[incompatible]" warning might save us some work.

Comments?
Regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From trac at crux.nu  Sat Dec 10 12:36:23 2005
From: trac at crux.nu (CRUX)
Date: Sat, 10 Dec 2005 12:36:23 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=239=3A_cdrdao=3A_new_version_out?=
Message-ID: <057.3678505b2d2053e3d6250d7ddd4891a0@crux.nu>

#9: cdrdao: new version out
-------------------------+--------------------------------------------------
       Id:  9            |      Status:  new                     
Component:  ports        |    Modified:  Sat Dec 10 13:36:23 2005
 Severity:  trivial      |   Milestone:                          
 Priority:  normal       |     Version:  2.0                     
    Owner:  Simone Rota  |    Reporter:  Speek                   
-------------------------+--------------------------------------------------
 There's an update of cdrdao: 1.2.1.

-- 
Ticket URL: <http://www.crux.nu/cgi-bin/trac.cgi/ticket/9>
CRUX <http://example.com/>
CRUX


From trac at crux.nu  Sat Dec 10 12:51:23 2005
From: trac at crux.nu (CRUX)
Date: Sat, 10 Dec 2005 12:51:23 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=239=3A_cdrdao=3A_new_version_out?=
In-Reply-To: <057.3678505b2d2053e3d6250d7ddd4891a0@crux.nu>
References: <057.3678505b2d2053e3d6250d7ddd4891a0@crux.nu>
Message-ID: <066.a2166f14b5c417f3c63ac2a121cf128f@crux.nu>

#9: cdrdao: new version out
-------------------------+--------------------------------------------------
       Id:  9            |      Status:  closed                  
Component:  ports        |    Modified:  Sat Dec 10 13:51:23 2005
 Severity:  trivial      |   Milestone:                          
 Priority:  normal       |     Version:  2.0                     
    Owner:  Simone Rota  |    Reporter:  Speek                   
-------------------------+--------------------------------------------------
Changes (by sip):

  * resolution:  => fixed
  * status:  new => closed

Comment:

 thanks, fixed in [324]

-- 
Ticket URL: <http://www.crux.nu/cgi-bin/trac.cgi/ticket/9>
CRUX <http://example.com/>
CRUX


From predivan at ptt.yu  Thu Dec  8 23:06:20 2005
From: predivan at ptt.yu (Predrag Ivanovic)
Date: Fri, 9 Dec 2005 00:06:20 +0100
Subject: [clc-devel] rsync files ready
In-Reply-To: <20051207213732.GA13683@titanium>
References: <20051207213732.GA13683@titanium>
Message-ID: <20051209000620.4a20b182.predivan@ptt.yu>

On Wed, 7 Dec 2005 22:37:32 +0100
Johannes Winkelmann wrote:

> Hi,
 Hi Johannes.
 
> If you want to get the rsync ports, you can do the following:
> 
> 1. install rsync
> 2. get the ports driver from
> http://www.karsikkopuu.net/crux/misc/rsync
> 3. move the driver to /etc/ports/drivers and make it executable
> 4. get 
>    http://jw.tks6.net/files/crux/core.rsync
>    http://jw.tks6.net/files/crux/opt.rsync
>    http://jw.tks6.net/files/crux/contrib.rsync
> 5. mkdir /usr/ports/rsync
> 6. run ports -u
> 
> This should give you tthe latest ports in /usr/ports/rsync.

I did all that,and it works great,quicker,IMHO, than with svn repo.
A question,if I may.
After checkout I get the following :
--
Error: Couldn't chroot into /usr/ports/rsync/opt (Operation not permitted)
Updating failed
---
Same error with contrib,core and contrib-test.
Since I'm using Han's pkgutils,I run ports -u as non-root,and all directories under /usr/ports are owned
by that user(all permissions are OK,AFAICT).
I don't get that error with either cvsup or httup backend.
This line from rsync driver trigers it:
---
# use chroot as an additional safety measure when removing files
chroot($destination) or error("Couldn't chroot into $destination");
chdir('/');
---
How can I resolve this?Is there a workaround? man chroot isn't very helpful :-(
How does this chroot thingie work,anyway?
Other than that,great work,as always,from CLC crew,thank you <g>

> Regards, Johannes 

Pedja
-- 
 "Hell, just simulate the first unicellular organisms, then
  have it run four billion years in a minute, and you have instant humans!
  (Assuming you simulated the rest of the universe correctly.)"


From jw at tks6.net  Sat Dec 10 15:39:17 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Sat, 10 Dec 2005 16:39:17 +0100
Subject: [clc-devel] rsync files ready
In-Reply-To: <20051209000620.4a20b182.predivan@ptt.yu>
References: <20051207213732.GA13683@titanium> <20051209000620.4a20b182.predivan@ptt.yu>
Message-ID: <20051210153917.GJ6186@titanium>

Hi Pedja,

On Fri, Dec 09, 2005 at 00:06:20 +0100, Predrag Ivanovic wrote:
> On Wed, 7 Dec 2005 22:37:32 +0100
> Johannes Winkelmann wrote:
> 
> > Hi,
>  Hi Johannes.
>  
> > If you want to get the rsync ports, you can do the following:
[...]
> > This should give you tthe latest ports in /usr/ports/rsync.
> 
> I did all that,and it works great,quicker,IMHO, than with svn repo.
Good to hear. I'm also quite impressed by the speed.

> A question,if I may.
> After checkout I get the following :
> --
> Error: Couldn't chroot into /usr/ports/rsync/opt (Operation not permitted)
> Updating failed
> ---
> Same error with contrib,core and contrib-test.
> Since I'm using Han's pkgutils,I run ports -u as non-root,and all
> directories under /usr/ports are owned by that user(all permissions
> are OK,AFAICT).
Okay; well, I 

> I don't get that error with either cvsup or httup backend.
> This line from rsync driver trigers it:
> ---
> # use chroot as an additional safety measure when removing files
> chroot($destination) or error("Couldn't chroot into $destination");
> chdir('/');
> ---
> How can I resolve this? Is there a workaround?
You're the first to report that (and it's good to learn about this now
before we switch), thanks. 

> man chroot isn't very helpful :-(
man 2 chroot describes the system call if you look for details

> How does this chroot thingie work,anyway?
Basically, it just uses /usr/ports/opt as its new root, which is a
really effective way to make sure we don't accidently remove other
files (since they're not accessible from within this chroot
environment). We'll try to find a better solution for it soon, stay
tuned :-).

> Other than that,great work,as always,from CLC crew,thank you <g>
Thank you!

Best regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From jukka at karsikkopuu.net  Sat Dec 10 16:32:04 2005
From: jukka at karsikkopuu.net (Jukka Heino)
Date: Sat, 10 Dec 2005 18:32:04 +0200
Subject: [clc-devel] rsync files ready
In-Reply-To: <20051210153917.GJ6186@titanium>
References: <20051207213732.GA13683@titanium> <20051209000620.4a20b182.predivan@ptt.yu> <20051210153917.GJ6186@titanium>
Message-ID: <439B0304.5010209@karsikkopuu.net>

Johannes Winkelmann wrote:

>On Fri, Dec 09, 2005 at 00:06:20 +0100, Predrag Ivanovic wrote:
>
[...]


>>A question,if I may.
>>After checkout I get the following :
>>--
>>Error: Couldn't chroot into /usr/ports/rsync/opt (Operation not permitted)
>>Updating failed
>>---
>>Same error with contrib,core and contrib-test.
>>Since I'm using Han's pkgutils,I run ports -u as non-root,and all
>>directories under /usr/ports are owned by that user(all permissions
>>are OK,AFAICT).
>>    
>>
>Basically, it just uses /usr/ports/opt as its new root, which is a
>really effective way to make sure we don't accidently remove other
>files (since they're not accessible from within this chroot
>environment). We'll try to find a better solution for it soon, stay
>tuned :-).
>
>  
>
Hi Pedja,

I've prepared a new driver file which falls back to plain old chdir() 
and path validation when running as a normal user. Can you put this to 
/etc/ports/drivers/rsync and see if it fixes your problem: 
http://www.karsikkopuu.net/crux/misc/rsync

Regards,
Jukka


From jw at tks6.net  Sun Dec 11 09:51:23 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Sun, 11 Dec 2005 10:51:23 +0100
Subject: [clc-devel] rsync switch: guide & date proposition
Message-ID: <20051211095123.GB17807@titanium>

Hi,

Yesterday Jukka and I discussed whether it makes sense to automate the
switch to rsync in some way, and arrived at the conclusion that we
should rather provide a good guide since the changes are quite
important, and the users should really understand what happens there
(especially WRT new contrib).

I've written a draft for that on
  http://crux.nu/cgi-bin/trac.cgi/wiki/ServerMigration
(second part)

It's a bit verbose, but I wanted to make sure that every user can update
his/her system with it. Also note that the prt.tar.gz links don't work
yet.
If you have a moment, please have a quick look and correct my grammar,
spelling, wording and the wrong commands I might have used :-).


Other that that, I'd suggest to switch ASAP now, and look into any
further problems later on (since I believe the things we didn't solve to
this point won't be solved in the next couple of days anyway). My
proposition is to do announce it on tuesday next week. Please let me
know if you either agree or disagree with this date.

Also, I've started a page with tasks to we'll have to look into after
the switch (and possibly next year):
  http://crux.nu/cgi-bin/trac.cgi/wiki/PostSwitch
Please add your notes there as well. Priorities are up for discussion,
of course.

Best regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From jue at jue.li  Sun Dec 11 12:27:14 2005
From: jue at jue.li (Juergen Daubert)
Date: Sun, 11 Dec 2005 13:27:14 +0100
Subject: [clc-devel] rsync switch: guide & date proposition
In-Reply-To: <20051211095123.GB17807@titanium>
References: <20051211095123.GB17807@titanium>
Message-ID: <20051211122714.GA3012@jue.netz>

On Sun, Dec 11, 2005 at 10:51:23AM +0100, Johannes Winkelmann wrote:
> Hi,

Hello Johannes,

> Yesterday Jukka and I discussed whether it makes sense to automate the
> switch to rsync in some way, and arrived at the conclusion that we
> should rather provide a good guide since the changes are quite
> important, and the users should really understand what happens there
> (especially WRT new contrib).
> 
> I've written a draft for that on
>   http://crux.nu/cgi-bin/trac.cgi/wiki/ServerMigration
> (second part)
> 
> It's a bit verbose, but I wanted to make sure that every user can update
> his/her system with it. Also note that the prt.tar.gz links don't work
> yet.
> If you have a moment, please have a quick look and correct my grammar,
> spelling, wording and the wrong commands I might have used :-).

Yery comprehensive and clear page, thanks.

> Other that that, I'd suggest to switch ASAP now, and look into any
> further problems later on (since I believe the things we didn't solve to
> this point won't be solved in the next couple of days anyway). My
> proposition is to do announce it on tuesday next week. Please let me
> know if you either agree or disagree with this date.

Yep, go for it.

Greetings
J?rgen

-- 
Juergen Daubert  |  mailto:jue at jue.li  
Korb, Germany    |  http://jue.li/crux



From jasonthomasdolan at yahoo.com  Sun Dec 11 14:11:57 2005
From: jasonthomasdolan at yahoo.com (Jay Dolan)
Date: Sun, 11 Dec 2005 06:11:57 -0800 (PST)
Subject: Fwd: Re: [clc-devel] rsync switch: guide & date proposition
Message-ID: <20051211141157.33751.qmail@web32904.mail.mud.yahoo.com>

Ugh, I double-mailed cptn again :/

> --- Johannes Winkelmann wrote:
> > Hi,
> 
> Stud 8)
> 
> > 
> > I've written a draft for that on
> >  
> >
> http://crux.nu/cgi-bin/trac.cgi/wiki/ServerMigration
> > (second part)
> 
> It looked really good to me.  I made just a couple
> wording changes, and added the Summary section to
> the
> end (for people who, say, have to update multiple
> boxes).
> 
> How did you guys resolve the multiple-version issue
> with the rsync driver?  (e.g. crux-2.1/ports)  Was
> it
> trivial?  If that's taken care of, yea - let's
> switcheroo! :)



Jay Dolan
Software Engineer, Systems Analyst
Windmill Cycles, Inc.
508.999.4000

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


From tillbiedermann at yahoo.de  Sun Dec 11 23:10:23 2005
From: tillbiedermann at yahoo.de (Till Biedermann)
Date: Mon, 12 Dec 2005 00:10:23 +0100
Subject: [clc-devel] rsync switch: guide & date proposition
In-Reply-To: <20051211095123.GB17807@titanium>
References: <20051211095123.GB17807@titanium>
Message-ID: <439CB1DF.8030805@yahoo.de>


Johannes Winkelmann wrote:
> If you have a moment, please have a quick look and correct my grammar,
> spelling, wording and the wrong commands I might have used :-).
> 

The guide looks quite clear. Grammar, spelling and wording are better
than mine - so there are no corrections from my side ;-)


> Other that that, I'd suggest to switch ASAP now, and look into any
> further problems later on (since I believe the things we didn't solve to
> this point won't be solved in the next couple of days anyway). My
> proposition is to do announce it on tuesday next week. Please let me
> know if you either agree or disagree with this date.
> 

I agree.


Regards Till



	

	
		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de


From clc-devel at berlios.de  Mon Dec 12 01:38:17 2005
From: clc-devel at berlios.de (clc-devel at berlios.de)
Date: Mon, 12 Dec 2005 02:38:17 +0100
Subject: [clc-devel] [security] crux-2.1/ports/opt/kdegraphics/
Message-ID: <439cd489.w41EyBJqsPXwxYjY%clc-devel@lists.berlios.de>

This is a notification of a security related commit in
crux-2.1/ports/opt/kdegraphics/:
 kdegraphics: patch xpdf/kpdf vulnerability

Commit information:
  Author: sten
  Date: 2005-12-12 02:38:14 +0100 (Mon, 12 Dec 2005)

  URL http://crux.nu/cgi-bin/trac.cgi/changeset/339


From trac at crux.nu  Mon Dec 12 10:18:49 2005
From: trac at crux.nu (CRUX)
Date: Mon, 12 Dec 2005 10:18:49 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2310=3A_groff_mm_macros_incorrectly_center_display_?=
 =?utf-8?q?captions?=
Message-ID: <057.37c156272958997d883240370be808b6@crux.nu>

#10: groff mm macros incorrectly center display captions
--------------------+-------------------------------------------------------
       Id:  10      |      Status:  new                     
Component:  ports   |    Modified:  Mon Dec 12 11:18:48 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  per     |    Reporter:  danieldk at pobox.com      
--------------------+-------------------------------------------------------
 The groff 1.19.x mm macros incorrectly center the display captions. This
 error is documented here:

 http://lists.gnu.org/archive/html/groff/2005-10/msg00221.html and
 http://lists.gnu.org/archive/html/groff/2005-10/msg00235.html

 And was fixed in CVS:

 http://lists.gnu.org/archive/html/groff/2005-10/msg00235.html

 I have created a patch for the groff 1.19.2 port that fixes this:

 http://danieldk.org/crux/patches/groff-1.19.2-mm.diff

-- 
Ticket URL: <http://www.crux.nu/cgi-bin/trac.cgi/ticket/10>
CRUX <http://example.com/>
CRUX


From clc-devel at berlios.de  Mon Dec 12 17:50:52 2005
From: clc-devel at berlios.de (clc-devel at berlios.de)
Date: Mon, 12 Dec 2005 18:50:52 +0100
Subject: [clc-devel] [security] crux-2.1/ports/opt/dropbear/
Message-ID: <439db87c./ZqYQYeg2B1PQWtD%clc-devel@lists.berlios.de>

This is a notification of a security related commit in
crux-2.1/ports/opt/dropbear/:
 dropbear: update to 0.47, http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/2005q4/000312.html

Commit information:
  Author: jue
  Date: 2005-12-12 18:50:50 +0100 (Mon, 12 Dec 2005)

  URL http://crux.nu/cgi-bin/trac.cgi/changeset/342


From predivan at ptt.yu  Mon Dec 12 18:52:45 2005
From: predivan at ptt.yu (Predrag Ivanovic)
Date: Mon, 12 Dec 2005 19:52:45 +0100
Subject: [RESEND]Re: [clc-devel] rsync files ready
In-Reply-To: <20051207213732.GA13683@titanium>
References: <20051207213732.GA13683@titanium>
Message-ID: <20051212195245.f2660d5b.predivan@ptt.yu>

On Wed, 7 Dec 2005 22:37:32 +0100
Johannes Winkelmann wrote:

> Hi,
 Hi Johannes.
 
> If you want to get the rsync ports, you can do the following:
> 
> 1. install rsync
> 2. get the ports driver from
> http://www.karsikkopuu.net/crux/misc/rsync
> 3. move the driver to /etc/ports/drivers and make it executable
> 4. get 
>    http://jw.tks6.net/files/crux/core.rsync
>    http://jw.tks6.net/files/crux/opt.rsync
>    http://jw.tks6.net/files/crux/contrib.rsync
> 5. mkdir /usr/ports/rsync
> 6. run ports -u
> 
> This should give you tthe latest ports in /usr/ports/rsync.

I did all that,and it works great,very fast,even on dialup.
A question,if I may.
After checkout I get the following :
--
Error: Couldn't chroot into /usr/ports/rsync/opt (Operation not permitted)
Updating failed
---
Same error with contrib,core and contrib-test.
Since I'm using Han's pkgutils,I run ports -u as non-root,and all directories under /usr/ports are owned
by that user(all permissions are OK,AFAICT).
I don't get that error with either cvsup or httup backend.
This line from rsync driver trigers it:
---
# use chroot as an additional safety measure when removing files
chroot($destination) or error("Couldn't chroot into $destination");
chdir('/');
---
After I commented out this line,I did a checkout again,everything works fine.
How does this chroot thingie work,anyway?
Is commenting out this line a Bad Idea[tm]?   
Other than that minor issue,great work,as always,from CLC crew,thank you <g>

> Regards, Johannes 

Pedja
-- 
 "Hell, just simulate the first unicellular organisms, then
  have it run four billion years in a minute, and you have instant humans!
  (Assuming you simulated the rest of the universe correctly.)"


From trac at crux.nu  Mon Dec 12 19:09:10 2005
From: trac at crux.nu (CRUX)
Date: Mon, 12 Dec 2005 19:09:10 -0000
Subject: [clc-devel] =?utf-8?b?UmU6IFtDUlVYXSAjMzogZGNyb24gJiBzbG9jYXRl?=
In-Reply-To: <057.9c8a1dd438ade51cc1322fd872b769ed@crux.nu>
References: <057.9c8a1dd438ade51cc1322fd872b769ed@crux.nu>
Message-ID: <066.312f02feba715ed85c33004f50bccb51@crux.nu>

#3: dcron & slocate
---------------------+------------------------------------------------------
       Id:  3        |      Status:  closed                  
Component:  ports    |    Modified:  Mon Dec 12 20:09:09 2005
 Severity:  trivial  |   Milestone:                          
 Priority:  normal   |     Version:  2.0                     
    Owner:  per      |    Reporter:  daniel at danm dot de   
---------------------+------------------------------------------------------
Changes (by jue):

  * resolution:  => fixed
  * status:  reopened => closed

Comment:

 Thanks for reporting.

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/3>
CRUX <http://example.com/>
CRUX


From trac at crux.nu  Tue Dec 13 21:14:50 2005
From: trac at crux.nu (CRUX)
Date: Tue, 13 Dec 2005 21:14:50 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2311=3A_=5BPATCH=5D_prt-get_to_consider_toolchain_f?=
 =?utf-8?q?irst?=
Message-ID: <057.2c10da569ee75ddaec624c3e95db75c0@crux.nu>

#11: [PATCH] prt-get to consider toolchain first
---------------------+------------------------------------------------------
       Id:  11       |      Status:  new                     
Component:  prt-get  |    Modified:  Tue Dec 13 22:14:50 2005
 Severity:  normal   |   Milestone:                          
 Priority:  normal   |     Version:  2.0                     
    Owner:  jw       |    Reporter:  cbou at mail.ru            
---------------------+------------------------------------------------------
 There is no toolchain dependencies in every port, which is okey, but in
 that case prt-get must take care about it.

 This patch used to address that issue.

-- 
Ticket URL: <http://www.crux.nu/cgi-bin/trac.cgi/ticket/11>
CRUX <http://example.com/>
CRUX


From jjasghar at gmail.com  Wed Dec 14 03:57:22 2005
From: jjasghar at gmail.com (Jonathan Asghar)
Date: Tue, 13 Dec 2005 21:57:22 -0600
Subject: [clc-devel] Re: about the new crux ports reorganization and multiplatform support :D
In-Reply-To: <439F52AB.5010905@libero.it>
References: <439F52AB.5010905@libero.it>
Message-ID: <57680e350512131957n159c283xcd5f680a7e3116f8@mail.gmail.com>

Hey guys...

> giulivo someone can help me to understand the new ports organization and
> how to synch with it in the best way using cruxppc?

It's mainly to interface with the new trac web page and svn repo that
was put in place. I bet there is away to make make another trunk so we
could have specific ppc Pkgfiles, but we need to make some movement
first.  Not to mention it' should make syncing up mirrors around the
world much easier so we dont just hit one to get ports.


> giulivo and use the official opt

a believe they are determined by per

> can you help us? :D
> i know you want join the crux ppc team... it's marvelous :D

I'd love to.  I'm going to cc this email to the crux-dev list too, to
see if we get any movement or words from the x86 guys. I think if we
make it more of a "cross platform" we can consolidate a lot of already
known issues and be able to anticipate many of them too.  If i
remember correctly Matt Housh (irc: jaeger) is willing to help beta
test some of the releases too.
(Matt if i got that wrong please tell me ;).  )

I'm excited that we are breathing new life into the project, though i
know there are compile issues they still are all just 1s and 0s.  It's
just how you look at them.

--
Jonathan Asghar
phone: 512.619.0722


From trac at crux.nu  Wed Dec 14 09:04:04 2005
From: trac at crux.nu (CRUX)
Date: Wed, 14 Dec 2005 09:04:04 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2312=3A_=5BPATCH=5Dprt-get_only_update_md5sum=2E?=
Message-ID: <057.20a62468e63c021542b950773d8db560@crux.nu>

#12: [PATCH]prt-get only update md5sum.
---------------------+------------------------------------------------------
       Id:  12       |      Status:  new                     
Component:  prt-get  |    Modified:  Wed Dec 14 10:04:04 2005
 Severity:  normal   |   Milestone:                          
 Priority:  normal   |     Version:                          
    Owner:  jw       |    Reporter:  Itn                     
---------------------+------------------------------------------------------
 If prt-get is passed the "-um",update md5sum,prt-get doesn't rebuild
 package,
 and then runs pkgadd.

 This patch add the command to update md5sum only,don't run pkgadd.

-- 
Ticket URL: <http://www.crux.nu/cgi-bin/trac.cgi/ticket/12>
CRUX <http://example.com/>
CRUX


From nick.steeves at shaw.ca  Wed Dec 14 09:29:20 2005
From: nick.steeves at shaw.ca (Nick Steeves)
Date: Wed, 14 Dec 2005 02:29:20 -0700
Subject: [clc-devel] Re: Merging of CRUX and CLC completed
Message-ID: <200512140229.25793.nick.steeves@shaw.ca>

Is it ok to abandon CVS/CLC updates from now on, and focus on crux.nu's SVN 
instead?

--
Nick
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20051214/b22bd59b/attachment.asc>

From jukka at karsikkopuu.net  Wed Dec 14 09:40:27 2005
From: jukka at karsikkopuu.net (Jukka Heino)
Date: Wed, 14 Dec 2005 11:40:27 +0200
Subject: [clc-devel] Re: Merging of CRUX and CLC completed
In-Reply-To: <200512140229.25793.nick.steeves@shaw.ca>
References: <200512140229.25793.nick.steeves@shaw.ca>
Message-ID: <439FE88B.806@karsikkopuu.net>

Nick Steeves wrote:

>Is it ok to abandon CVS/CLC updates from now on, and focus on crux.nu's SVN 
>instead?
>  
>
Yes, like the announcement said, "The old ports servers will remain 
online for a while, but won't get updates anymore." I think most of us 
have been updating the SVN repository exclusively for a while now.

// Jukka


From jw at tks6.net  Wed Dec 14 10:23:07 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Wed, 14 Dec 2005 11:23:07 +0100
Subject: [clc-devel] Re: about the new crux ports reorganization and multiplatform support :D
In-Reply-To: <57680e350512131957n159c283xcd5f680a7e3116f8@mail.gmail.com>
References: <439F52AB.5010905@libero.it> <57680e350512131957n159c283xcd5f680a7e3116f8@mail.gmail.com>
Message-ID: <20051214102307.GA25001@titanium>

Hi,

On Tue, Dec 13, 2005 at 21:57:22 -0600, Jonathan Asghar wrote:
> Hey guys...
> 
> > giulivo someone can help me to understand the new ports organization and
> > how to synch with it in the best way using cruxppc?
> It's mainly to interface with the new trac web page and svn repo that
> was put in place. I bet there is away to make make another trunk so we
> could have specific ppc Pkgfiles, but we need to make some movement
> first.
I think it's important to note that subversion nor any other VCS I
know is powerful enough for the sync use cases I know (which is x86 <->
sparc <-> x86_64).


When considering the multi-arch question, I'd like the following
requirements to be met:
1. No single master tree (i.e. not all master ports in x86); this is a
   real probem already now, as some maintainers are moving from x86 to
   x86_64
2. No untested ports distributed to users 
3. Reduce the work load for maintainers on new architectures, and for
   updates of synced packages
4. No special cases: CRUX' ports should be the same, independent of the
   architecture

In order to have a successful discussion, I think we should first make
sure that we define similar requirement everyone can live with, before
plunging into details.


However, to give those new to the subject some background, here's a list
of approaches previously discussed und formerly used in some ports
(PPC, uCRUX,  x86_64, SPARC):

----------------------
1) All in one Pkgfile (the gentoo approach)
Here, a Pkgfile would contain things like 
  if [ "$arch" = "sparc64" ]; then
  elif [ "$arch" = "ppc" ]; then
  elif [ "$arch" = "ppc" ]; then
  ...
  fi

Pros: 
- generic changes are available on every platform easily

Cons:
- ugly Pkgfiles
- in order to allow different platforms to have different versions, the
  Pkgfiles' names must include a version, and the Pkgfile must include a
  field which says "known to work on platform X"; this again makes the
  package management tools more complex

Conclusion:
There's a certain consens that this is not a CRUX-like solution


----------------------
2.1) The file override approach
With a a magic Pkgfile name (Pkgfile.$arch overrides Pkgfile), provide
a way to override Pkgfiles

Pros:
- no work required if a Pkgfile works on the target platform

Cons:
- It introduces special cases, making the package management more
  complex (think: "if there's a Pkgfile.$arch, use that one")
- The special cases make it also harder for users to understand the
  system 
- If there are both Pkgfile and Pkgfile.$arch, and the Pkgfile is
  updated, chances are the $arch maintainer has to merge the changes
  manually
- It invites to do ugly tricks (like sourcing the Pkgfile, and only
  changing vars)
- requires one master architecture
- Main disadvantage: It invites to provide untested ports from other
  architectures, and only fixing them (by providing a Pkgfile.$arch) if
  there's a problem


2.2) The repo override approach
Very similar to the above, however using separate collections to
override "broken" ports. That's what both the ppc and x86_64 ports did
in the past (not sure if that's still the case).

Pros:
- no work required if a Pkgfile works on the target platform

Cons:
- The special cases make it also harder for users to understand the
  system 
- If there are both Pkgfile and Pkgfile.$arch, and the Pkgfile is
  updated, chances are the $arch maintainer has to merge the changes
  manually
- requires one master architecture
- Main disadvantage: It invites to provide untested ports from other
  architectures, and only fixing them (by providing it in the override
  repo) if there's a problem


Conclusion:
The fact that a port shows up in $ARCH because it's in $OTHERARCH seems
wrong to me; it should be there because there's someone looking after
it. Also, this approach requires one master architecture, which seems to
become a problem as former CLC/x86 people are now working only on x86_64
(yes I mean you, Daniel! ;-)).


----------------------
3) The branches/pure VCS approach
Back in the days when we last time discussed this, several from us (me
included) considered this a viable solution: basically we'd just use
different branches in a VCS to keep track of changes. We've tried it for
CRUX/Sparc.

Pro:
- Automated merging possible
- Independent ports versions easily possible
- Only tested ports/updates get to the branch

Cons:
- requires one master architecture
- the common commands often aren't helpful for maintainers: you don't
  actually care about all diffs to a parent tree, just the ones you
  maintain.
- usually doesn't store the url of the master repo, i.e. in svn you have
  to run 'svn diff <url>' to diff from arch X to Y.

Conclusion:
It seemed like a good idea, but in real life, it didn't work out that
well, and wasn't practical. The fact that it requires one master
architecture is another major problem.


----------------------
4) the "smart merge tool" & one master port approach

Finally, this is the method I consider best. It's based on the mppm tool
which is/was used for uCRUX, and was suggested to the PPC team when we
discussed it. Not sure if they tried it.

The basic idea is that for every port in the CRUX universe (consisting
of many architectures), there's just one maintainer (aka primary
maintainer). On the other architectures, a arch maintainer just makes
sure a port works on this architecture. This has a couple of interesting
properties:

- the ports tree is quite unified. CRUX feels the very same on every
  architecture
- the primary maintainers can work on their favorite architecture (i.e.
  no master architecture needed)
- being an arch maintainer does't require as much work as being a
  primary maintainer (given that the primary maintainer does most of the
  port specific work, like following the development), which _should_
  allow even small groups of people to maintain an arch port while still
  only providing tested ports

On the technical side, I proposed to have a smart tool which can do
automated (three way) merging and track just your ports. That means the
arch maintainer would run
  $ stm sync
  $ stm diff
And see only the ports he/she maintains which were changed. 
However, this smart tool requires the ports to be on your 


Pro:
- only tested ports are distributed
- automated merging possible
- arch maintainer job causes not too much work
- clear responsibilities between maintainers
- unified ports tree
- copes will with primary maintainers on different architectures
- starting a new arch port doesn't need write access to existing
  repositories
- VCS-agnostic: arch X can use CVS, while arch Y uses Subversion.

Cons:
- requires to have the master ports locally, which right now would mean
  that a maintainer on PPC would need both x86 and x86_64 trees
- requires us to write this smart tool :-)



Obviously, the only solution which meets my initial requirements is the
last one which isn't surprising since the requirements were there
before, and #4 was my take to meet them.

However, as mentioned previously, I'd suggest we try to find a common
goals first, before going into the discussion of how to realize it.

Best regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From tilman at code-monkey.de  Wed Dec 14 21:47:25 2005
From: tilman at code-monkey.de (Tilman Sauerbeck)
Date: Wed, 14 Dec 2005 22:47:25 +0100
Subject: [clc-devel] Renaming core/pkgconfig to core/pkg-config
Message-ID: <20051214214724.GA2938@code-monkey.de>

Hi,
I'd like to rename core/pkgconfig to core/pkg-config, since the name of
the package changed upstream (see
http://pkg-config.freedesktop.org/wiki/).

pkgconfig is currently listed in ~5 ports' dependency lists, so these
could be easily updated.

However, I think pkg-config should be treated as an essential package,
since it's used by so many packages these days. That way, we could drop
it from all of the depency lists ;)

Any objections to renaming the port and removing it from any dependency
list?

Regards,
Tilman
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20051214/c0b9c35b/attachment.asc>

From trac at crux.nu  Thu Dec 15 07:10:31 2005
From: trac at crux.nu (CRUX)
Date: Thu, 15 Dec 2005 07:10:31 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2313=3A_findutils_=28core=29_broken_URL?=
In-Reply-To: <053.58a77e33a19c465e1689d4689d9727de@crux.nu>
References: <053.58a77e33a19c465e1689d4689d9727de@crux.nu>
Message-ID: <062.56e6f46b1adab59519f3a10ba22d0ea8@crux.nu>

#13: findutils (core) broken URL
--------------------+-------------------------------------------------------
       Id:  13      |      Status:  closed                  
Component:  ports   |    Modified:  Thu Dec 15 08:10:31 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:  2.0                     
    Owner:  per     |    Reporter:  tomas at famolsen.dk       
--------------------+-------------------------------------------------------
Changes (by jheino):

  * resolution:  => fixed
  * status:  new => closed

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/13>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Thu Dec 15 00:35:19 2005
From: trac at crux.nu (CRUX)
Date: Thu, 15 Dec 2005 00:35:19 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2313=3A_findutils_=28core=29_broken_URL?=
Message-ID: <053.58a77e33a19c465e1689d4689d9727de@crux.nu>

#13: findutils (core) broken URL
--------------------+-------------------------------------------------------
       Id:  13      |      Status:  new                     
Component:  ports   |    Modified:  Thu Dec 15 01:35:19 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:  2.0                     
    Owner:  per     |    Reporter:  tomas at famolsen.dk       
--------------------+-------------------------------------------------------
 the 'findutils' port version 4.2.27 (core) has a broken URL.

 In the Pkgfile a working replacement is below:
 http://ftp.gnu.org/pub/gnu/$name/$name-$version.tar.gz

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/13>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Thu Dec 15 00:33:05 2005
From: trac at crux.nu (CRUX)
Date: Thu, 15 Dec 2005 00:33:05 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=237=3A_firefox_port_version?=
In-Reply-To: <053.959fa3fb038ab5a18caa9de5d530354f@crux.nu>
References: <053.959fa3fb038ab5a18caa9de5d530354f@crux.nu>
Message-ID: <062.1b20f34453963dfad95011bf30f8cb30@crux.nu>

#7: firefox port version
-------------------+--------------------------------------------------------
       Id:  7      |      Status:  closed                  
Component:  ports  |    Modified:  Thu Dec 15 01:33:04 2005
 Severity:  major  |   Milestone:                          
 Priority:  high   |     Version:  2.0                     
    Owner:  per    |    Reporter:  tomas at famolsen.dk       
-------------------+--------------------------------------------------------
Changes (by tomas at famolsen.dk):

  * resolution:  => fixed
  * status:  new => closed

Comment:

 With the new (and very nice) "unified" ports tree, this has been fixed.

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/7>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Thu Dec 15 18:21:33 2005
From: trac at crux.nu (CRUX)
Date: Thu, 15 Dec 2005 18:21:33 -0000
Subject: [clc-devel] =?utf-8?b?UmU6IFtDUlVYXSAjODogemlwICYgdW56aXA=?=
In-Reply-To: <053.b2caee429075c6bcefb0e85b0aa397d4@crux.nu>
References: <053.b2caee429075c6bcefb0e85b0aa397d4@crux.nu>
Message-ID: <062.5fb40779651ec000f4ea2b19f274e98c@crux.nu>

#8: zip & unzip
---------------------+------------------------------------------------------
       Id:  8        |      Status:  closed                  
Component:  ports    |    Modified:  Thu Dec 15 19:21:33 2005
 Severity:  trivial  |   Milestone:                          
 Priority:  normal   |     Version:  2.0                     
    Owner:  per      |    Reporter:  anonymous               
---------------------+------------------------------------------------------
Changes (by sip):

  * resolution:  => fixed
  * status:  new => closed

Comment:

 Thanks, fixed in [384]

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/8>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Fri Dec 16 12:32:15 2005
From: trac at crux.nu (CRUX)
Date: Fri, 16 Dec 2005 12:32:15 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2314=3A_Update_port_db_repos_to_point_to_rsync_coll?=
 =?utf-8?q?ections?=
Message-ID: <053.92a6dffab8f35422c89a3921f5de46cc@crux.nu>

#14: Update port db repos to point to rsync collections
---------------------------+------------------------------------------------
       Id:  14             |      Status:  new                     
Component:  doc / website  |    Modified:  Fri Dec 16 13:32:15 2005
 Severity:  major          |   Milestone:                          
 Priority:  normal         |     Version:                          
    Owner:  per            |    Reporter:  jw                      
---------------------------+------------------------------------------------
 The ports db still points to the old base, opt and contrib.

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/14>
CRUX <http://crux.nu/>
CRUX


From predivan at ptt.yu  Sat Dec 17 02:41:48 2005
From: predivan at ptt.yu (Predrag Ivanovic)
Date: Sat, 17 Dec 2005 03:41:48 +0100
Subject: [clc-devel] rsync files ready
In-Reply-To: <439B0304.5010209@karsikkopuu.net>
References: <20051207213732.GA13683@titanium>
	<20051209000620.4a20b182.predivan@ptt.yu>
	<20051210153917.GJ6186@titanium>
	<439B0304.5010209@karsikkopuu.net>
Message-ID: <20051217034148.c272dc74.predivan@ptt.yu>

On Sat, 10 Dec 2005 18:32:04 +0200
Jukka Heino wrote:

<snip>
> Hi Pedja,
> 
> I've prepared a new driver file which falls back to plain old chdir() 
> and path validation when running as a normal user. Can you put this to 
> /etc/ports/drivers/rsync and see if it fixes your problem: 
> http://www.karsikkopuu.net/crux/misc/rsync

Works great,thanks :-)

> 
> Regards,
> Jukka

Pedja
-- 
'Cluids' - def: "Fluids having the effect of restoring or imparting
Clue. Eg; beer, coffee,etc."
                      --Dan Holdsworth 


From jue at jue.li  Fri Dec 16 13:03:08 2005
From: jue at jue.li (Juergen Daubert)
Date: Fri, 16 Dec 2005 14:03:08 +0100
Subject: [clc-devel] Renaming core/pkgconfig to core/pkg-config
In-Reply-To: <20051214214724.GA2938@code-monkey.de>
References: <20051214214724.GA2938@code-monkey.de>
Message-ID: <20051216130308.GA19662@jue.netz>

On Wed, Dec 14, 2005 at 10:47:25PM +0100, Tilman Sauerbeck wrote:
> Hi,

Hallo,

> I'd like to rename core/pkgconfig to core/pkg-config, since the name of
> the package changed upstream (see
> http://pkg-config.freedesktop.org/wiki/).
> 
> pkgconfig is currently listed in ~5 ports' dependency lists, so these
> could be easily updated.
> 
> However, I think pkg-config should be treated as an essential package,
> since it's used by so many packages these days. That way, we could drop
> it from all of the depency lists ;)
> 
> Any objections to renaming the port 

No

> and removing it from any dependency list?

Yes, at least at the moment ;-) I think we should first find a 
reasonable solution how to deal with core dependencies. 

To keep the thinks simple I'd suggest to list only runtime but _no_ 
buildtime dependencies. A exception from this can/should be glibc, 
because it's needed by every programm.

If we go for this, all the build stuff like gcc, make, libtool, sed 
etc. must be installed to build ports.

Open question here is where/how we list/mark these ports, to give 
the users an overview about these core-core ports ?


kind regards
J?rgen

-- 
Juergen Daubert  |  mailto:jue at jue.li  
Korb, Germany    |  http://jue.li/crux



From sip at varlock.com  Sat Dec 17 04:39:01 2005
From: sip at varlock.com (Simone Rota)
Date: Sat, 17 Dec 2005 05:39:01 +0100
Subject: [clc-devel] trac customization
Message-ID: <43A39665.3090600@varlock.com>

Hi,

I've started to put a bit of work into a local trac (0.91)
installation in order to provide a (still) light but a bit
more personalized appearance to the CRUX website.

Preliminary screenshot here:
http://www.varlock.com/tmp/trac091/trac01.png

See also my previous wikka proposal
http://www.varlock.com/tmp/wikka/

To the ones present at CRUXCON 2005:
any guideline/idea/preference regarding
choice of colors?

Suggestions welcome as usual.

Regards,
Simone


-- 
Simone Rota           WEB : http://www.varlock.com
Bergamo, Italy        MAIL: sip at varlock.com


From jw at tks6.net  Sat Dec 17 09:06:56 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Sat, 17 Dec 2005 10:06:56 +0100
Subject: [clc-devel] Renaming core/pkgconfig to core/pkg-config
In-Reply-To: <20051216130308.GA19662@jue.netz>
References: <20051214214724.GA2938@code-monkey.de> <20051216130308.GA19662@jue.netz>
Message-ID: <20051217090656.GA25966@titanium>

Hi,

On Fri, Dec 16, 2005 at 14:03:08 +0100, Juergen Daubert wrote:
> On Wed, Dec 14, 2005 at 10:47:25PM +0100, Tilman Sauerbeck wrote:
> > Hi,
> 
> Hallo,
> 
> > I'd like to rename core/pkgconfig to core/pkg-config, since the name of
> > the package changed upstream (see
> > http://pkg-config.freedesktop.org/wiki/).
Sounds reasonable.

[...]
> > Any objections to renaming the port 
> 
> No
No objections

> 
> > and removing it from any dependency list?
> 
> Yes, at least at the moment ;-) I think we should first find a 
> reasonable solution how to deal with core dependencies. 
> 
> To keep the thinks simple I'd suggest to list only runtime but _no_ 
> buildtime dependencies. A exception from this can/should be glibc, 
> because it's needed by every programm.
Same for gcc which is currently needed by all C++ programs unless
linked statically.

> If we go for this, all the build stuff like gcc, make, libtool, sed 
> etc. must be installed to build ports.
> 
> Open question here is where/how we list/mark these ports, to give 
> the users an overview about these core-core ports ?
At CRUXCon, we planned to:
- integrate this list in pkgutils
- give no option in 'setup' to not install those
- add a warning to pkgrm when you try to remove one of those (it should
  be possible, but require some additional argument to force it).

I'd say we start by compiling a list on the Wiki, and link it from the
package guidelines (and maybe the FAQ) once we get the impression it's
fine.

Best regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From jasonthomasdolan at yahoo.com  Sat Dec 17 14:04:20 2005
From: jasonthomasdolan at yahoo.com (Jay Dolan)
Date: Sat, 17 Dec 2005 06:04:20 -0800 (PST)
Subject: [clc-devel] trac customization
In-Reply-To: <43A39665.3090600@varlock.com>
Message-ID: <20051217140420.59531.qmail@web32901.mail.mud.yahoo.com>


--- Simone Rota <sip at varlock.com> wrote:

> Hi,

Hey :)

> See also my previous wikka proposal
> http://www.varlock.com/tmp/wikka/
> 
> To the ones present at CRUXCON 2005:
> any guideline/idea/preference regarding
> choice of colors?
> 

Well, I don't know why our opinions would carry more
weight than any of the other maintainers, but I
certainly like your wikka color scheme very much.

Jay Dolan
Software Engineer, Systems Analyst
Windmill Cycles, Inc.
508.999.4000

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


From jw at tks6.net  Sat Dec 17 14:24:58 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Sat, 17 Dec 2005 15:24:58 +0100
Subject: [clc-devel] trac customization
In-Reply-To: <43A39665.3090600@varlock.com>
References: <43A39665.3090600@varlock.com>
Message-ID: <20051217142458.GD6090@titanium>

Hi Simone,

On Sat, Dec 17, 2005 at 05:39:01 +0100, Simone Rota wrote:
> Hi,
> 
> I've started to put a bit of work into a local trac (0.91)
> installation in order to provide a (still) light but a bit
> more personalized appearance to the CRUX website.
> 
> Preliminary screenshot here:
> http://www.varlock.com/tmp/trac091/trac01.png

Looks nice. The only thing I'd prefer from the current site is the
navbar, at least the currently highlighted trac section:
  http://jw.tks6.net/files/crux/trac.png
The current navbar (maybe minus the shadow like on the port db page) is
something I quite like :-).

I remember that Per wasn't too fond of the all-brown Wikka design; to me
the trac design looks more balanced though, with the red links, so if
it's ready to be used for our page (that basically means that the wiki
navigation on the left is there as well) I'd suggest we switch our
installation on crux.nu, and see what the reactions are.

We still have to update trac on crux.nu though, contrib/trac is still at
0.8... 

Regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From sip at varlock.com  Sat Dec 17 14:26:23 2005
From: sip at varlock.com (Simone Rota)
Date: Sat, 17 Dec 2005 15:26:23 +0100
Subject: [clc-devel] trac customization
In-Reply-To: <20051217140420.59531.qmail@web32901.mail.mud.yahoo.com>
References: <20051217140420.59531.qmail@web32901.mail.mud.yahoo.com>
Message-ID: <43A4200F.1040602@varlock.com>

On 12/17/05 15:04 Jay Dolan wrote:
> Hey :)

Hey Jay,

>>To the ones present at CRUXCON 2005:
>>any guideline/idea/preference regarding
>>choice of colors?
> 
> Well, I don't know why our opinions would carry more
> weight than any of the other maintainers,

Sorry, bad wording of mine: I was simply asking if
there's been some discussion about colors during CC05.

> but I
> certainly like your wikka color scheme very much.

I liked that too, maybe a bit less brownish.

Regards,
Simone


-- 
Simone Rota           WEB : http://www.varlock.com
Bergamo, Italy        MAIL: sip at varlock.com


From trac at crux.nu  Sat Dec 17 19:43:19 2005
From: trac at crux.nu (CRUX)
Date: Sat, 17 Dec 2005 19:43:19 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2315=3A_Nmap_new_version_out?=
Message-ID: <053.8535c98b1773fb8a41f0aae2f0a9f664@crux.nu>

#15: Nmap new version out
---------------------+------------------------------------------------------
       Id:  15       |      Status:  new                     
Component:  ports    |    Modified:  Sat Dec 17 20:43:19 2005
 Severity:  trivial  |   Milestone:                          
 Priority:  normal   |     Version:  2.0                     
    Owner:  per      |    Reporter:  anonymous               
---------------------+------------------------------------------------------
 There is a new version (3.95) of nmap.

-- 
Ticket URL: <http://www.crux.nu/cgi-bin/trac.cgi/ticket/15>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Sat Dec 17 20:18:37 2005
From: trac at crux.nu (CRUX)
Date: Sat, 17 Dec 2005 20:18:37 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2315=3A_Nmap_new_version_out?=
In-Reply-To: <053.8535c98b1773fb8a41f0aae2f0a9f664@crux.nu>
References: <053.8535c98b1773fb8a41f0aae2f0a9f664@crux.nu>
Message-ID: <062.06c5860d17da19a37827bb0c137d3e92@crux.nu>

#15: Nmap new version out
---------------------+------------------------------------------------------
       Id:  15       |      Status:  closed                  
Component:  ports    |    Modified:  Sat Dec 17 21:18:37 2005
 Severity:  trivial  |   Milestone:                          
 Priority:  normal   |     Version:  2.0                     
    Owner:  per      |    Reporter:  anonymous               
---------------------+------------------------------------------------------
Changes (by sip):

  * resolution:  => fixed
  * status:  new => closed

Comment:

 Thanks, updated in [390]

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/15>
CRUX <http://crux.nu/>
CRUX


From jw at tks6.net  Sun Dec 18 10:22:13 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Sun, 18 Dec 2005 11:22:13 +0100
Subject: [clc-devel] advocates for new contrib members
Message-ID: <20051218102213.GA26293@titanium>

Hi,

It seems there are more and more people who want to join the new
contrib, and I think it would be a good idea so start a similar model as
we had at CLC for maintainers:
1. in order to join contrib, you have to find someone to advacate for
   you
2. the advocate is responsible for helping the candidate to get
   started, and should observe him for a while to make sure he's doing a
   good job

Everyone who's part of 'contrib' already is invited to be an advocate
(assuming that he's been part of the system for some time, like one
month or so).

Would that make sense? If not, who's responsible to decide who should
join?

Regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From centericq at ukr.net  Sun Dec 18 11:28:18 2005
From: centericq at ukr.net (Oleksiy V. Khilkevich)
Date: Sun, 18 Dec 2005 13:28:18 +0200
Subject: [clc-devel] advocates for new contrib members
In-Reply-To: <20051218102213.GA26293@titanium>
References: <20051218102213.GA26293@titanium>
Message-ID: <op.s1y8tgjcmta8g5@hermes>

On Sun, 18 Dec 2005 12:22:13 +0200, Johannes Winkelmann <jw at tks6.net>  
wrote:

> Hi,

Hey!

>
> It seems there are more and more people who want to join the new
> contrib, and I think it would be a good idea so start a similar model as
> we had at CLC for maintainers:
> 1. in order to join contrib, you have to find someone to advacate for
>    you
> 2. the advocate is responsible for helping the candidate to get
>    started, and should observe him for a while to make sure he's doing a
>    good job
>
> Everyone who's part of 'contrib' already is invited to be an advocate
thanks ;)

> (assuming that he's been part of the system for some time, like one
> month or so).

that should be ok!

> Would that make sense? If not, who's responsible to decide who should
> join?

Core maintainers I think, but they've already enough job, so your idea is  
more than pretty :) That'll make a contrib more united, I thinnk.
Advocate may only help to start properly or may support a newbie sometime.

That is what about _really_ new to CLC.
Those who allready have their own repo, have a right to be added to new  
contrib. They've allready passed one test anyway.

-- 
kind regards,
Oleksiy V. Khilkevich      [GRIM-UANIC]  [GRIM-RIPE]

Please avoid sending me Word, Excel or PowerPoint attachments.
Use plain text, HTML or PDF instead.
http://www.gnu.org/philosophy/no-word-attachments.html


From sip at varlock.com  Sun Dec 18 16:30:50 2005
From: sip at varlock.com (Simone Rota)
Date: Sun, 18 Dec 2005 17:30:50 +0100
Subject: [clc-devel] advocates for new contrib members
In-Reply-To: <20051218102213.GA26293@titanium>
References: <20051218102213.GA26293@titanium>
Message-ID: <43A58EBA.20502@varlock.com>

On 12/18/05 11:22 Johannes Winkelmann wrote:
> 1. in order to join contrib, you have to find someone to advacate for
>    you
> 2. the advocate is responsible for helping the candidate to get
>    started, and should observe him for a while to make sure he's doing a
>    good job
> 
> Would that make sense? If not, who's responsible to decide who should
> join?

Sounds ok.

Since the new contrib is quite new, I suggest we (CLC)
directly take care of partecipation requests for a short
period.

Then, when the whole thing assumes a well defined shape,
we can either employ an advocacy-based method or
delegate submission handling to one or more
elder new-contrib members, providing there is some
voluntary.

Maybe the 2nd solution is easier both for contributors
and clc, since it provides one or more contacts that
can be a bridge with core developers.

Regards,
Simone

-- 
Simone Rota           WEB : http://www.varlock.com
Bergamo, Italy        MAIL: sip at varlock.com


From trac at crux.nu  Sun Dec 18 22:34:11 2005
From: trac at crux.nu (CRUX)
Date: Sun, 18 Dec 2005 22:34:11 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2316=3A_The_new_guys_need_to_know_about_community?=
 =?utf-8?q?=2E?=
Message-ID: <053.57a00136d46af8e65afe1c1299292a07@crux.nu>

#16: The new guys need to know about community.
---------------------------+------------------------------------------------
       Id:  16             |      Status:  new                     
Component:  doc / website  |    Modified:  Sun Dec 18 23:34:11 2005
 Severity:  major          |   Milestone:                          
 Priority:  high           |     Version:                          
    Owner:  per            |    Reporter:  centericq at ukr.net       
---------------------------+------------------------------------------------
 This is a VERY important thing to add!
 If this is not the most important thing in the universe - sorry for boring
 you!

 Johannes have a great map of CLC! Why it is not in the Links section?
 Here is a link to save your time:
 http://jw.tks6.net/files/crux/cruxmap.html

-- 
Ticket URL: <http://www.crux.nu/cgi-bin/trac.cgi/ticket/16>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Mon Dec 19 01:55:48 2005
From: trac at crux.nu (CRUX)
Date: Mon, 19 Dec 2005 01:55:48 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2317=3A_ethereal=3A_broken_source_URL?=
Message-ID: <053.e71469f9116ffc94ccc2df0bfc90975f@crux.nu>

#17: ethereal: broken source URL
--------------------+-------------------------------------------------------
       Id:  17      |      Status:  new                     
Component:  ports   |    Modified:  Mon Dec 19 02:55:48 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  per     |    Reporter:  sten                    
--------------------+-------------------------------------------------------
 ethereal's source URL starts at 20 KB/s, then bottoms out to nothing, and
 sometimes comes back to 200 bytes/s, sometimes doesn't.  The source URL is
 unreliable, so in my opinion, it should be switched to ethereal's
 sourceforge mirror.

 --- Pkgfile (revision 404)
 +++ Pkgfile (working copy)
 @@ -8,7 +8,7 @@
  name=ethereal
  version=0.10.13
  release=1
 -source=(ftp://ftp.ethereal.com/pub/ethereal/all-
 versions/$name-$version.tar.bz2)
 +source=(http://dl.sourceforge.net/sourceforge/$name/$name-$version.tar.bz2)

  build () {
     cd $name-$version

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/17>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Mon Dec 19 10:25:35 2005
From: trac at crux.nu (CRUX)
Date: Mon, 19 Dec 2005 10:25:35 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2317=3A_ethereal=3A_broken_source_URL?=
In-Reply-To: <053.e71469f9116ffc94ccc2df0bfc90975f@crux.nu>
References: <053.e71469f9116ffc94ccc2df0bfc90975f@crux.nu>
Message-ID: <062.3e020f3062ed6761018d3da3da8ed274@crux.nu>

#17: ethereal: broken source URL
--------------------+-------------------------------------------------------
       Id:  17      |      Status:  closed                  
Component:  ports   |    Modified:  Mon Dec 19 11:25:35 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  per     |    Reporter:  sten                    
--------------------+-------------------------------------------------------
Changes (by tilman):

  * resolution:  => fixed
  * status:  new => closed

Comment:

 Mmhkay, fixed :]

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/17>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Mon Dec 19 11:42:27 2005
From: trac at crux.nu (CRUX)
Date: Mon, 19 Dec 2005 11:42:27 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2316=3A_The_new_guys_need_to_know_about_commu?=
 =?utf-8?q?nity=2E?=
In-Reply-To: <053.57a00136d46af8e65afe1c1299292a07@crux.nu>
References: <053.57a00136d46af8e65afe1c1299292a07@crux.nu>
Message-ID: <062.702ac02bf9cb9b531e5846d2714fff24@crux.nu>

#16: The new guys need to know about community.
---------------------------+------------------------------------------------
       Id:  16             |      Status:  new                     
Component:  doc / website  |    Modified:  Mon Dec 19 12:42:27 2005
 Severity:  major          |   Milestone:                          
 Priority:  high           |     Version:                          
    Owner:  per            |    Reporter:  centericq at ukr.net       
---------------------------+------------------------------------------------
Comment (by bd2):

 btw, the map don't work in Konqueror (from KDE-3.5) :-(

-- 
Ticket URL: <http://www.crux.nu/cgi-bin/trac.cgi/ticket/16>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Mon Dec 19 11:44:25 2005
From: trac at crux.nu (CRUX)
Date: Mon, 19 Dec 2005 11:44:25 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2316=3A_The_new_guys_need_to_know_about_commu?=
 =?utf-8?q?nity=2E?=
In-Reply-To: <053.57a00136d46af8e65afe1c1299292a07@crux.nu>
References: <053.57a00136d46af8e65afe1c1299292a07@crux.nu>
Message-ID: <062.9b765fd4e54643d2a05aa554803cc4fd@crux.nu>

#16: The new guys need to know about community.
---------------------------+------------------------------------------------
       Id:  16             |      Status:  new                     
Component:  doc / website  |    Modified:  Mon Dec 19 12:44:25 2005
 Severity:  major          |   Milestone:                          
 Priority:  high           |     Version:                          
    Owner:  per            |    Reporter:  centericq at ukr.net       
---------------------------+------------------------------------------------
Comment (by bd2):

 Oops, forgot. The error is:

 Error: http://jw.tks6.net/files/crux/cruxmap.html: ReferenceError: Can't
 find variable: GMap

-- 
Ticket URL: <http://www.crux.nu/cgi-bin/trac.cgi/ticket/16>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Mon Dec 19 12:00:50 2005
From: trac at crux.nu (CRUX)
Date: Mon, 19 Dec 2005 12:00:50 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2316=3A_The_new_guys_need_to_know_about_commu?=
 =?utf-8?q?nity=2E?=
In-Reply-To: <053.57a00136d46af8e65afe1c1299292a07@crux.nu>
References: <053.57a00136d46af8e65afe1c1299292a07@crux.nu>
Message-ID: <062.2dfbfcb64eb78ef973a70cc13ff7784d@crux.nu>

#16: The new guys need to know about community.
---------------------------+------------------------------------------------
       Id:  16             |      Status:  new                     
Component:  doc / website  |    Modified:  Mon Dec 19 13:00:50 2005
 Severity:  minor          |   Milestone:                          
 Priority:  high           |     Version:                          
    Owner:  per            |    Reporter:  centericq at ukr.net       
---------------------------+------------------------------------------------
Changes (by jw):

  * severity:  major => minor

Comment:

 Regarding Konqueror: Feel free to report that to either KDE or Google

 Changing this to "minor", since we really have more important issues right
 now

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/16>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Mon Dec 19 12:01:42 2005
From: trac at crux.nu (CRUX)
Date: Mon, 19 Dec 2005 12:01:42 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2316=3A_The_new_guys_need_to_know_about_commu?=
 =?utf-8?q?nity=2E?=
In-Reply-To: <053.57a00136d46af8e65afe1c1299292a07@crux.nu>
References: <053.57a00136d46af8e65afe1c1299292a07@crux.nu>
Message-ID: <062.cee11b4f53dda30558b9e3501129c348@crux.nu>

#16: The new guys need to know about community.
---------------------------+------------------------------------------------
       Id:  16             |      Status:  new                     
Component:  doc / website  |    Modified:  Mon Dec 19 13:01:42 2005
 Severity:  minor          |   Milestone:                          
 Priority:  low            |     Version:                          
    Owner:  per            |    Reporter:  centericq at ukr.net       
---------------------------+------------------------------------------------
Changes (by jw):

  * priority:  high => low

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/16>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Mon Dec 19 12:13:19 2005
From: trac at crux.nu (CRUX)
Date: Mon, 19 Dec 2005 12:13:19 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2316=3A_The_new_guys_need_to_know_about_commu?=
 =?utf-8?q?nity=2E?=
In-Reply-To: <053.57a00136d46af8e65afe1c1299292a07@crux.nu>
References: <053.57a00136d46af8e65afe1c1299292a07@crux.nu>
Message-ID: <062.d49ca5bf4a7545585c4e7fa52147fbfa@crux.nu>

#16: The new guys need to know about community.
---------------------------+------------------------------------------------
       Id:  16             |      Status:  new                     
Component:  doc / website  |    Modified:  Mon Dec 19 13:13:19 2005
 Severity:  minor          |   Milestone:                          
 Priority:  low            |     Version:                          
    Owner:  per            |    Reporter:  centericq at ukr.net       
---------------------------+------------------------------------------------
Comment (by bd2):

 > Feel free to report that to either KDE or Google

 stupid google. Hate them for that. Konqueror with User-Agent set to
 "Safari" works great.

-- 
Ticket URL: <http://www.crux.nu/cgi-bin/trac.cgi/ticket/16>
CRUX <http://crux.nu/>
CRUX


From jw at tks6.net  Mon Dec 19 12:55:09 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Mon, 19 Dec 2005 13:55:09 +0100
Subject: [clc-devel] Multi-platform ports management
Message-ID: <20051219125509.GA4009@titanium>

Hi there,

I know that the PPC team as well as Peter Banks who took over the sparc
port are reading this, so let's start discussion issues related to ports
management. I think it's important to first agree on a goal for this,
and cover the technical details later if there's a consensus.
Also let me state that this is my personal opinion only, not the one of
CLC or the CRUX project.

My goal is to have a system with the following properties:

1. The user only gets ports tested on this platform
2. The user gets the same system on every system
3. No single master tree (as it is now)
4. The package management stays as easy as it is now (i.e. no special
   cases)
5. Allow to start ports to new architectures easily, without requiring
   too many developers

Is this something we can agree on?

Kind regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From jw at tks6.net  Mon Dec 19 13:01:57 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Mon, 19 Dec 2005 14:01:57 +0100
Subject: [clc-devel] Multi-platform ports management
In-Reply-To: <20051219125509.GA4009@titanium>
References: <20051219125509.GA4009@titanium>
Message-ID: <20051219130157.GA3315@titanium>

Hi,

On Mon, Dec 19, 2005 at 13:55:09 +0100, Johannes Winkelmann wrote:
> Hi there,
[...] 
> My goal is to have a system with the following properties:
> 
> 1. The user only gets ports tested on this platform
> 2. The user gets the same system on every system
That should of course be: The user gets the same system on every
architecture.

Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From giulivo.navigante at katamail.com  Mon Dec 19 16:23:48 2005
From: giulivo.navigante at katamail.com (Giulivo Navigante)
Date: Mon, 19 Dec 2005 17:23:48 +0100
Subject: [clc-devel] Multi-platform ports management
In-Reply-To: <20051219125509.GA4009@titanium>
References: <20051219125509.GA4009@titanium>
Message-ID: <43A6DE94.2060005@katamail.com>

Johannes Winkelmann wrote:
> Hi there,
> 
> I know that the PPC team as well as Peter Banks who took over the sparc
> port are reading this, so let's start discussion issues related to ports
> management. I think it's important to first agree on a goal for this,
> and cover the technical details later if there's a consensus.
> Also let me state that this is my personal opinion only, not the one of
> CLC or the CRUX project.
> 
> My goal is to have a system with the following properties:
> 
> 1. The user only gets ports tested on this platform

i think this is very difficult to realize and not useful... infact $ARCH 
developers should perform a test for every known port and this is not 
acceptable specially for little communities

if the $ARCH community can instead use the "master" ports tree (it 
should be ok in the 90% of cases), the $ARCH developers can focalize the 
attention in the porting and the rimanent 10% of buggy cases

> 2. The user gets the same system on every system

ok for me

> 3. No single master tree (as it is now)

see point 1

> 4. The package management stays as easy as it is now (i.e. no special
>    cases)

ok for me

> 5. Allow to start ports to new architectures easily, without requiring
>    too many developers

see point 1

> Is this something we can agree on?

regards
-- 
Giulivo Navigante
http://cruxppc.sunsite.dk


From jw at tks6.net  Mon Dec 19 16:41:25 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Mon, 19 Dec 2005 17:41:25 +0100
Subject: [clc-devel] Multi-platform ports management
In-Reply-To: <43A6DE94.2060005@katamail.com>
References: <20051219125509.GA4009@titanium> <43A6DE94.2060005@katamail.com>
Message-ID: <20051219164125.GA6869@titanium>

Hi,

On Mon, Dec 19, 2005 at 17:23:48 +0100, Giulivo Navigante wrote:
> Johannes Winkelmann wrote:
[...]
> >My goal is to have a system with the following properties:
> >
> >1. The user only gets ports tested on this platform
> 
> i think this is very difficult to realize and not useful... infact $ARCH 
> developers should perform a test for every known port and this is not 
> acceptable specially for little communities
I'm not quite sure here. Adapting the base and opt ports for CRUX/SPARC
took me only a few days, and I did it alone. In real life, those changes
don't happen all at the same time, so after the initial port, it's like
1 or 2 updates per day.

What makes you believe it's not acceptable?

Are you currently using any tools to sync your trees with the x86 one
for those ports which require changes?


> if the $ARCH community can instead use the "master" ports tree (it 
> should be ok in the 90% of cases)
However, this only works if there's a single master tree. We from the
x86 port lost a good number of important projects due to Daniel's move
to x86_64, and chances are this will happen more often in the future. I
don't think that a model with a single master tree is realistic for the
future, considering the size of our team.

Regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From giulivo.navigante at katamail.com  Mon Dec 19 17:54:01 2005
From: giulivo.navigante at katamail.com (Giulivo Navigante)
Date: Mon, 19 Dec 2005 18:54:01 +0100
Subject: [clc-devel] Multi-platform ports management
In-Reply-To: <20051219164125.GA6869@titanium>
References: <20051219125509.GA4009@titanium> <43A6DE94.2060005@katamail.com> <20051219164125.GA6869@titanium>
Message-ID: <43A6F3B9.1070406@katamail.com>

Johannes Winkelmann wrote:
> Hi,
> 
> I'm not quite sure here. Adapting the base and opt ports for CRUX/SPARC
> took me only a few days, and I did it alone. In real life, those changes
> don't happen all at the same time, so after the initial port, it's like
> 1 or 2 updates per day.
 >
> What makes you believe it's not acceptable?

not acceptable for little communities because they remains 1 or 2 
updates per day if the number of ports remains of little entity, as it 
is now ... in order consider that "tests" can be made only by $ARCH 
developers

> Are you currently using any tools to sync your trees with the x86 one
> for those ports which require changes?

no, we've in mind to have /usr/ports/x86 and /usr/ports/ppc
in the second tree will exists only the ports that needs to be modified 
on ppc

>>if the $ARCH community can instead use the "master" ports tree (it 
>>should be ok in the 90% of cases)
> 
> However, this only works if there's a single master tree. We from the
> x86 port lost a good number of important projects due to Daniel's move
> to x86_64, and chances are this will happen more often in the future. I
> don't think that a model with a single master tree is realistic for the
> future, considering the size of our team.

our idea instead is based on a "master" single tree where we should 
merge forces :P
-- 
Giulivo Navigante
http://cruxppc.sunsite.dk


From daniel at danm.de  Mon Dec 19 17:57:07 2005
From: daniel at danm.de (Daniel Mueller)
Date: Mon, 19 Dec 2005 18:57:07 +0100
Subject: [clc-devel] Multi-platform ports management
In-Reply-To: <43A6DE94.2060005@katamail.com>
References: <20051219125509.GA4009@titanium> <43A6DE94.2060005@katamail.com>
Message-ID: <200512191857.07350.daniel@danm.de>

On Monday 19 December 2005 17:23, Giulivo Navigante wrote:
> i think this is very difficult to realize and not useful... infact $ARCH
> developers should perform a test for every known port and this is not
> acceptable specially for little communities

I don't agree with you in this point. I had to test EVERY particular port for 
x86_64 because there were bugs sometimes even if the source compiled cleanly 
(e.g. 'bc' -> sporadic segmentation faults, 'irssi 0.8.9' -> connect (tcp) 
errors, [..]). 

It's not our job to provide as much ports as possible. A small, good running 
set of ports should be sufficient for the most users.

bye, danm

-- 
Daniel Mueller
Berlin, Germany         OpenPGP: 1024D/E4F4383A


From jjasghar at gmail.com  Mon Dec 19 18:01:15 2005
From: jjasghar at gmail.com (Jonathan Asghar)
Date: Mon, 19 Dec 2005 12:01:15 -0600
Subject: [clc-devel] Multi-platform ports management
In-Reply-To: <43A6F3B9.1070406@katamail.com>
References: <20051219125509.GA4009@titanium> <43A6DE94.2060005@katamail.com>
	 <20051219164125.GA6869@titanium> <43A6F3B9.1070406@katamail.com>
Message-ID: <57680e350512191001j74978fc5q426865ff726695f6@mail.gmail.com>

Hey guys...i think i'd like to put my $0.02 in now.

> > I'm not quite sure here. Adapting the base and opt ports for CRUX/SPARC
> > took me only a few days, and I did it alone. In real life, those changes
> > don't happen all at the same time, so after the initial port, it's like
> > 1 or 2 updates per day.
>  >
> > What makes you believe it's not acceptable?
>
> not acceptable for little communities because they remains 1 or 2
> updates per day if the number of ports remains of little entity, as it
> is now ... in order consider that "tests" can be made only by $ARCH
> developers

I have to agree with Johannes here, the testing should happen on the
dev side and there should be some type of "QOS" control for a port
that we produce.

>
> > Are you currently using any tools to sync your trees with the x86 one
> > for those ports which require changes?
>
> no, we've in mind to have /usr/ports/x86 and /usr/ports/ppc
> in the second tree will exists only the ports that needs to be modified
> on ppc
>
> >>if the $ARCH community can instead use the "master" ports tree (it
> >>should be ok in the 90% of cases)

not to throw a wrench in this discussion, but i did the server
migration off crux.nu for the hell of it on the ppc install that i did
last night, and so far every port i've tried works fine.  I even built
firefox 1.5 with the deps from Matts gnome repo and it worked like a
charm.  I know i'm going to run into some problems eventually, but
hell, i'm telling yall that maybe the best was would be to just submit
patches to the tree for ppc/sparc? use the repos and create tools for
the two other $ARCHS to patch them to make sure the work?

-j

--
Jonathan Asghar
phone: 512.619.0722


From daniel at danm.de  Mon Dec 19 18:14:04 2005
From: daniel at danm.de (Daniel Mueller)
Date: Mon, 19 Dec 2005 19:14:04 +0100
Subject: [clc-devel] Re: Multi-platform ports management
In-Reply-To: <20051219125509.GA4009@titanium>
References: <20051219125509.GA4009@titanium>
Message-ID: <200512191914.04334.daniel@danm.de>

On Monday 19 December 2005 13:55, Johannes Winkelmann wrote:

> 1. The user only gets ports tested on this platform

yep.

> 2. The user gets the same system on every system

This is not possible. Lilo doesn't work on all platforms and devfs was thrown 
out of the kernel source tree. Library paths differ from $arch to $arch and 
configuration files sometimes need special adjustments.

> 3. No single master tree (as it is now)

Mhh, a separated ports tree would be nice. A mechanism which prevents me from 
accidently touching x86 ports :-)

> 4. The package management stays as easy as it is now (i.e. no special
>    cases)

:-( 

I'm not allowed to write a 'patch-helper' function in special cases? It's 
annoying to write fifteen 'patch -p1 < $SRC/no1.patch' lines. 

> 5. Allow to start ports to new architectures easily, without requiring
>    too many developers

What do you mean?

bye, danm

-- 
Daniel Mueller
Berlin, Germany         OpenPGP: 1024D/E4F4383A


From jw at tks6.net  Mon Dec 19 18:15:07 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Mon, 19 Dec 2005 19:15:07 +0100
Subject: [clc-devel] Multi-platform ports management
In-Reply-To: <43A6F3B9.1070406@katamail.com>
References: <20051219125509.GA4009@titanium> <43A6DE94.2060005@katamail.com> <20051219164125.GA6869@titanium> <43A6F3B9.1070406@katamail.com>
Message-ID: <20051219181505.GA21003@titanium>

On Mon, Dec 19, 2005 at 18:54:01 +0100, Giulivo Navigante wrote:
> Johannes Winkelmann wrote:
> >Hi,
> >
> >I'm not quite sure here. Adapting the base and opt ports for CRUX/SPARC
> >took me only a few days, and I did it alone. In real life, those changes
> >don't happen all at the same time, so after the initial port, it's like
> >1 or 2 updates per day.
> >
> >What makes you believe it's not acceptable?
> 
> not acceptable for little communities because they remains 1 or 2 
> updates per day if the number of ports remains of little entity, as it 
> is now ... in order consider that "tests" can be made only by $ARCH 
> developers
Okay. With a community of three developers, that means that one will
have to update ~5 ports every week with 2 updates per day. I definitely
expect the x86 maintainers to be able to cope with this kind of load,
and they're even required to follow the mailing lists etc. If we assume
the ports build fine, that's maybe an average of half an hour per port,
which is 2.5 h per week.
How much work/time are you guys willing to spend on this project?

> >Are you currently using any tools to sync your trees with the x86 one
> >for those ports which require changes?
> 
> no, we've in mind to have /usr/ports/x86 and /usr/ports/ppc
> in the second tree will exists only the ports that needs to be modified 
> on ppc
No, I mean those ports which are modified; how do you sync those?


> >>if the $ARCH community can instead use the "master" ports tree (it 
> >>should be ok in the 90% of cases)
> >
> >However, this only works if there's a single master tree. We from the
> >x86 port lost a good number of important projects due to Daniel's move
> >to x86_64, and chances are this will happen more often in the future. I
> >don't think that a model with a single master tree is realistic for the
> >future, considering the size of our team.
> 
> our idea instead is based on a "master" single tree where we should 
> merge forces :P
I'm not quite sure I understand you here. You want one tree which
supports all architecures? Like gentoo, with if [ "$arch" = "ppc" ]; ...
elif ... elif ... fi all over the Pkgfiles?

Regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From jw at tks6.net  Mon Dec 19 18:32:06 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Mon, 19 Dec 2005 19:32:06 +0100
Subject: [clc-devel] Re: Multi-platform ports management
In-Reply-To: <200512191914.04334.daniel@danm.de>
References: <20051219125509.GA4009@titanium> <200512191914.04334.daniel@danm.de>
Message-ID: <20051219183206.GB21003@titanium>

Hi Daniel,

On Mon, Dec 19, 2005 at 19:14:04 +0100, Daniel Mueller wrote:
> On Monday 19 December 2005 13:55, Johannes Winkelmann wrote:
> 
> > 1. The user only gets ports tested on this platform
> 
> yep.
> 
> > 2. The user gets the same system on every system
> 
> This is not possible. Lilo doesn't work on all platforms and devfs was thrown 
> out of the kernel source tree. Library paths differ from $arch to $arch and 
> configuration files sometimes need special adjustments.
Oh, you took my words too literarily.

What I meant is that it's /usr/ports/{core,opt,contrib} on every arch
for example.
The PPC team seems to be in favour of a /usr/ports/{x86,ppc} special
solution on their system; it's more this kind of things I mean.

Of course, ports have to be chosen per plaform, changes have to be made
for pathes and so an. As for devfs, that's not really an issue of archs;
if we had sync'ed released, all archs would have udev.

I would however be in favour that all archs have more or less the same
features in their ports; as a silly example, let's say mplayer is build
without GUI on all archs. However, I think that's already the case now.

> > 3. No single master tree (as it is now)
> 
> Mhh, a separated ports tree would be nice. A mechanism which prevents me from 
> accidently touching x86 ports :-)
It will also allow us to distribute the primary maintenance (following
the mailing lists, checking for announcements and conflicts) to several
architectures, making it easier to maintain a port on a another
architecture (let's say I maintain libxml2 on sparc which you maintain
on x86_64; in this case, I can simply follow your port, but not the
libxml2 mailing list).


> > 4. The package management stays as easy as it is now (i.e. no special
> >    cases)
> 
> :-( 
> 
> I'm not allowed to write a 'patch-helper' function in special cases? It's 
> annoying to write fifteen 'patch -p1 < $SRC/no1.patch' lines. 
Peanuts :-). What I meant here was that it's not something like:

If you execute pkgmk, it will
1. check for Pkgfile.$arch, and build it if it's there
2. choose Pkgfile otherwise
and the same for md5sum and footprint

That's what I meant with special cases for the package management. I'm
mainly against this since the users who look for an error in a build
will have to go through the same process: "where's the error, is it in
Pkgfile.$arch, or in Pkgfile...".

> > 5. Allow to start ports to new architectures easily, without requiring
> >    too many developers
> 
> What do you mean?
Basically two things.
1. that in order to start an architecture which only reuses ports from
the other architectures and requires little work (i.e. provide a sync
tool which is adapted to our needs).

2. that the setup allows to start working on it without requiring
special accounts or rights. The typical situation would be to have a
central SVN repo, where everything's developed and users need write
permissions to start working on a new archtecture.


Well, I guess my initial mail wasn't too clear then :-). Sorry for that,
and thanks for your questions, I hope I could clear up my previous mail
a bit.
Kind regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From daniel at danm.de  Mon Dec 19 19:00:31 2005
From: daniel at danm.de (Daniel Mueller)
Date: Mon, 19 Dec 2005 20:00:31 +0100
Subject: [clc-devel] Re: Multi-platform ports management
In-Reply-To: <20051219183206.GB21003@titanium>
References: <20051219125509.GA4009@titanium> <200512191914.04334.daniel@danm.de> <20051219183206.GB21003@titanium>
Message-ID: <200512192000.31347.daniel@danm.de>

On Monday 19 December 2005 19:32, Johannes Winkelmann wrote:

> > > 3. No single master tree (as it is now)
> >
> > Mhh, a separated ports tree would be nice. A mechanism which prevents me
> > from accidently touching x86 ports :-)
>
> It will also allow us to distribute the primary maintenance (following
> the mailing lists, checking for announcements and conflicts) [..]

I don't know much about SVN yet - is it possible to create a branch for this 
or would we get our 'own' repository (one per architecture).

Giulivo:
What do you think? My ports tree (AMD64) would look like this:

/usr/ports/
		base
		opt
		compat32	(32bit ports)
		contrib

+ 

/usr/ports-x86/
		base
		opt
		contrib

The /usr/ports-x86 directory is NOT activated in /etc/prt-get.conf (not even 
mentioned!). It's just there for the users cause we can't provide all x86 
ports.

bye, danm

-- 
Daniel Mueller
Berlin, Germany         OpenPGP: 1024D/E4F4383A


From jw at tks6.net  Mon Dec 19 19:06:55 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Mon, 19 Dec 2005 20:06:55 +0100
Subject: [clc-devel] Re: Multi-platform ports management
In-Reply-To: <200512192000.31347.daniel@danm.de>
References: <20051219125509.GA4009@titanium> <200512191914.04334.daniel@danm.de> <20051219183206.GB21003@titanium> <200512192000.31347.daniel@danm.de>
Message-ID: <20051219190655.GA2301@titanium>

Hi,

On Mon, Dec 19, 2005 at 20:00:31 +0100, Daniel Mueller wrote:
> On Monday 19 December 2005 19:32, Johannes Winkelmann wrote:
> 
> > > > 3. No single master tree (as it is now)
> > >
> > > Mhh, a separated ports tree would be nice. A mechanism which prevents me
> > > from accidently touching x86 ports :-)
> >
> > It will also allow us to distribute the primary maintenance (following
> > the mailing lists, checking for announcements and conflicts) [..]
> 
> I don't know much about SVN yet - is it possible to create a branch for this 
> or would we get our 'own' repository (one per architecture).
We could host certain architectures in the same repository, but we
shouldn't make that a requirement.

I'd like to see a setup which doesn't depend on a particular revision
control system, since this will make it easier for new ports to get
started. Instead, I'd just sync all trees with "primary ports" to the
HDD, and track/sync/merge them there.

Regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From giulivo.navigante at katamail.com  Mon Dec 19 20:11:09 2005
From: giulivo.navigante at katamail.com (Giulivo Navigante)
Date: Mon, 19 Dec 2005 21:11:09 +0100
Subject: [clc-devel] Multi-platform ports management
In-Reply-To: <57680e350512191001j74978fc5q426865ff726695f6@mail.gmail.com>
References: <20051219125509.GA4009@titanium> <43A6DE94.2060005@katamail.com>	 <20051219164125.GA6869@titanium> <43A6F3B9.1070406@katamail.com> <57680e350512191001j74978fc5q426865ff726695f6@mail.gmail.com>
Message-ID: <43A713DD.1050804@katamail.com>

Jonathan Asghar wrote:
 >
> I have to agree with Johannes here, the testing should happen on the
> dev side and there should be some type of "QOS" control for a port
> that we produce.

this implies that $ARCH developers should test every known port of 
core/opt (and contrib?) collections... and it is not acceptable for me, 
specially for little communities, infact it produces two negaive aspects 
for the 90% of ports:

1. $ARCH dev are really overloaded
2. $ARCH ports can remains outdated for a long period

and the only 1 positive effective for the remanent 10% of buggy ports:

1. port usable without sending a ticket to the $ARCH developers

consider also the "obviously tested" ports distributed on the $ARCH iso 
image

regards
-- 
Giulivo Navigante
http://cruxppc.sunsite.dk


From jjasghar at gmail.com  Mon Dec 19 20:19:39 2005
From: jjasghar at gmail.com (Jonathan Asghar)
Date: Mon, 19 Dec 2005 14:19:39 -0600
Subject: [clc-devel] Multi-platform ports management
In-Reply-To: <43A713DD.1050804@katamail.com>
References: <20051219125509.GA4009@titanium> <43A6DE94.2060005@katamail.com>
	 <20051219164125.GA6869@titanium> <43A6F3B9.1070406@katamail.com>
	 <57680e350512191001j74978fc5q426865ff726695f6@mail.gmail.com>
	 <43A713DD.1050804@katamail.com>
Message-ID: <57680e350512191219ncb99d3cldb09905ec30daf90@mail.gmail.com>

> this implies that $ARCH developers should test every known port of
> core/opt (and contrib?) collections...

I dont truly believe that, first off, we have to "test" the majority
if not all of core/opt because we install the OS right?  yes contrib
is huge, i concede that, but i dont think it's unrealistic for us to
have a test plan for each release.  plus thats where bug reports come
into play, for the small amount of users right now for cruxppc we can
set up a mailing list type bug report system so we can get ontop of
the problem ports.
Yes, i agree it seems like a hack as of right now, but i guess in my
mind i'd prefer us to get a road layed down before moving towards the
superhighway, if you catch my drift.
my priorities in general would be to get a good uptodate ports system,
and solid base to work with, then move towards almost "recruiting"
users so the community grows and we can start worrying about stream
lining the "problem ports."
Also like i keep saying, i rsynced the ports for the x86 tree and so
far so good...i can send out the pkginfo -i to see what compiled fine
with no tweaking if yall like.

regards,
-j

--
Jonathan Asghar
phone: 512.619.0722


From trac at crux.nu  Tue Dec 20 07:23:24 2005
From: trac at crux.nu (CRUX)
Date: Tue, 20 Dec 2005 07:23:24 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2318=3A_pkg-get_bug?=
Message-ID: <053.97cbf1347804f9ab3172b4b139965fab@crux.nu>

#18: pkg-get bug
--------------------+-------------------------------------------------------
       Id:  18      |      Status:  new                     
Component:  ports   |    Modified:  Tue Dec 20 08:23:24 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  per     |    Reporter:  centericq at ukr.net       
--------------------+-------------------------------------------------------
 Well, after I've done pkg-repgen on my packages, I receive the following:

 {{{
 grim$ pkg-get diff
 pkg-get: /crux/pkgrepo/PKGREPO appears to be in wrong format!
 Aborting.
 }}}

 After a quick view of pkg-get source it seems like the problem caused by
 an prt-get update, which pkg-get didn't catched yet...

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/18>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Tue Dec 20 09:28:38 2005
From: trac at crux.nu (CRUX)
Date: Tue, 20 Dec 2005 09:28:38 -0000
Subject: [clc-devel] =?utf-8?b?UmU6IFtDUlVYXSAjMTg6IHBrZy1nZXQgYnVn?=
In-Reply-To: <053.97cbf1347804f9ab3172b4b139965fab@crux.nu>
References: <053.97cbf1347804f9ab3172b4b139965fab@crux.nu>
Message-ID: <062.029de89526c7771b2ad275224f64768f@crux.nu>

#18: pkg-get bug
--------------------+-------------------------------------------------------
       Id:  18      |      Status:  new                     
Component:  ports   |    Modified:  Tue Dec 20 10:28:38 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  per     |    Reporter:  centericq at ukr.net       
--------------------+-------------------------------------------------------
Comment (by cohan):

 I experienced the same problem after upgrading to the new rsync ports
 structure, but the reason was quite simple: building the new pkgrepo
 "failed":

 pkg-get repgen

 Package 'fam' not found
 Package 'imlib' not found
 Package 'lynx' not found

 this does not look like a critical error, but the repo produced when such
 a "not found" message occured while generating the repository leads to
 unuseable PKREPO's

 obviously pkg-get needs information from the ports tree to complete its
 REPO

 solution: remove the binary packages not present in your current ports
 tree OR provide the old ports as well

 furthermore, the readme of pkg-get says that the repo format slightly
 changed, but i guess you updated both pkg-repgen and pkg-get on all
 affected systems, so this should not be an issue

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/18>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Tue Dec 20 14:41:44 2005
From: trac at crux.nu (CRUX)
Date: Tue, 20 Dec 2005 14:41:44 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2319=3A_rc_shouldn=27t_remove_directories_on_system?=
 =?utf-8?q?_startup?=
Message-ID: <053.891a05521cd48a07048b963126a9c8a3@crux.nu>

#19: rc shouldn't remove directories on system startup
--------------------+-------------------------------------------------------
       Id:  19      |      Status:  new                     
Component:  ports   |    Modified:  Tue Dec 20 15:41:44 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  Per     |    Reporter:  jue                     
--------------------+-------------------------------------------------------
 Some applications, at least sane, may need a group writeable directory
 /var/lock/<name> to put lock-files into. At the moment rc removes
 everything, even directories, on system startup from /var/lock.

 Trivial fix:

 {{{
 --- rc.orig     2005-12-20 15:35:57.000000000 +0100
 +++ rc  2005-12-20 15:36:17.000000000 +0100
 @@ -53,7 +53,7 @@
  : > /var/run/utmp
  /bin/rm -rf /forcefsck /fastboot /etc/nologin /etc/shutdownpid
  (cd /var/run && /usr/bin/find . -name "*.pid" -delete)
 -(cd /var/lock && /usr/bin/find . ! -name . -delete)
 +(cd /var/lock && /usr/bin/find . ! -type d -delete)
  (cd /tmp && /usr/bin/find . ! -name . -delete)
  /bin/mkdir -m 1777 /tmp/.ICE-unix
 }}}

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/19>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Tue Dec 20 14:46:33 2005
From: trac at crux.nu (CRUX)
Date: Tue, 20 Dec 2005 14:46:33 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2320=3A_Dependencies_are_not_always_satisfiable?=
Message-ID: <053.784135d3f96ae25e0babccd57730a4d0@crux.nu>

#20: Dependencies are not always satisfiable
--------------------+-------------------------------------------------------
       Id:  20      |      Status:  new                     
Component:  ports   |    Modified:  Tue Dec 20 15:46:33 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  per     |    Reporter:  centericq at ukr.net       
--------------------+-------------------------------------------------------
 Seems like not all dependencies of some ports available in
 core/opt/contrib collections:


 {{{
 root# prt-get depends kdelibs
 ...
 -- missing packages
 imlib from kdelibs
 fam from kdelibs
 openldap from kdelibs

 }}}

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/20>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Tue Dec 20 14:52:43 2005
From: trac at crux.nu (CRUX)
Date: Tue, 20 Dec 2005 14:52:43 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2320=3A_Dependencies_are_not_always_satisfiab?=
 =?utf-8?q?le?=
In-Reply-To: <053.784135d3f96ae25e0babccd57730a4d0@crux.nu>
References: <053.784135d3f96ae25e0babccd57730a4d0@crux.nu>
Message-ID: <062.ee55faab01177d1047cf74bbe46c01b1@crux.nu>

#20: Dependencies are not always satisfiable
--------------------+-------------------------------------------------------
       Id:  20      |      Status:  new                     
Component:  ports   |    Modified:  Tue Dec 20 15:52:43 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  sten    |    Reporter:  centericq at ukr.net       
--------------------+-------------------------------------------------------
Changes (by jue):

  * owner:  per => sten

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/20>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Tue Dec 20 14:54:04 2005
From: trac at crux.nu (CRUX)
Date: Tue, 20 Dec 2005 14:54:04 -0000
Subject: [clc-devel] =?utf-8?b?UmU6IFtDUlVYXSAjMTg6IHBrZy1nZXQgYnVn?=
In-Reply-To: <053.97cbf1347804f9ab3172b4b139965fab@crux.nu>
References: <053.97cbf1347804f9ab3172b4b139965fab@crux.nu>
Message-ID: <062.8e35a31ca28f7bf3f4812decd30792be@crux.nu>

#18: pkg-get bug
--------------------+-------------------------------------------------------
       Id:  18      |      Status:  new                     
Component:  ports   |    Modified:  Tue Dec 20 15:54:04 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  sip     |    Reporter:  centericq at ukr.net       
--------------------+-------------------------------------------------------
Changes (by jue):

  * owner:  per => sip

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/18>
CRUX <http://crux.nu/>
CRUX


From jue at jue.li  Tue Dec 20 12:36:19 2005
From: jue at jue.li (Juergen Daubert)
Date: Tue, 20 Dec 2005 13:36:19 +0100
Subject: [clc-devel] Multi-platform ports management
In-Reply-To: <43A6DE94.2060005@katamail.com>
References: <20051219125509.GA4009@titanium> <43A6DE94.2060005@katamail.com>
Message-ID: <20051220123619.GA2039@jue.netz>

On Mon, Dec 19, 2005 at 05:23:48PM +0100, Giulivo Navigante wrote:
> Johannes Winkelmann wrote:
> >Hi there,
> >
> >I know that the PPC team as well as Peter Banks who took over the sparc
> >port are reading this, so let's start discussion issues related to ports
> >management. I think it's important to first agree on a goal for this,
> >and cover the technical details later if there's a consensus.
> >Also let me state that this is my personal opinion only, not the one of
> >CLC or the CRUX project.
> >
> >My goal is to have a system with the following properties:
> >
> >1. The user only gets ports tested on this platform
> 
> i think this is very difficult to realize and not useful... infact $ARCH 
> developers should perform a test for every known port and this is not 
> acceptable specially for little communities

I have to full agree with Johannes here. For me it's not acceptable to
have untested ports in a 'official' ports tree. Quality should go over
quantity.

regards
J?rgen


-- 
Juergen Daubert  |  mailto:jue at jue.li  
Korb, Germany    |  http://jue.li/crux



From trac at crux.nu  Tue Dec 20 17:37:51 2005
From: trac at crux.nu (CRUX)
Date: Tue, 20 Dec 2005 17:37:51 -0000
Subject: [clc-devel] =?utf-8?b?UmU6IFtDUlVYXSAjMTg6IHBrZy1nZXQgYnVn?=
In-Reply-To: <053.97cbf1347804f9ab3172b4b139965fab@crux.nu>
References: <053.97cbf1347804f9ab3172b4b139965fab@crux.nu>
Message-ID: <062.37f580e4095c0ca6ef646d98f191b190@crux.nu>

#18: pkg-get bug
--------------------+-------------------------------------------------------
       Id:  18      |      Status:  assigned                
Component:  ports   |    Modified:  Tue Dec 20 18:37:51 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  sip     |    Reporter:  centericq at ukr.net       
--------------------+-------------------------------------------------------
Changes (by sip):

  * status:  new => assigned

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/18>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Tue Dec 20 18:09:29 2005
From: trac at crux.nu (CRUX)
Date: Tue, 20 Dec 2005 18:09:29 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2321=3A_A_pkgmk_enhancement?=
Message-ID: <053.ff1dcc1c065eaef6e63d7ed97415ec27@crux.nu>

#21: A pkgmk enhancement
-------------------------+--------------------------------------------------
       Id:  21           |      Status:  new                     
Component:  pkgutils     |    Modified:  Tue Dec 20 19:09:29 2005
 Severity:  enhancement  |   Milestone:                          
 Priority:  normal       |     Version:                          
    Owner:  per          |    Reporter:  centericq at ukr.net       
-------------------------+--------------------------------------------------
 Sorry for an extensive traffic :)

 It would be nice to add to pkgmk an option which allows not to fail when
 tenth of NEW mismatches found :).

 When you have some optional dependency for kdebase and it is not
 represented in your .footprint but you want to be sure you don't missed
 anything really required  - it would be handy to have such option

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/21>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Tue Dec 20 18:09:41 2005
From: trac at crux.nu (CRUX)
Date: Tue, 20 Dec 2005 18:09:41 -0000
Subject: [clc-devel] =?utf-8?b?UmU6IFtDUlVYXSAjMTg6IHBrZy1nZXQgYnVn?=
In-Reply-To: <053.97cbf1347804f9ab3172b4b139965fab@crux.nu>
References: <053.97cbf1347804f9ab3172b4b139965fab@crux.nu>
Message-ID: <062.e42b69abcd2aea95f7eaabdc0f8b710c@crux.nu>

#18: pkg-get bug
--------------------+-------------------------------------------------------
       Id:  18      |      Status:  closed                  
Component:  ports   |    Modified:  Tue Dec 20 19:09:41 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  sip     |    Reporter:  centericq at ukr.net       
--------------------+-------------------------------------------------------
Changes (by sip):

  * resolution:  => fixed
  * status:  assigned => closed

Comment:

 Thanks, fixed in [423].
 pkg-repgen now produces well-formed repo files even
 if the port is missing.

 Not sure if i prefer this approach rather than aborting
 generation and reverting to the old repo, anyway this
 one is quicker. Lazy me.

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/18>
CRUX <http://crux.nu/>
CRUX


From jue at jue.li  Tue Dec 20 12:36:19 2005
From: jue at jue.li (Juergen Daubert)
Date: Tue, 20 Dec 2005 13:36:19 +0100
Subject: [clc-devel] Multi-platform ports management
In-Reply-To: <43A6DE94.2060005@katamail.com>
References: <20051219125509.GA4009@titanium> <43A6DE94.2060005@katamail.com>
Message-ID: <20051220123619.GA2039@jue.netz>

On Mon, Dec 19, 2005 at 05:23:48PM +0100, Giulivo Navigante wrote:
> Johannes Winkelmann wrote:
> >Hi there,
> >
> >I know that the PPC team as well as Peter Banks who took over the sparc
> >port are reading this, so let's start discussion issues related to ports
> >management. I think it's important to first agree on a goal for this,
> >and cover the technical details later if there's a consensus.
> >Also let me state that this is my personal opinion only, not the one of
> >CLC or the CRUX project.
> >
> >My goal is to have a system with the following properties:
> >
> >1. The user only gets ports tested on this platform
> 
> i think this is very difficult to realize and not useful... infact $ARCH 
> developers should perform a test for every known port and this is not 
> acceptable specially for little communities

I have to full agree with Johannes here. For me it's not acceptable to
have untested ports in a 'official' ports tree. Quality should go over
quantity.

regards
J?rgen


-- 
Juergen Daubert  |  mailto:jue at jue.li  
Korb, Germany    |  http://jue.li/crux



From jw at tks6.net  Tue Dec 20 22:58:31 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Tue, 20 Dec 2005 23:58:31 +0100
Subject: [clc-devel] Multi-platform ports management
In-Reply-To: <43A713DD.1050804@katamail.com>
References: <20051219125509.GA4009@titanium> <43A6DE94.2060005@katamail.com> <20051219164125.GA6869@titanium> <43A6F3B9.1070406@katamail.com> <57680e350512191001j74978fc5q426865ff726695f6@mail.gmail.com> <43A713DD.1050804@katamail.com>
Message-ID: <20051220225831.GG2301@titanium>

Hi Giulivo,

On Mon, Dec 19, 2005 at 21:11:09 +0100, Giulivo Navigante wrote:
> Jonathan Asghar wrote:
> >
> >I have to agree with Johannes here, the testing should happen on the
> >dev side and there should be some type of "QOS" control for a port
> >that we produce.
> 
> this implies that $ARCH developers should test every known port of 
> core/opt (and contrib?) collections... and it is not acceptable for me, 
> specially for little communities
You've stated this a couple of times now so I assume you're convinced
that it doesn't make sense to even try it.

I'm willing to believe that too, but since I'm currently confident that
it is possible even for a small crowd to maintain a properly tested
system using the right tools, I convinced Daniel to do a test run with a
x86_64 port which syncs from (and hopefully also to) x86.

We plan to start in january, and we'll certainly post our results here
to let you know how it goes. I'm sure that the outcome of this test will
give us a good idea about what's possible and what's not, and will
hopefully allow to use more facts and less emotional arguments in this
discussion.

Best regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From trac at crux.nu  Wed Dec 21 05:44:19 2005
From: trac at crux.nu (CRUX)
Date: Wed, 21 Dec 2005 05:44:19 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2322=3A_=27_prt-get_help_=27_doesn=27t_list_=27_dep?=
 =?utf-8?q?inst_=27_as_an_option_--_confusing_to_newbie=27s?=
Message-ID: <053.f8cb3f21776233c4b61362fdf5115311@crux.nu>

#22: ' prt-get help ' doesn't list ' depinst ' as an option -- confusing to
newbie's
---------------------+------------------------------------------------------
       Id:  22       |      Status:  new                     
Component:  prt-get  |    Modified:  Wed Dec 21 06:44:19 2005
 Severity:  normal   |   Milestone:                          
 Priority:  normal   |     Version:                          
    Owner:  jw       |    Reporter:  ckrainey at gmail.com      
---------------------+------------------------------------------------------
 ' prt-get help ' does not list ' depinst ' as an option -- confusing to
 newbie's (which I am ;-) ).  This is the first in a series of polish bugs
 I will be reporting in order to help shore up this great distro.

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/22>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Wed Dec 21 06:08:37 2005
From: trac at crux.nu (CRUX)
Date: Wed, 21 Dec 2005 06:08:37 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2323=3A_Broken_Port=3A__gtk_2=2E8=2E9-1?=
Message-ID: <053.81a4dfa8c5edc6d37a1562429499d241@crux.nu>

#23: Broken Port:  gtk 2.8.9-1
-------------------+--------------------------------------------------------
       Id:  23     |      Status:  new                     
Component:  ports  |    Modified:  Wed Dec 21 07:08:37 2005
 Severity:  major  |   Milestone:                          
 Priority:  high   |     Version:                          
    Owner:  per    |    Reporter:  anonymous               
-------------------+--------------------------------------------------------
 GTK 2.8.9-1 will not build during ' prt-get sysup ' after fresh install of
 CRUX using jaeger's "crux-2.1-latest.iso built on 30-Sep-2005 19:04" CD.
 GTK 2.8.9-1 depends on cairo and pango with cairo support.  Installing
 cairo and then 'prt-get update -fr pango' solves the problem.

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/23>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Wed Dec 21 09:00:13 2005
From: trac at crux.nu (CRUX)
Date: Wed, 21 Dec 2005 09:00:13 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2324=3A_Link_to_the_Ukrainian_CRUX_community?=
Message-ID: <053.c77999a3277a92fe697258f9b02f1a2c@crux.nu>

#24: Link to the Ukrainian CRUX community
---------------------------+------------------------------------------------
       Id:  24             |      Status:  new                     
Component:  doc / website  |    Modified:  Wed Dec 21 10:00:13 2005
 Severity:  normal         |   Milestone:                          
 Priority:  normal         |     Version:                          
    Owner:  jw             |    Reporter:  artur at idt.org.ua        
---------------------------+------------------------------------------------
 Link to the Ukrainian CRUX community: http://crux.org.ua .
 It works on the trac wiki too.
 I think it will be good if you'll add a link to this resource at
 http://crux.nu/cgi-bin/trac.cgi/wiki/Links.
 After the some time there will be a mirror and ukraine repository (now it
 sited at http://www.grimmy.kiev.ua/crux/repo/).

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/24>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Wed Dec 21 09:14:30 2005
From: trac at crux.nu (CRUX)
Date: Wed, 21 Dec 2005 09:14:30 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2325=3A_Link_to_the_Russian_translation_of_CRUX_Han?=
 =?utf-8?q?dbook_=28release_2=2E1=29?=
Message-ID: <053.a3ba3f1fd6703e2691e2507e1149d658@crux.nu>

#25: Link to the Russian translation of CRUX Handbook (release 2.1)
---------------------------+------------------------------------------------
       Id:  25             |      Status:  new                     
Component:  doc / website  |    Modified:  Wed Dec 21 10:14:30 2005
 Severity:  normal         |   Milestone:                          
 Priority:  normal         |     Version:                          
    Owner:  jw             |    Reporter:  artur at idt.org.ua        
---------------------------+------------------------------------------------
 The Russian translation of CRUX Handbook (release 2.1) was translated a
 month ago. HTML version of this document located at
 http://crux.isa.kz/?q=node/2.

 I think that you must put this link to the UserDocumentation ('''CRUX
 Handbook Translations''' section).

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/25>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Wed Dec 21 09:26:16 2005
From: trac at crux.nu (CRUX)
Date: Wed, 21 Dec 2005 09:26:16 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2325=3A_Link_to_the_Russian_translation_of_CR?=
 =?utf-8?q?UX_Handbook_=28release_2=2E1=29?=
In-Reply-To: <053.a3ba3f1fd6703e2691e2507e1149d658@crux.nu>
References: <053.a3ba3f1fd6703e2691e2507e1149d658@crux.nu>
Message-ID: <062.a2c89bcd2a8f8701324dfa7aca991329@crux.nu>

#25: Link to the Russian translation of CRUX Handbook (release 2.1)
---------------------------+------------------------------------------------
       Id:  25             |      Status:  closed                  
Component:  doc / website  |    Modified:  Wed Dec 21 10:26:16 2005
 Severity:  normal         |   Milestone:                          
 Priority:  normal         |     Version:                          
    Owner:  jw             |    Reporter:  artur at idt.org.ua        
---------------------------+------------------------------------------------
Changes (by anonymous):

  * resolution:  => fixed
  * status:  new => closed

Comment:

 done (also see my private mail)

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/25>
CRUX <http://crux.nu/>
CRUX


From giulivo.navigante at katamail.com  Wed Dec 21 10:27:37 2005
From: giulivo.navigante at katamail.com (Giulivo Navigante)
Date: Wed, 21 Dec 2005 11:27:37 +0100
Subject: [clc-devel] Multi-platform ports management
In-Reply-To: <20051220225831.GG2301@titanium>
References: <20051219125509.GA4009@titanium> <43A6DE94.2060005@katamail.com> <20051219164125.GA6869@titanium> <43A6F3B9.1070406@katamail.com> <57680e350512191001j74978fc5q426865ff726695f6@mail.gmail.com> <43A713DD.1050804@katamail.com> <20051220225831.GG2301@titanium>
Message-ID: <43A92E19.6010507@katamail.com>

Johannes Winkelmann wrote:
>
> We plan to start in january, and we'll certainly post our results here
> to let you know how it goes. I'm sure that the outcome of this test will
> give us a good idea about what's possible and what's not, and will
> hopefully allow to use more facts and less emotional arguments in this
> discussion.

i'm perfectly in accord with you

we will do the same for the ppc platform ... a propos, we've already do 
a similar work before distribute cruxppc 1.3 and 2.0, so consider my 
idea not only based on emotional arguments, but also on facts :)

regards
-- 
Giulivo Navigante
http://cruxppc.sunsite.dk


From trac at crux.nu  Wed Dec 21 10:55:18 2005
From: trac at crux.nu (CRUX)
Date: Wed, 21 Dec 2005 10:55:18 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2324=3A_Link_to_the_Ukrainian_CRUX_community?=
In-Reply-To: <053.c77999a3277a92fe697258f9b02f1a2c@crux.nu>
References: <053.c77999a3277a92fe697258f9b02f1a2c@crux.nu>
Message-ID: <062.fafe62eb64ced0ede15096c5cff954a5@crux.nu>

#24: Link to the Ukrainian CRUX community
---------------------------+------------------------------------------------
       Id:  24             |      Status:  closed                  
Component:  doc / website  |    Modified:  Wed Dec 21 11:55:17 2005
 Severity:  normal         |   Milestone:                          
 Priority:  normal         |     Version:                          
    Owner:  jw             |    Reporter:  artur at idt.org.ua        
---------------------------+------------------------------------------------
Changes (by jheino):

  * resolution:  => fixed
  * status:  new => closed

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/24>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Wed Dec 21 22:30:22 2005
From: trac at crux.nu (CRUX)
Date: Wed, 21 Dec 2005 22:30:22 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2314=3A_Update_port_db_repos_to_point_to_rsyn?=
 =?utf-8?q?c_collections?=
In-Reply-To: <053.92a6dffab8f35422c89a3921f5de46cc@crux.nu>
References: <053.92a6dffab8f35422c89a3921f5de46cc@crux.nu>
Message-ID: <062.af5c72d97441262ad599678015d68d00@crux.nu>

#14: Update port db repos to point to rsync collections
---------------------------+------------------------------------------------
       Id:  14             |      Status:  closed                  
Component:  doc / website  |    Modified:  Wed Dec 21 23:30:22 2005
 Severity:  major          |   Milestone:                          
 Priority:  normal         |     Version:                          
    Owner:  per            |    Reporter:  jw                      
---------------------------+------------------------------------------------
Changes (by jw):

  * resolution:  => fixed
  * status:  new => closed

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/14>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Thu Dec 22 11:15:40 2005
From: trac at crux.nu (CRUX)
Date: Thu, 22 Dec 2005 11:15:40 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2326=3A_man-pages_conflict?=
Message-ID: <053.1d87fb806ee1b3c02275743dcd16ef80@crux.nu>

#26: man-pages conflict
-------------------+--------------------------------------------------------
       Id:  26     |      Status:  new                     
Component:  ports  |    Modified:  Thu Dec 22 12:15:40 2005
 Severity:  minor  |   Milestone:                          
 Priority:  low    |     Version:  2.0                     
    Owner:  per    |    Reporter:  Lucas                   
-------------------+--------------------------------------------------------
 {{{
 sudo pkgadd -u /usr/pkgmk/man-pages#2.18-1.pkg.tar.gz
 usr/man/man2/fgetxattr.2.gz
 usr/man/man2/flistxattr.2.gz
 usr/man/man2/fremovexattr.2.gz
 usr/man/man2/fsetxattr.2.gz
 usr/man/man2/getxattr.2.gz
 usr/man/man2/lgetxattr.2.gz
 usr/man/man2/listxattr.2.gz
 usr/man/man2/llistxattr.2.gz
 usr/man/man2/lremovexattr.2.gz
 usr/man/man2/lsetxattr.2.gz
 usr/man/man2/removexattr.2.gz
 usr/man/man2/setxattr.2.gz
 pkgadd: listed file(s) already installed (use -f to ignore and overwrite)
 }}}

 These should be provided by acl an attr ports

 http://nipul.dynserv.net/lhazel64/attr

 http://nipul.dynserv.net/lhazel64/acl

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/26>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Thu Dec 22 13:29:09 2005
From: trac at crux.nu (CRUX)
Date: Thu, 22 Dec 2005 13:29:09 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2327=3A_new_mirror?=
Message-ID: <053.5a0179435f5081afe05d616fb281f8d4@crux.nu>

#27: new mirror
---------------------------+------------------------------------------------
       Id:  27             |      Status:  new                     
Component:  doc / website  |    Modified:  Thu Dec 22 14:29:09 2005
 Severity:  normal         |   Milestone:                          
 Priority:  normal         |     Version:                          
    Owner:  per            |    Reporter:  artur at idt.org.ua        
---------------------------+------------------------------------------------
 Please add following string to the wiki:Download page:
 {{{
 ||Ukraine||crux.org.ua||[http://crux.org.ua/download/ HTTP]||(Full mirror;
 [http://www.ua-ix.net.ua/uaix/bin/view/Main_ua/WebHome UA-IX] only)||
 }}}

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/27>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Thu Dec 22 20:46:30 2005
From: trac at crux.nu (CRUX)
Date: Thu, 22 Dec 2005 20:46:30 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2328=3A_OpenOffice=2Eorg_2=2E0=2Ex_file_locking_and?=
 =?utf-8?q?_NFS?=
Message-ID: <053.9f127625794e9c393ac42612b6d04d86@crux.nu>

#28: OpenOffice.org 2.0.x file locking and NFS
-----------------------------+----------------------------------------------
       Id:  28               |      Status:  new                     
Component:  ports            |    Modified:  Thu Dec 22 21:46:29 2005
 Severity:  normal           |   Milestone:                          
 Priority:  normal           |     Version:  2.0                     
    Owner:  sip at varlock.com  |    Reporter:  jdolan                  
-----------------------------+----------------------------------------------
 OOo 2.0.x now uses file locking by default, which is kindof nice, but does
 not currently work with CRUX's nfs ports, even when lockd is running on
 both client and server machines.  Others (Debain) users have noticed the
 same behaviour.  Some report limited success in reading/writing files over
 NFS in OOo by downgrading their NFS server's protocol to version2, but
 this is an undesirable solution for one application.

 Another option is to disable file locking via the soffice startup script,
 as this was the default in OOo 1.x:

 --- /usr/bin/soffice    2005-10-15 10:02:19.000000000 -0400
 +++ soffice     2005-12-22 15:38:44.000000000 -0500
 @@ -35,13 +35,13 @@
 #*************************************************************************

  #
 -# STAR_PROFILE_LOCKING_DISABLED=1
 -# export STAR_PROFILE_LOCKING_DISABLED
 +STAR_PROFILE_LOCKING_DISABLED=1
 +export STAR_PROFILE_LOCKING_DISABLED
  #

  # file locking now enabled by default
  SAL_ENABLE_FILE_LOCKING=1
 -export SAL_ENABLE_FILE_LOCKING
 +#export SAL_ENABLE_FILE_LOCKING

  # the following test is needed on Linux PPC with IBM j2sdk142
  if [ `uname -s` = "Linux" -a  "`uname -m`" = "ppc" ] ; then


 See http://www.openoffice.org/issues/show_bug.cgi?id=54586

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/28>
CRUX <http://crux.nu/>
CRUX


From viper at hometux.de  Fri Dec 23 10:57:41 2005
From: viper at hometux.de (Simon =?iso-8859-1?Q?Glo=DFner?=)
Date: Fri, 23 Dec 2005 11:57:41 +0100
Subject: [clc-devel] Renaming core/pkgconfig to core/pkg-config
In-Reply-To: <20051217090656.GA25966@titanium>
References: <20051214214724.GA2938@code-monkey.de> <20051216130308.GA19662@jue.netz> <20051217090656.GA25966@titanium>
Message-ID: <20051223105741.GA20669@viper.lan>

On Sat, Dec 17, 2005 at 10:06:56AM +0100, Johannes Winkelmann wrote:
> At CRUXCon, we planned to:
> - give no option in 'setup' to not install those

I disagree about this point. I think we shouldn't force the user to do
anything. A warning if they try to deselect it is ok but forcing them
is silly. Up to now I don't have any reasons why you should deselect
them but perhaps anybody else has them.

Regards Viper


From jw at tks6.net  Fri Dec 23 13:33:27 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Fri, 23 Dec 2005 14:33:27 +0100
Subject: [clc-devel] Little time to spend on CRUX related stuff in Q1/2006
Message-ID: <20051223133327.GB32382@titanium>

Hi there,

In the first quarter next year, I'll be moving to a different city (from
Bern to Zurich) and start to work for a different employer. I'm just
mentioning it here since I have a number of tasks ahead with higher
priority than CRUX, and I'll therefore focus mainly on the multi-arch
experiment and my ports, and spend little or no time on the new contrib,
change requests for the webpage, crux.nu administration or the issues
listed on the PostSwitch wiki page.  
I'm sure that this will cause no problems as those were shared
responsibilities anyway, I might however redirect some requests sent to
me privately to clc-devel or clc-contrib.

Thanks for your understanding,
Best regards, Johannes
P.S. If you happen to visit Zurich after January 16, let me know :-)
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From trac at crux.nu  Fri Dec 23 13:47:27 2005
From: trac at crux.nu (CRUX)
Date: Fri, 23 Dec 2005 13:47:27 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2329=3A_missing_depencies_for_blender3d?=
Message-ID: <053.23d0dc85717cb5ade1684ff8aedade32@crux.nu>

#29: missing depencies for blender3d
--------------------+-------------------------------------------------------
       Id:  29      |      Status:  new                     
Component:  ports   |    Modified:  Fri Dec 23 14:47:27 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  per     |    Reporter:  dct.c                   
--------------------+-------------------------------------------------------
 xenon# prt-get depends blender
 -- dependencies ([i] = installed)
 [i] glibc
 [i] libjpeg
 [i] pkgconfig
 [i] alsa-lib
 [i] freetype
 [i] expat
 [i] openssl
 [ ] doxygen
 [i] libpng
 [ ] libsdl
 [i] fontconfig
 [i] python
 [i] x11
 [ ] scons
 [ ] mesalib
 [ ] ftgl
 [ ] blender

 -- missing packages
 libz from blender
 libglut from mesalib

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/29>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Fri Dec 23 16:31:05 2005
From: trac at crux.nu (CRUX)
Date: Fri, 23 Dec 2005 16:31:05 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2330=3A_=5BSECURITY=5D_=5BPATCH=5D_Fix_openssl_dire?=
 =?utf-8?q?ctory_structure?=
Message-ID: <053.27bc8f4d578629224a0a443b7727d339@crux.nu>

#30: [SECURITY] [PATCH] Fix openssl directory structure
--------------------+-------------------------------------------------------
       Id:  30      |      Status:  new                     
Component:  ports   |    Modified:  Fri Dec 23 17:31:05 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  per     |    Reporter:  centericq at ukr.net       
--------------------+-------------------------------------------------------
 OpenSSL package lacks the /etc/ssl/newcerts directory, where openssl
 utility creates new certificates. If the directory not exists - it fails
 to sign a server keys.
 Also it will be nice to do this:

 mkdir -p $PKG/etc/ssl/newcerts
 touch $PKG/etc/ssl/index.txt
 cat "01" > $PKG/etc/ssl/serial

 All filenames are taken from a standard configuration file.
 It is wise to chmod 700 $PKG/etc/ssl/private to avoid access of normal
 users to secret keys
 Patch is here
 {{{
 --- Pkgfile.old 2005-12-23 18:23:43.000000000 +0200
 +++ Pkgfile     2005-12-23 18:28:15.000000000 +0200
 @@ -2,7 +2,7 @@

  name=openssl
  version=0.9.7i
 -release=1
 +release=2
  source=(http://www.openssl.org/source/$name-$version.tar.gz)

  build() {
 @@ -12,4 +12,9 @@ build() {
      make INSTALL_PREFIX=$PKG MANDIR=/usr/man MANSUFFIX=ssl install
      find $PKG -name "*fips*" -exec rm -f {} \;
      chmod -R +w $PKG
 +
 +    mkdir -p $PKG/etc/ssl/newcerts
 +    touch $PKG/etc/ssl/index.txt
 +    echo "01" > $PKG/etc/ssl/serial
 +    chmod 700 $PKG/etc/ssl/private
  }
 }}}

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/30>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Sat Dec 24 08:40:46 2005
From: trac at crux.nu (CRUX)
Date: Sat, 24 Dec 2005 08:40:46 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2328=3A_OpenOffice=2Eorg_2=2E0=2Ex_file_locki?=
 =?utf-8?q?ng_and_NFS?=
In-Reply-To: <053.9f127625794e9c393ac42612b6d04d86@crux.nu>
References: <053.9f127625794e9c393ac42612b6d04d86@crux.nu>
Message-ID: <062.cbfdbbde09aac94121b109ea00529264@crux.nu>

#28: OpenOffice.org 2.0.x file locking and NFS
-----------------------------+----------------------------------------------
       Id:  28               |      Status:  closed                  
Component:  ports            |    Modified:  Sat Dec 24 09:40:46 2005
 Severity:  normal           |   Milestone:                          
 Priority:  normal           |     Version:  2.0                     
    Owner:  sip at varlock.com  |    Reporter:  jdolan                  
-----------------------------+----------------------------------------------
Changes (by sip):

  * resolution:  => fixed
  * status:  new => closed

Comment:

 I opted for simply putting a note on the README since I believe
 OO locking is something one would want as a default behaviour,
 and we cannot know for sure at build time if the user will access
 OO files on a NFS share (even if nfs is active/installed)

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/28>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Sat Dec 24 08:41:22 2005
From: trac at crux.nu (CRUX)
Date: Sat, 24 Dec 2005 08:41:22 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2328=3A_OpenOffice=2Eorg_2=2E0=2Ex_file_locki?=
 =?utf-8?q?ng_and_NFS?=
In-Reply-To: <053.9f127625794e9c393ac42612b6d04d86@crux.nu>
References: <053.9f127625794e9c393ac42612b6d04d86@crux.nu>
Message-ID: <062.4402009b4275af40b1c375ac29094156@crux.nu>

#28: OpenOffice.org 2.0.x file locking and NFS
-----------------------------+----------------------------------------------
       Id:  28               |      Status:  reopened                
Component:  ports            |    Modified:  Sat Dec 24 09:41:21 2005
 Severity:  normal           |   Milestone:                          
 Priority:  normal           |     Version:  2.0                     
    Owner:  sip at varlock.com  |    Reporter:  jdolan                  
-----------------------------+----------------------------------------------
Changes (by sip):

  * resolution:  fixed =>
  * status:  closed => reopened

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/28>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Sat Dec 24 08:42:26 2005
From: trac at crux.nu (CRUX)
Date: Sat, 24 Dec 2005 08:42:26 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2328=3A_OpenOffice=2Eorg_2=2E0=2Ex_file_locki?=
 =?utf-8?q?ng_and_NFS?=
In-Reply-To: <053.9f127625794e9c393ac42612b6d04d86@crux.nu>
References: <053.9f127625794e9c393ac42612b6d04d86@crux.nu>
Message-ID: <062.393bb68a690c9d139ec65a7e49cab7e0@crux.nu>

#28: OpenOffice.org 2.0.x file locking and NFS
--------------------+-------------------------------------------------------
       Id:  28      |      Status:  new                     
Component:  ports   |    Modified:  Sat Dec 24 09:42:26 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:  2.0                     
    Owner:  sip     |    Reporter:  jdolan                  
--------------------+-------------------------------------------------------
Changes (by sip):

  * status:  reopened => new
  * owner:  sip at varlock.com => sip

Comment:

 Sorrry for the noise, I reopened and reassigned to the user
 so the email is not visible.

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/28>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Sat Dec 24 08:42:42 2005
From: trac at crux.nu (CRUX)
Date: Sat, 24 Dec 2005 08:42:42 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2328=3A_OpenOffice=2Eorg_2=2E0=2Ex_file_locki?=
 =?utf-8?q?ng_and_NFS?=
In-Reply-To: <053.9f127625794e9c393ac42612b6d04d86@crux.nu>
References: <053.9f127625794e9c393ac42612b6d04d86@crux.nu>
Message-ID: <062.78fa75dc14f1b728f32560ecc52850d1@crux.nu>

#28: OpenOffice.org 2.0.x file locking and NFS
--------------------+-------------------------------------------------------
       Id:  28      |      Status:  closed                  
Component:  ports   |    Modified:  Sat Dec 24 09:42:41 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:  2.0                     
    Owner:  sip     |    Reporter:  jdolan                  
--------------------+-------------------------------------------------------
Changes (by sip):

  * resolution:  => fixed
  * status:  new => closed

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/28>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Sat Dec 24 09:05:42 2005
From: trac at crux.nu (CRUX)
Date: Sat, 24 Dec 2005 09:05:42 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2316=3A_The_new_guys_need_to_know_about_commu?=
 =?utf-8?q?nity=2E?=
In-Reply-To: <053.57a00136d46af8e65afe1c1299292a07@crux.nu>
References: <053.57a00136d46af8e65afe1c1299292a07@crux.nu>
Message-ID: <062.377402a21c39f565713e103643a2e3b8@crux.nu>

#16: The new guys need to know about community.
---------------------------+------------------------------------------------
       Id:  16             |      Status:  closed                  
Component:  doc / website  |    Modified:  Sat Dec 24 10:05:42 2005
 Severity:  minor          |   Milestone:                          
 Priority:  low            |     Version:                          
    Owner:  per            |    Reporter:  centericq at ukr.net       
---------------------------+------------------------------------------------
Changes (by sip):

  * resolution:  => fixed
  * status:  new => closed

Comment:

 Added to Links -> Community

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/16>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Sat Dec 24 09:18:00 2005
From: trac at crux.nu (CRUX)
Date: Sat, 24 Dec 2005 09:18:00 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2322=3A_=27_prt-get_help_=27_doesn=27t_list_?=
 =?utf-8?q?=27_depinst_=27_as_an_option_--_confusing_to_newbie=27s?=
In-Reply-To: <053.f8cb3f21776233c4b61362fdf5115311@crux.nu>
References: <053.f8cb3f21776233c4b61362fdf5115311@crux.nu>
Message-ID: <062.e26c97483045bb1896bc55f90c60ef78@crux.nu>

#22: ' prt-get help ' doesn't list ' depinst ' as an option -- confusing to
newbie's
---------------------+------------------------------------------------------
       Id:  22       |      Status:  assigned                
Component:  prt-get  |    Modified:  Sat Dec 24 10:18:00 2005
 Severity:  normal   |   Milestone:                          
 Priority:  normal   |     Version:                          
    Owner:  sip      |    Reporter:  ckrainey at gmail.com      
---------------------+------------------------------------------------------
Changes (by sip):

  * status:  new => assigned
  * owner:  jw => sip

Comment:

 Committed fix in [445]

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/22>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Sat Dec 24 09:25:16 2005
From: trac at crux.nu (CRUX)
Date: Sat, 24 Dec 2005 09:25:16 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2327=3A_new_mirror?=
In-Reply-To: <053.5a0179435f5081afe05d616fb281f8d4@crux.nu>
References: <053.5a0179435f5081afe05d616fb281f8d4@crux.nu>
Message-ID: <062.c66f63cd68d87c0d7c7bb47df3f448ef@crux.nu>

#27: new mirror
---------------------------+------------------------------------------------
       Id:  27             |      Status:  closed                  
Component:  doc / website  |    Modified:  Sat Dec 24 10:25:16 2005
 Severity:  normal         |   Milestone:                          
 Priority:  normal         |     Version:                          
    Owner:  per            |    Reporter:  artur at idt.org.ua        
---------------------------+------------------------------------------------
Changes (by sip):

  * resolution:  => fixed
  * status:  new => closed

Comment:

 Added. Not sure if we should list restricted-access mirrors in this
 page, we'll see if/when there are similar cases in the future.

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/27>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Sat Dec 24 09:40:03 2005
From: trac at crux.nu (CRUX)
Date: Sat, 24 Dec 2005 09:40:03 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2320=3A_Dependencies_are_not_always_satisfiab?=
 =?utf-8?q?le?=
In-Reply-To: <053.784135d3f96ae25e0babccd57730a4d0@crux.nu>
References: <053.784135d3f96ae25e0babccd57730a4d0@crux.nu>
Message-ID: <062.991777dca9c6bb0badfea7a8bb36fe3b@crux.nu>

#20: Dependencies are not always satisfiable
--------------------+-------------------------------------------------------
       Id:  20      |      Status:  new                     
Component:  ports   |    Modified:  Sat Dec 24 10:40:02 2005
 Severity:  normal  |   Milestone:                          
 Priority:  high    |     Version:                          
    Owner:  sten    |    Reporter:  centericq at ukr.net       
--------------------+-------------------------------------------------------
Changes (by sip):

  * priority:  normal => high

Comment:

 Here's the complete list of missing deps at the
 time of writing:

 fam from kdelibs[[BR]]
 gnome-vfs from xine-lib[[BR]]
 gst-plugins from amarok[[BR]]
 imlib from kdelibs[[BR]]
 iproute2 from vpnc[[BR]]
 libmikmod from sdl_mixer[[BR]]

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/20>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Sat Dec 24 10:11:44 2005
From: trac at crux.nu (CRUX)
Date: Sat, 24 Dec 2005 10:11:44 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2310=3A_groff_mm_macros_incorrectly_center_di?=
 =?utf-8?q?splay_captions?=
In-Reply-To: <053.51861b3dd629b780acbe9c0d76e57d92@crux.nu>
References: <053.51861b3dd629b780acbe9c0d76e57d92@crux.nu>
Message-ID: <062.b4346f6991f13dd8b2b628f105ecd4af@crux.nu>

#10: groff mm macros incorrectly center display captions
--------------------+-------------------------------------------------------
       Id:  10      |      Status:  closed                  
Component:  ports   |    Modified:  Sat Dec 24 11:11:44 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  per     |    Reporter:  danieldk at pobox.com      
--------------------+-------------------------------------------------------
Changes (by sip):

  * resolution:  => fixed
  * status:  new => closed

Comment:

 Fixed in [446]

 It's probably better to postpone such minor fixes
 (expecially in core) and wait until they're shipped with
 the next release.

 Anyway, the patch was provided, the groff team does not
 release too often, so I updated the port.

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/10>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Mon Dec 26 10:12:50 2005
From: trac at crux.nu (CRUX)
Date: Mon, 26 Dec 2005 10:12:50 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2320=3A_Dependencies_are_not_always_satisfiab?=
 =?utf-8?q?le?=
In-Reply-To: <053.784135d3f96ae25e0babccd57730a4d0@crux.nu>
References: <053.784135d3f96ae25e0babccd57730a4d0@crux.nu>
Message-ID: <062.3e358329b60a33ee1c64c40b6a880720@crux.nu>

#20: Dependencies are not always satisfiable
--------------------+-------------------------------------------------------
       Id:  20      |      Status:  assigned                
Component:  ports   |    Modified:  Mon Dec 26 11:12:50 2005
 Severity:  normal  |   Milestone:                          
 Priority:  high    |     Version:                          
    Owner:  sten    |    Reporter:  centericq at ukr.net       
--------------------+-------------------------------------------------------
Changes (by sten):

  * status:  new => assigned

Comment:

 The FAM issue is in the process of being resolved.  My subjective
 experiences with FAM have been highly unsatisfactory.  It, or the way
 konqueror talks to FAM, as FAM talks to the kernel via DNotify seem to
 destabilize my KDE desktop more then just leaving FAM out.

 I'm in the process of testing the latest version of gamin, and would
 appreciate any horror/success stories resulting from switching from FAM to
 gamin.  Gamin is default for Ubuntu/Kubuntu, so it might be worthwhile.
 It can be found in my httpup repository:
 http://members.shaw.ca/nick.steeves/ports/

 I'll drop those gnome-vfs, and gst-plugins dependencies if the GNOME stuff
 is going to be excluded from crux.nu for a very long time--they're just
 there so that a user can track footprint mis-matches.

 I have no interest, or responsibility for the maintenance of iproute2, but
 have adopted libmikmod.

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/20>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Mon Dec 26 10:14:44 2005
From: trac at crux.nu (CRUX)
Date: Mon, 26 Dec 2005 10:14:44 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2331=3A_iproute2_missing_from_vpnc?=
Message-ID: <053.2d6dc77dd97a9b55f942bf3e6515bb9a@crux.nu>

#31: iproute2 missing from vpnc
--------------------+-------------------------------------------------------
       Id:  31      |      Status:  new                     
Component:  ports   |    Modified:  Mon Dec 26 11:14:44 2005
 Severity:  normal  |   Milestone:                          
 Priority:  high    |     Version:                          
    Owner:  jaeger  |    Reporter:  sten                    
--------------------+-------------------------------------------------------
 this was mistakenly assigned to me in another ticket.  Please take care of
 it.

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/31>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Wed Dec 28 11:56:02 2005
From: trac at crux.nu (CRUX)
Date: Wed, 28 Dec 2005 11:56:02 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2320=3A_Dependencies_are_not_always_satisfiab?=
 =?utf-8?q?le?=
In-Reply-To: <053.784135d3f96ae25e0babccd57730a4d0@crux.nu>
References: <053.784135d3f96ae25e0babccd57730a4d0@crux.nu>
Message-ID: <062.6dabf77da6d003f09c7528d6517b78d7@crux.nu>

#20: Dependencies are not always satisfiable
--------------------+-------------------------------------------------------
       Id:  20      |      Status:  closed                  
Component:  ports   |    Modified:  Wed Dec 28 12:56:02 2005
 Severity:  normal  |   Milestone:                          
 Priority:  high    |     Version:                          
    Owner:  sten    |    Reporter:  centericq at ukr.net       
--------------------+-------------------------------------------------------
Changes (by sten):

  * resolution:  => fixed
  * status:  assigned => closed

Comment:

 Matt Housh told me that the GNOME stuff is out of opt permanently, so I've
 removed all GNOME-related dependencies.

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/20>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Wed Dec 28 18:05:30 2005
From: trac at crux.nu (CRUX)
Date: Wed, 28 Dec 2005 18:05:30 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2332=3A_md5sum_mismatch_for_kdebase?=
Message-ID: <053.1666ea0846772a5b0ca83c842e2ae819@crux.nu>

#32: md5sum mismatch for kdebase
--------------------+-------------------------------------------------------
       Id:  32      |      Status:  new                     
Component:  ports   |    Modified:  Wed Dec 28 19:05:30 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  sten    |    Reporter:  anonymous               
--------------------+-------------------------------------------------------
 =======> ERROR: Md5sum mismatch found:
 MISSING   ddd463e86a38549ec30d462416067c86  kdm
 NEW       1eda0ffa08aee841a5beb2fe21197043  kdm
 =======> ERROR: Building '/usr/ports/packages/kdebase#3.5.0-3.pkg.tar.gz'
 failed.

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/32>
CRUX <http://crux.nu/>
CRUX


From jue at jue.li  Thu Dec 29 11:27:22 2005
From: jue at jue.li (Juergen Daubert)
Date: Thu, 29 Dec 2005 12:27:22 +0100
Subject: [clc-devel] core/opt dependencies
Message-ID: <20051229112722.GA13120@jue.netz>

Hi all,

one outstanding point is still the question how to deal with
dependencies for core and even opt ports. IIRC one result of 
CruxCon 2005 was, to handle that in the following way:

 - All core/opt ports should list run-time dependencies
 - but not to glibc and gcc
 - no build-time dependencies

As a first step I've created a dependency list of all core
ports [1] with a slightly modified version of Johannes' 
'finddeps' [2]. To simplify this, the script 'mkdeplist' [3]
could be used. The output of 'reducedeps' [4] is a compressed
list with no redundant dependencies [5]. [6] is a list of all 
core/opt ports installed on my system.
Be aware, [3] and [4] are quick hacks without any comments
and error checks.

One drawback of the method above is, that the list is not
complete, because only deps which can be found with ldd are
listed. Other deps like hicolor-icon-theme for gtk or ruby
for yapo are missing.

Ok so far, but how to proceed ? 

- if we agree with the rules above, I'll add all the missing
  deps to the core ports.
- remove build-time deps like pkgconfig
- define a list of core-core ports, which must be installed to
  build ports, or ... ?
- it would be nice if we had a complete core/opt list. 
  I'm volunteer for creating/maintaining such a list. To build
  them I need the output of 'mkdeplist /usr/ports/opt'.

Thanks for your attention and kind regards
Juergen


[1] http://jue.li/crux/misc/core_deps_full.txt
[2] http://jue.li/crux/misc/finddeps
[3] http://jue.li/crux/misc/mkdeplist
[4] http://jue.li/crux/misc/reducedeps
[5] http://jue.li/crux/misc/core_deps.txt
[6] http://jue.li/crux/misc/all_deps.txt

-- 
Juergen Daubert  |  mailto:jue at jue.li  
Korb, Germany    |  http://jue.li/crux



From trac at crux.nu  Thu Dec 29 16:06:07 2005
From: trac at crux.nu (CRUX)
Date: Thu, 29 Dec 2005 16:06:07 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2328=3A_OpenOffice=2Eorg_2=2E0=2Ex_file_locki?=
 =?utf-8?q?ng_and_NFS?=
In-Reply-To: <053.9f127625794e9c393ac42612b6d04d86@crux.nu>
References: <053.9f127625794e9c393ac42612b6d04d86@crux.nu>
Message-ID: <062.12a256febe7ae9a4a3141417e936df24@crux.nu>

#28: OpenOffice.org 2.0.x file locking and NFS
--------------------+-------------------------------------------------------
       Id:  28      |      Status:  closed                  
Component:  ports   |    Modified:  Thu Dec 29 17:06:07 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:  2.0                     
    Owner:  sip     |    Reporter:  jdolan                  
--------------------+-------------------------------------------------------
Comment (by jdolan):

 Okay, I can live with that.  From what I've found OOo 2.x is not yet
 stable, anyway.  We're reverting to 1.1.5.  Bugger :/

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/28>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Thu Dec 29 19:19:04 2005
From: trac at crux.nu (CRUX)
Date: Thu, 29 Dec 2005 19:19:04 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2332=3A_md5sum_mismatch_for_kdebase?=
In-Reply-To: <053.1666ea0846772a5b0ca83c842e2ae819@crux.nu>
References: <053.1666ea0846772a5b0ca83c842e2ae819@crux.nu>
Message-ID: <062.03c51b0f404eb95fdef48fcbae8c09e8@crux.nu>

#32: md5sum mismatch for kdebase
--------------------+-------------------------------------------------------
       Id:  32      |      Status:  closed                  
Component:  ports   |    Modified:  Thu Dec 29 20:19:04 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  sten    |    Reporter:  anonymous               
--------------------+-------------------------------------------------------
Changes (by sten):

  * resolution:  => fixed
  * status:  new => closed

Comment:

 fixed in [471]

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/32>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Thu Dec 29 20:10:49 2005
From: trac at crux.nu (CRUX)
Date: Thu, 29 Dec 2005 20:10:49 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2333=3A_contrib/gcc4_port_broken?=
Message-ID: <053.fa73b49b8a41a269222aa10ddd48da11@crux.nu>

#33: contrib/gcc4 port broken
--------------------+-------------------------------------------------------
       Id:  33      |      Status:  new                     
Component:  ports   |    Modified:  Thu Dec 29 21:10:49 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  per     |    Reporter:  anonymous               
--------------------+-------------------------------------------------------
 The mirror used has broken links.

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/33>
CRUX <http://crux.nu/>
CRUX


From sip at varlock.com  Thu Dec 29 20:19:24 2005
From: sip at varlock.com (Simone Rota)
Date: Thu, 29 Dec 2005 21:19:24 +0100
Subject: [clc-devel] core/opt dependencies
In-Reply-To: <20051229112722.GA13120@jue.netz>
References: <20051229112722.GA13120@jue.netz>
Message-ID: <43B444CC.6000805@varlock.com>

On 12/29/05 12:27 Juergen Daubert wrote:
> one outstanding point is still the question how to deal with
> dependencies for core and even opt ports. IIRC one result of 
> CruxCon 2005 was, to handle that in the following way:
> 
>  - All core/opt ports should list run-time dependencies
>  - but not to glibc and gcc
>  - no build-time dependencies

Maybe I'm a bit late for this note, anyway, after having
used the new collection layout for a while, I feel a bit
nostalgic regarding the previous base/opt division.

To me x11, gtk, firefox etc are not exactly what I'd call
core requirements for a CRUX setup (even if it's important
to have them on the iso).

An idea is to move the ports from the previous opt collection
into the current opt, with some ex-base port too,
thus obtaining a true core collection, that really represent
things that should not be removed (ie by prt-get) and are not listed as
dependencies for other ports since they're implied (pkgconfig?).

Note that this will not impact end users at all.

> - remove build-time deps like pkgconfig
> - define a list of core-core ports, which must be installed to
>   build ports, or ... ?

This two points would be handled by the suggested core/opt separation.

> - if we agree with the rules above, I'll add all the missing
>   deps to the core ports.
> - it would be nice if we had a complete core/opt list. 
>   I'm volunteer for creating/maintaining such a list. To build
>   them I need the output of 'mkdeplist /usr/ports/opt'.

I plan to setup (in a few days) a build machine to fully test
core and opt ports for missing deps, broken urls, etc.
I'll send you the list of found deps for opt on a stock
opt+core setup.

Regards,
Simone

-- 
Simone Rota           WEB : http://www.varlock.com
Bergamo, Italy        MAIL: sip at varlock.com


From tilman at code-monkey.de  Thu Dec 29 20:50:46 2005
From: tilman at code-monkey.de (Tilman Sauerbeck)
Date: Thu, 29 Dec 2005 21:50:46 +0100
Subject: [clc-devel] core/opt dependencies
In-Reply-To: <43B444CC.6000805@varlock.com>
References: <20051229112722.GA13120@jue.netz> <43B444CC.6000805@varlock.com>
Message-ID: <20051229205045.GA20385@code-monkey.de>

Simone Rota [2005-12-29 21:19]:
> On 12/29/05 12:27 Juergen Daubert wrote:
> > one outstanding point is still the question how to deal with
> > dependencies for core and even opt ports. IIRC one result of 
> > CruxCon 2005 was, to handle that in the following way:
> > 
> >  - All core/opt ports should list run-time dependencies
> >  - but not to glibc and gcc
> >  - no build-time dependencies
> 
> Maybe I'm a bit late for this note, anyway, after having
> used the new collection layout for a while, I feel a bit
> nostalgic regarding the previous base/opt division.
> 
> To me x11, gtk, firefox etc are not exactly what I'd call
> core requirements for a CRUX setup (even if it's important
> to have them on the iso).

Yes, I've been thinking about this as well.

> An idea is to move the ports from the previous opt collection
> into the current opt, with some ex-base port too,
> thus obtaining a true core collection, that really represent
> things that should not be removed (ie by prt-get) and are not listed as
> dependencies for other ports since they're implied (pkgconfig?).

I like this proposal.

Regards,
Tilman
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20051229/985bbabf/attachment.asc>

From trac at crux.nu  Thu Dec 29 21:20:05 2005
From: trac at crux.nu (CRUX)
Date: Thu, 29 Dec 2005 21:20:05 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2334=3A_db_version_bump_=28fixes_broken_link=29?=
Message-ID: <053.a4c0e0367a09ccb2274439efea72bd96@crux.nu>

#34: db version bump (fixes broken link)
---------------------+------------------------------------------------------
       Id:  34       |      Status:  new                     
Component:  ports    |    Modified:  Thu Dec 29 22:20:04 2005
 Severity:  trivial  |   Milestone:                          
 Priority:  normal   |     Version:                          
    Owner:  per      |    Reporter:  aon at iki.fi              
---------------------+------------------------------------------------------
 Berkeley DB 4.3.29 has been released on 30th September 2005. The old
 version (4.3.28) doesn't seem to exist on the mirror anymore.

 {{{
 diff -uprN db/.md5sum db.new/.md5sum
 --- db/.md5sum  2005-12-29 21:14:31.000000000 +0200
 +++ db.new/.md5sum      2005-12-29 21:14:27.000000000 +0200
 @@ -1 +1 @@
 -e27759537db6054b31d8cb3e99ba6fbb  db-4.3.28.tar.gz
 +13585a20ce32f113b8e8cdb57f52e3bb  db-4.3.29.tar.gz
 diff -uprN db/Pkgfile db.new/Pkgfile
 --- db/Pkgfile  2005-12-29 21:14:31.000000000 +0200
 +++ db.new/Pkgfile      2005-12-29 21:14:27.000000000 +0200
 @@ -3,7 +3,7 @@
  # Maintainer:  Per Lid?n <per at fukt.bth.se>

  name=db
 -version=4.3.28
 +version=4.3.29
  release=1
  source=(ftp://ftp.sleepycat.com/releases/$name-$version.tar.gz)
 }}}

-- 
Ticket URL: <http://www.crux.nu/cgi-bin/trac.cgi/ticket/34>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Thu Dec 29 21:53:27 2005
From: trac at crux.nu (CRUX)
Date: Thu, 29 Dec 2005 21:53:27 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2333=3A_contrib/gcc4_port_broken?=
In-Reply-To: <053.fa73b49b8a41a269222aa10ddd48da11@crux.nu>
References: <053.fa73b49b8a41a269222aa10ddd48da11@crux.nu>
Message-ID: <062.8965358750e2bb80ba0aa2fbc273b5e0@crux.nu>

#33: contrib/gcc4 port broken
--------------------+-------------------------------------------------------
       Id:  33      |      Status:  closed                  
Component:  ports   |    Modified:  Thu Dec 29 22:53:27 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  per     |    Reporter:  anonymous               
--------------------+-------------------------------------------------------
Changes (by jw):

  * resolution:  => fixed
  * status:  new => closed

Comment:

 Fixed; please report problems regarding ports from contrib directly to the
 maintainer

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/33>
CRUX <http://crux.nu/>
CRUX


From jue at jue.li  Fri Dec 30 12:27:12 2005
From: jue at jue.li (Juergen Daubert)
Date: Fri, 30 Dec 2005 13:27:12 +0100
Subject: [clc-devel] core/opt dependencies
In-Reply-To: <43B444CC.6000805@varlock.com>
References: <20051229112722.GA13120@jue.netz> <43B444CC.6000805@varlock.com>
Message-ID: <20051230122712.GA1641@jue.netz>

On Thu, Dec 29, 2005 at 09:19:24PM +0100, Simone Rota wrote:
> On 12/29/05 12:27 Juergen Daubert wrote:
> > one outstanding point is still the question how to deal with
> > dependencies for core and even opt ports. IIRC one result of 
> > CruxCon 2005 was, to handle that in the following way:
> > 
> >  - All core/opt ports should list run-time dependencies
> >  - but not to glibc and gcc
> >  - no build-time dependencies
> 
> Maybe I'm a bit late for this note, anyway, after having
> used the new collection layout for a while, I feel a bit
> nostalgic regarding the previous base/opt division.
> 
> To me x11, gtk, firefox etc are not exactly what I'd call
> core requirements for a CRUX setup (even if it's important
> to have them on the iso).

I can understand your feelings about the current divison of
ports in core/opt. We still have the problem, that we try to 
map some basic functionallity with a filesystem layout. 
ATM core represents all ports included on the cd. But I agree
that x11, gtk etc. are not vital for a "core" crux system.

One desperate approach could be to put all core/opt ports in
one collection, e.g crux, and achieve the additioal grouping
with some extra meta-data in the Pkgfiles or other mechanisms
like helper-files ...


kind regards
J?rgen


-- 
Juergen Daubert  |  mailto:jue at jue.li  
Korb, Germany    |  http://jue.li/crux



From jasonthomasdolan at yahoo.com  Fri Dec 30 14:30:04 2005
From: jasonthomasdolan at yahoo.com (Jay Dolan)
Date: Fri, 30 Dec 2005 06:30:04 -0800 (PST)
Subject: Fwd: Re: [clc-devel] core/opt dependencies
Message-ID: <20051230143004.42010.qmail@web32902.mail.mud.yahoo.com>

--- Jay Dolan wrote:
> Date: Fri, 30 Dec 2005 06:28:36 -0800 (PST)
> From: Jay Dolan
> Subject: Re: [clc-devel] core/opt dependencies
> To: Juergen Daubert
> 
> --- Juergen Daubert wrote:
> > I can understand your feelings about the current
> > divison of
> > ports in core/opt. We still have the problem, that
> > we try to 
> > map some basic functionallity with a filesystem
> > layout. 
> > ATM core represents all ports included on the cd.
> > But I agree
> > that x11, gtk etc. are not vital for a "core" crux
> > system.
> > 
> > One desperate approach could be to put all
> core/opt
> > ports in
> > one collection, e.g crux, and achieve the
> additioal
> > grouping
> > with some extra meta-data in the Pkgfiles or other
> > mechanisms
> > like helper-files ...
> > 
> 
> 
> There is really no need for such metadata.  Per will
> compile a list of ports (probably very close to what
> was 'base') that will be pre-selected when setup is
> run.  When else do you need to know what's in
> 'base'? 
> In this way, setup will be slightly less confusing
> to
> first-timers, too, because they will not be faced
> with
> "What's base, opt, and contrib?"  Instead, just the
> package names will be visible because if it's on the
> cd, it's 'core'.  Let's not make it more complicated
> than it has to be :)
> 

Sorry for the 2x mail Jue.


Jay Dolan
Software Engineer, Systems Analyst
Windmill Cycles, Inc.
508.999.4000


	
		
__________________________________ 
Yahoo! for Good - Make a difference this year. 
http://brand.yahoo.com/cybergivingweek2005/


From jue at jue.li  Fri Dec 30 15:22:17 2005
From: jue at jue.li (Juergen Daubert)
Date: Fri, 30 Dec 2005 16:22:17 +0100
Subject: Fwd: Re: [clc-devel] core/opt dependencies
In-Reply-To: <20051230143004.42010.qmail@web32902.mail.mud.yahoo.com>
References: <20051230143004.42010.qmail@web32902.mail.mud.yahoo.com>
Message-ID: <20051230152216.GA31932@jue.netz>

On Fri, Dec 30, 2005 at 06:30:04AM -0800, Jay Dolan wrote:
> --- Jay Dolan wrote:
>  
>  There is really no need for such metadata.  Per will
>  compile a list of ports (probably very close to what
>  was 'base') that will be pre-selected when setup is
>  run.  When else do you need to know what's in
>  'base'? 
>  In this way, setup will be slightly less confusing
>  to
>  first-timers, too, because they will not be faced
>  with
>  "What's base, opt, and contrib?"  Instead, just the
>  package names will be visible because if it's on the
>  cd, it's 'core'.  Let's not make it more complicated
>  than it has to be :)
  
ok, than the ports listed as dependencies in core ports
are all of core but not those one on that list ? Where is 
that list ?

Hmm, sounds not very straight-forward to me, but anyway,
as long as this point is not really clear, it makes no
sense to touch the core ports and add any dependency
information.

best regards
Juergen

-- 
Juergen Daubert  |  mailto:jue at jue.li  
Korb, Germany    |  http://jue.li/crux



From jasonthomasdolan at yahoo.com  Fri Dec 30 15:39:25 2005
From: jasonthomasdolan at yahoo.com (Jay Dolan)
Date: Fri, 30 Dec 2005 07:39:25 -0800 (PST)
Subject: Fwd: Re: [clc-devel] core/opt dependencies
In-Reply-To: <20051230152216.GA31932@jue.netz>
Message-ID: <20051230153925.35380.qmail@web32914.mail.mud.yahoo.com>

--- Juergen Daubert <jue at jue.li> wrote:
> ok, than the ports listed as dependencies in core
> ports
> are all of core but not those one on that list ?
> Where is 
> that list ?
> 
> Hmm, sounds not very straight-forward to me, but
> anyway,
> as long as this point is not really clear, it makes
> no
> sense to touch the core ports and add any dependency
> information.

I think all ports except a very select few (c build
chain) will have dependency information.  Deps will be
omitted from those ports simply because users won't be
expected to rebuild them.  They will  be updated only
with new CRUX releases - thus we can ensure a
consistent bootstrapped build environment.  Those few
ports happen to be a subset of 'preselected essential
setup packages' - a list that only needs to be
maintained in the setup script.  Does this make sense?

Jay Dolan
Software Engineer, Systems Analyst
Windmill Cycles, Inc.
508.999.4000


	
		
__________________________________ 
Yahoo! for Good - Make a difference this year. 
http://brand.yahoo.com/cybergivingweek2005/


From jue at jue.li  Fri Dec 30 16:10:33 2005
From: jue at jue.li (Juergen Daubert)
Date: Fri, 30 Dec 2005 17:10:33 +0100
Subject: Fwd: Re: [clc-devel] core/opt dependencies
In-Reply-To: <20051230153925.35380.qmail@web32914.mail.mud.yahoo.com>
References: <20051230152216.GA31932@jue.netz> <20051230153925.35380.qmail@web32914.mail.mud.yahoo.com>
Message-ID: <20051230161033.GA32587@jue.netz>

On Fri, Dec 30, 2005 at 07:39:25AM -0800, Jay Dolan wrote:
> I think all ports except a very select few (c build
> chain) will have dependency information.  

You are still talking about run-time dependencies ?

-- 
Juergen Daubert  |  mailto:jue at jue.li  
Korb, Germany    |  http://jue.li/crux



From jasonthomasdolan at yahoo.com  Fri Dec 30 16:30:49 2005
From: jasonthomasdolan at yahoo.com (Jay Dolan)
Date: Fri, 30 Dec 2005 08:30:49 -0800 (PST)
Subject: Fwd: Re: [clc-devel] core/opt dependencies
In-Reply-To: <20051230161033.GA32587@jue.netz>
Message-ID: <20051230163049.76795.qmail@web32909.mail.mud.yahoo.com>

--- Juergen Daubert <jue at jue.li> wrote:
> You are still talking about run-time dependencies ?

Correct.  And so, I'm not even sure that there /are/
any dependencies for them (not exactly things I know a
heck of a lot about).  But either way, the ports for
gcc, glibc, binutils, ..will not have a populated
Depends on: line because  it is not recommended that
users rebuild or update these ports in the first
place.

Thus, the ports tree is more-or-less uniform.  All
ports advertise runtime dependencies except for those
belonging to the c build chain.  In the users eyes,
these are 'do not touch' anyway.  Furthermore, setup
simply maintains a list of what is necessary to have a
functional install, and those are only preselected
(not forced).

The only classification for 'core' is 'I'm on the cd'.

Jay Dolan
Software Engineer, Systems Analyst
Windmill Cycles, Inc.
508.999.4000

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


From tilman at code-monkey.de  Fri Dec 30 16:39:13 2005
From: tilman at code-monkey.de (Tilman Sauerbeck)
Date: Fri, 30 Dec 2005 17:39:13 +0100
Subject: Fwd: Re: [clc-devel] core/opt dependencies
In-Reply-To: <20051230163049.76795.qmail@web32909.mail.mud.yahoo.com>
References: <20051230161033.GA32587@jue.netz> <20051230163049.76795.qmail@web32909.mail.mud.yahoo.com>
Message-ID: <20051230163911.GA2581@code-monkey.de>

Jay Dolan [2005-12-30 08:30]:
> Thus, the ports tree is more-or-less uniform.  All
> ports advertise runtime dependencies except for those
> belonging to the c build chain.  In the users eyes,
> these are 'do not touch' anyway.  Furthermore, setup
> simply maintains a list of what is necessary to have a
> functional install, and those are only preselected
> (not forced).

This doesn't solve the issue w/ pkgconfig (which is a build time
dependency, but it certainly doesn't belong to the c build chain).

Regards,
Tilman

-- 
GnuPG key available at
http://code-monkey.de/files/tsauerbeck-public-key.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20051230/65f98ba6/attachment.asc>

From sip at varlock.com  Fri Dec 30 22:42:43 2005
From: sip at varlock.com (Simone Rota)
Date: Fri, 30 Dec 2005 23:42:43 +0100
Subject: Fwd: Re: [clc-devel] core/opt dependencies
In-Reply-To: <20051230163911.GA2581@code-monkey.de>
References: <20051230161033.GA32587@jue.netz> <20051230163049.76795.qmail@web32909.mail.mud.yahoo.com> <20051230163911.GA2581@code-monkey.de>
Message-ID: <43B5B7E3.9010000@varlock.com>

On 12/30/05 17:39 Tilman Sauerbeck wrote:
>>Thus, the ports tree is more-or-less uniform.  All
>>ports advertise runtime dependencies except for those
>>belonging to the c build chain.  In the users eyes,
>>these are 'do not touch' anyway.  Furthermore, setup
>>simply maintains a list of what is necessary to have a
>>functional install, and those are only preselected
>>(not forced).
> 
> 
> This doesn't solve the issue w/ pkgconfig (which is a build time
> dependency, but it certainly doesn't belong to the c build chain).

True, the same could be said about findutils and sed: maybe
they're not strictly needed but they're often used at build time.

I had a deeper look at the current core collection:
I consider most of the ports to be essential for a
functional Linux setup.

Personally I'd prefer to have all the GUI-related
stuff in opt, since most of my installations are
server related; my concept of 'do not touch' includes
all the other core ports and goes a litlle beyond
the mere toolchain.

I understand this view is totally subjective,
anyway as stated before this way is a lot easier
for packagers since it provides a well-defined
list of implicit dependencies that are available
on a minimal (but not to the extreme) CRUX system.

That said I think this adantage is valueable not only
at CRUX installation time.

Regards,
Simone


-- 
Simone Rota           WEB : http://www.varlock.com
Bergamo, Italy        MAIL: sip at varlock.com


From trac at crux.nu  Sat Dec 31 08:28:12 2005
From: trac at crux.nu (CRUX)
Date: Sat, 31 Dec 2005 08:28:12 -0000
Subject: [clc-devel] =?utf-8?b?UmU6IFtDUlVYXSAjMjM6IEJyb2tlbiBQb3J0OiAgZ3RrIDIuOC45LTE=?=
In-Reply-To: <053.81a4dfa8c5edc6d37a1562429499d241@crux.nu>
References: <053.81a4dfa8c5edc6d37a1562429499d241@crux.nu>
Message-ID: <062.a626dad2fb44b5cbb4ac5da273cd1f26@crux.nu>

#23: Broken Port:  gtk 2.8.9-1
-------------------+--------------------------------------------------------
       Id:  23     |      Status:  closed                  
Component:  ports  |    Modified:  Sat Dec 31 09:28:11 2005
 Severity:  major  |   Milestone:                          
 Priority:  high   |     Version:                          
    Owner:  per    |    Reporter:  anonymous               
-------------------+--------------------------------------------------------
Changes (by jaeger):

  * resolution:  => fixed
  * status:  new => closed

Comment:

 This has been fixed with the newer release of the custom ISO. Please be
 aware that the updated ISO is unsupported by the CRUX or CLC communities
 as a whole and all further issues should be directed to me via email.

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/23>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Sat Dec 31 08:31:17 2005
From: trac at crux.nu (CRUX)
Date: Sat, 31 Dec 2005 08:31:17 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2331=3A_iproute2_missing_from_vpnc?=
In-Reply-To: <053.2d6dc77dd97a9b55f942bf3e6515bb9a@crux.nu>
References: <053.2d6dc77dd97a9b55f942bf3e6515bb9a@crux.nu>
Message-ID: <062.14829336862a84cf49625f7159b2994e@crux.nu>

#31: iproute2 missing from vpnc
--------------------+-------------------------------------------------------
       Id:  31      |      Status:  closed                  
Component:  ports   |    Modified:  Sat Dec 31 09:31:17 2005
 Severity:  normal  |   Milestone:                          
 Priority:  high    |     Version:                          
    Owner:  jaeger  |    Reporter:  sten                    
--------------------+-------------------------------------------------------
Changes (by jaeger):

  * resolution:  => wontfix
  * status:  new => closed

Comment:

 The 'iproute2' port, while a dependency of vpnc, is not one I maintain.
 Feel free to submit one via personal httpup repository to the 'contrib'
 collection.

-- 
Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/31>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Sat Dec 31 09:16:57 2005
From: trac at crux.nu (CRUX)
Date: Sat, 31 Dec 2005 09:16:57 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2335=3A_missing_dependency_for_gtk?=
Message-ID: <053.1ecea0de2d3209d4c77ef7f975f76871@crux.nu>

#35: missing dependency for gtk
--------------------+-------------------------------------------------------
       Id:  35      |      Status:  new                     
Component:  ports   |    Modified:  Sat Dec 31 10:16:57 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  per     |    Reporter:  anonymous               
--------------------+-------------------------------------------------------
 gtk does not compile if libtiff is not installed.

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/35>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Sat Dec 31 09:17:55 2005
From: trac at crux.nu (CRUX)
Date: Sat, 31 Dec 2005 09:17:55 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2336=3A_libtiff_version_bump?=
Message-ID: <053.5b71e68da05e1462d47f018c2f74822e@crux.nu>

#36: libtiff version bump
---------------------------+------------------------------------------------
       Id:  36             |      Status:  new                     
Component:  doc / website  |    Modified:  Sat Dec 31 10:17:55 2005
 Severity:  normal         |   Milestone:                          
 Priority:  normal         |     Version:                          
    Owner:  per            |    Reporter:  anonymous               
---------------------------+------------------------------------------------
 version bumped to 3.8.0.

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/36>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Sat Dec 31 09:18:30 2005
From: trac at crux.nu (CRUX)
Date: Sat, 31 Dec 2005 09:18:30 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2336=3A_libtiff_version_bump?=
In-Reply-To: <053.5b71e68da05e1462d47f018c2f74822e@crux.nu>
References: <053.5b71e68da05e1462d47f018c2f74822e@crux.nu>
Message-ID: <062.2ed9faa2c0eaa0bcd6400dee18730c54@crux.nu>

#36: libtiff version bump
--------------------+-------------------------------------------------------
       Id:  36      |      Status:  new                     
Component:  ports   |    Modified:  Sat Dec 31 10:18:29 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  per     |    Reporter:  anonymous               
--------------------+-------------------------------------------------------
Changes (by anonymous):

  * component:  doc / website => ports

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/36>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Sat Dec 31 09:57:19 2005
From: trac at crux.nu (CRUX)
Date: Sat, 31 Dec 2005 09:57:19 -0000
Subject: [clc-devel] =?utf-8?q?=5BCRUX=5D_=2337=3A_x11-fonts-dejavu_and_prt-get?=
Message-ID: <053.379aa379815c72887bfd999dcd38d4db@crux.nu>

#37: x11-fonts-dejavu and prt-get
----------------------------+-----------------------------------------------
       Id:  37              |      Status:  new                     
Component:  ports           |    Modified:  Sat Dec 31 10:57:19 2005
 Severity:  normal          |   Milestone:                          
 Priority:  normal          |     Version:                          
    Owner:  Rene Lengwinat  |    Reporter:  anonymous               
----------------------------+-----------------------------------------------
 the x11-fonts-dejavu port creates the archive dejavu-ttf#2.0-1.pkg.tar.gz
 while prt-get expects x11-fonts-dejavu#2.0-1.pkg.tar.gz.

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/37>
CRUX <http://crux.nu/>
CRUX


From trac at crux.nu  Sat Dec 31 20:05:25 2005
From: trac at crux.nu (CRUX)
Date: Sat, 31 Dec 2005 20:05:25 -0000
Subject: [clc-devel] =?utf-8?q?Re=3A_=5BCRUX=5D_=2335=3A_missing_dependency_for_gtk?=
In-Reply-To: <053.1ecea0de2d3209d4c77ef7f975f76871@crux.nu>
References: <053.1ecea0de2d3209d4c77ef7f975f76871@crux.nu>
Message-ID: <062.150087e910b3169d7f9829204dbcdb3b@crux.nu>

#35: missing dependency for gtk
--------------------+-------------------------------------------------------
       Id:  35      |      Status:  new                     
Component:  ports   |    Modified:  Sat Dec 31 21:05:25 2005
 Severity:  normal  |   Milestone:                          
 Priority:  normal  |     Version:                          
    Owner:  per     |    Reporter:  anonymous               
--------------------+-------------------------------------------------------
Comment (by sten):

 I have libtiff installed on two sytems, and gtk-2.8.9-1 compiles fine on
 both.

-- 
Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/35>
CRUX <http://crux.nu/>
CRUX