Re: [arch-general] Upstream urls and package descriptions

2013-08-01 Thread Gaetan Bisson
[2013-08-01 18:02:38 +0200] Karol Blazewicz: > The same upstream url can be used by many packages and standardizing > would make it a bit easier to find which packages need to have the > upstream url updated. That is just not feasible. As you noticed yourself: sometimes, a www prefix and/or slash

Re: [arch-general] Upstream urls and package descriptions

2013-08-01 Thread Allan McRae
On 02/08/13 02:02, Karol Blazewicz wrote: > Intro: > Below are some questions / ideas I came up with. I simply don't know > if anyone cares about these issues, whether there are rules or at > least suggestions how to best deal with them or is it up to the > maintainer. > > I've heard there were so

Re: [arch-general] Upstream urls and package descriptions

2013-08-01 Thread Karol Blazewicz
On Thu, Aug 1, 2013 at 11:02 PM, Myra Nelson wrote: > > The best way might be to follow Allan's suggestions on how to contribute to > Arch Linux. > > http://allanmcrae.com/2013/05/ways-to-contribute-to-arch-linux/ > > His suggestion about fixing bugs on the bug tracker also applies to filing > new

Re: [arch-general] Upstream urls and package descriptions

2013-08-01 Thread Myra Nelson
On Thu, Aug 1, 2013 at 1:23 PM, Karol Blazewicz wrote: > On Thu, Aug 1, 2013 at 6:37 PM, Rodrigo Rivas > wrote: > > On Thu, Aug 1, 2013 at 6:02 PM, Karol Blazewicz > > wrote: > > > >> I also found > >> https://www.archlinux.org/packages/extra/any/libreoffice-sid/ - ??? > >> language pack for Libr

Re: [arch-general] Upstream urls and package descriptions

2013-08-01 Thread Gaetan Bisson
[2013-08-01 20:23:18 +0200] Karol Blazewicz: > Should I open a single report for the base package e.g. > libreoffice-i18n and list which split packages need to be fixed or > open a report for each split libreoffice-* package? One report per pkgbase is good. -- Gaetan

Re: [arch-general] Upstream urls and package descriptions

2013-08-01 Thread Karol Blazewicz
On Fri, Aug 2, 2013 at 12:28 AM, Alexander Rødseth wrote: > Hi, > > > 2013/8/1 Karol Blazewicz : >> Package descriptions: >> There was an attempt at improving the descriptions last year, but it >> didn't go so well >> https://projects.archlinux.org/svntogit/community.git/commit/trunk?h=packages/bi

Re: [arch-general] Upstream urls and package descriptions

2013-08-01 Thread Alexander Rødseth
Hi, 2013/8/1 Karol Blazewicz : > Package descriptions: > There was an attempt at improving the descriptions last year, but it > didn't go so well > https://projects.archlinux.org/svntogit/community.git/commit/trunk?h=packages/bitcoin&id=bd4647fb433c517c03fb08f869944dc987372a69 In my opinion, the

Re: [arch-general] Upstream urls and package descriptions

2013-08-01 Thread Karol Blazewicz
On Thu, Aug 1, 2013 at 6:37 PM, Rodrigo Rivas wrote: > On Thu, Aug 1, 2013 at 6:02 PM, Karol Blazewicz > wrote: > >> I also found >> https://www.archlinux.org/packages/extra/any/libreoffice-sid/ - ??? >> language pack for LibreOffice >> https://www.archlinux.org/packages/extra/any/libreoffice-tt/

Re: [arch-general] Upstream urls and package descriptions

2013-08-01 Thread Thomas Bächler
Am 01.08.2013 18:02, schrieb Karol Blazewicz: > Upstream urls: > I found that dozens of packages in the repos have an upstream url that > prints 'Page Not Found' in one way or another. Should I open bug > reports for these packages or does nobody care about it? I could also > check if the source is

Re: [arch-general] Upstream urls and package descriptions

2013-08-01 Thread Rodrigo Rivas
On Thu, Aug 1, 2013 at 6:02 PM, Karol Blazewicz wrote: > I also found > https://www.archlinux.org/packages/extra/any/libreoffice-sid/ - ??? > language pack for LibreOffice > https://www.archlinux.org/packages/extra/any/libreoffice-tt/ - TT ? > language pack for LibreOffice > > What's this? > I've

[arch-general] Upstream urls and package descriptions

2013-08-01 Thread Karol Blazewicz
Intro: Below are some questions / ideas I came up with. I simply don't know if anyone cares about these issues, whether there are rules or at least suggestions how to best deal with them or is it up to the maintainer. I've heard there were some plans wrt a build server that would periodically chec