gspcav1-fbcondecor package installation errors

View: New views
5 Messages — Rating Filter:   Alert me  
< Prev | 1 - 2 | Next >

Re: Package search for community repo

by Abhishek Dasgupta :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

2009/7/23 Roman Kyrylych <roman.kyrylych@...>:
> This is absolutely no-go because this way bugtracker will be flooded
> with out-of date messages
> that have no useful information.

Agreed. The web interface is the best place to mark out-of-date. For
now, people can send to the maintainer directly.

> +1 for complete merging community into main website (with limited
> permissions for TUs)
> and removing community-related part of AUR
> (with a notice that if there was some important info in comments - it should be
> reported as bugs or it will be lost)

This information could be kept archived somewhere. A simple HTML dump
of the all the community package pages would suffice.

> (if there would be possibility to limit permissions per category then
> I would love
> to merge Community Packages bugtracker project as well,
> but that's not an option at this time).

That'd be really nice if possible. Then I wouldn't have to file two
bugs for each namcap tag.

--
Abhishek

Re: Package search for community repo

by Loui Chang :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Thu 23 Jul 2009 22:04 +0530, Abhishek Dasgupta wrote:

> 2009/7/23 Roman Kyrylych <roman.kyrylych@...>:
> > This is absolutely no-go because this way bugtracker will be flooded
> > with out-of date messages
> > that have no useful information.
>
> Agreed. The web interface is the best place to mark out-of-date. For
> now, people can send to the maintainer directly.
>
> > +1 for complete merging community into main website (with limited
> > permissions for TUs)
> > and removing community-related part of AUR
> > (with a notice that if there was some important info in comments -
> > it should be reported as bugs or it will be lost)
>
> This information could be kept archived somewhere. A simple HTML dump
> of the all the community package pages would suffice.

Well, I won't remove the packages outright. I'll just dummify them so
they won't appear in the AUR. Any particular reason that you'd want to
archive it though?


Re: Package search for community repo

by Abhishek Dasgupta :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

2009/7/23 Loui Chang <louipc.ist@...>:
> On Thu 23 Jul 2009 22:04 +0530, Abhishek Dasgupta wrote:
>> This information could be kept archived somewhere. A simple HTML dump
>> of the all the community package pages would suffice.
>
> Well, I won't remove the packages outright. I'll just dummify them so
> they won't appear in the AUR. Any particular reason that you'd want to
> archive it though?
>

Archiving the pages is easy, also some comments in the package
pages are useful for now.

--
Abhishek

Re: Package search for community repo

by Loui Chang :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Fri 24 Jul 2009 08:59 +0530, Abhishek Dasgupta wrote:

> 2009/7/23 Loui Chang <louipc.ist@...>:
> > On Thu 23 Jul 2009 22:04 +0530, Abhishek Dasgupta wrote:
> >> This information could be kept archived somewhere. A simple HTML dump
> >> of the all the community package pages would suffice.
> >
> > Well, I won't remove the packages outright. I'll just dummify them so
> > they won't appear in the AUR. Any particular reason that you'd want to
> > archive it though?
>
> Archiving the pages is easy, also some comments in the package
> pages are useful for now.

I know archiving is easy. I could just do a mysqldump.
Is there an application that you need the data for?

Re: Package search for community repo

by Abhishek Dasgupta :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

2009/7/24 Loui Chang <louipc.ist@...>:
> I know archiving is easy. I could just do a mysqldump.
> Is there an application that you need the data for?
>

No, just the data could be useful in the future.

--
Abhishek
< Prev | 1 - 2 | Next >