Allison Randal dijo [Wed, Dec 19, 2007 at 03:27:33PM +0200]:
>
> How difficult would it be to set up a debian-parrot group? It would
> consist of the specific Parrot team members who have responsibility
> for packaging and uploading Parrot (understanding that each would
> need to apply as a DM). W
Allison Randal dijo [Wed, Dec 19, 2007 at 02:14:35PM +0200]:
> Indeed. Parrot is a complete virtual machine similar to Mono or
> Java. As such, it's likely that Parrot will ultimately split into a
> few more packages than it currently has, including parrot-modules,
> parrot-dev, and packages for ru
Jeremiah Foster wrote:
How difficult would it be to set up a debian-parrot group?
Not hard at all. As Martin mentioned, debian has a development machine
called alioth which hosts a GForge repository, if that is the right
word. http://alioth.debian.org/
This sounds like the ideal solution,
> > In short, "teams" i.e. debian-perl are internal debian groups with
> > upload rights.
>
> How difficult would it be to set up a debian-parrot group?
Not hard at all. As Martin mentioned, debian has a development machine
called alioth which hosts a GForge repository, if that is the right
html (left column,
> under "PTS subscription"). If you select "Advanced Mode", you
> can chose only to get bug reports.
>
> Moritz
>
> > Allison
> >
> > Moritz Lenz wrote:
> >> Good localtime(),
> >>
> >> The
> > Usually the debian maintainer is responsible for forwarding bugs,
> > since parrot is maintainer-less it appears that this didn't
> happen. I
> > will look into this and see if I can forward them.
>
> Thanks, that would be helpful.
Here is the first bug, it appears to be a debian bug an
> From: Allison Randal [mailto:[EMAIL PROTECTED]
>
> Indeed. Parrot is a complete virtual machine similar to Mono
> or Java. As such, it's likely that Parrot will ultimately
> split into a few more packages than it currently has,
> including parrot-modules, parrot-dev, and packages for
> ru
On Dec 19, 2007 10:27 AM, Allison Randal <[EMAIL PROTECTED]> wrote:
> How difficult would it be to set up a debian-parrot group? It would
> consist of the specific Parrot team members who have responsibility for
> packaging and uploading Parrot (understanding that each would need to
> apply as a D
Jeremiah Foster wrote:
That document assumes that the team "parrot-porters" is a group of
debian developers working together to maintain parrot in debian, it is a
document aimed at debian developers. However I cannot find a debian team
called "parrot-porters". I assume this is the name that the
Jeremiah Foster wrote:
Parrot is a bit of different beastie than the perl modules we normally
handle. But I am fairly certain someone here would be willing to help. I
am not very familiar with parrot aside from having read some articles on
PIR and seen a couple talks, but it is still a bit over
an.org/p/parrot.html (left column, under "PTS
subscription"). If you select "Advanced Mode", you can chose only to get
bug reports.
Moritz
> Allison
>
> Moritz Lenz wrote:
>> Good localtime(),
>>
>> The Debian packages for pugs and parrot have been o
our ticket queue? We're not aware of the 2 RC
bugs referenced by your issue #444708.
Allison
Moritz Lenz wrote:
Good localtime(),
The Debian packages for pugs and parrot have been orphaned, i.e. they
have no maintainer anymore, and will disappear from Debian if nobody
takes over:
Good localtime(),
The Debian packages for pugs and parrot have been orphaned, i.e. they
have no maintainer anymore, and will disappear from Debian if nobody
takes over:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444708
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444711
If anybody
13 matches
Mail list logo
