Il 02/01/2013 11:03, Allan McRae ha scritto:

Devs and TUs,

Fix your mess if you run "extrapkg" on a package in the community SVN or "communitypkg" on a package in the core/extra SVN.

Also, always use these tools. There were a bunch of issues that could only be caused by manually using archrelease and doing it wrong.

These can break ABS updating. I just fixed eight packages...

Allan

Could you please list which packages you've fixed? So we know the dev/tu are doing it wrong. -- Arch Linux Developer http://www.archlinux.org http://www.archlinux.it

On 02/01/13 23:44, Allan McRae wrote:

On 02/01/13 21:55, Giovanni Scafora wrote:

...

Il 02/01/2013 11:03, Allan McRae ha scritto:

...

Devs and TUs,

Fix your mess if you run "extrapkg" on a package in the community SVN or "communitypkg" on a package in the core/extra SVN.

Also, always use these tools. There were a bunch of issues that could only be caused by manually using archrelease and doing it wrong.

These can break ABS updating. I just fixed eight packages...

Allan

Could you please list which packages you've fixed? So we know the dev/tu are doing it wrong.

If you really want to know, look for my SVN commits in both repos for the last day with commit messages that are fairly obvious...

But git does not show empty directories such as repo/x86_64 being delete... So here goes the packages: sparsehash python-pymongo lib32-llvm lib32-libffi go erlang-cl ginac libcompizconfig

On 3 January 2013 14:53, Alexander Rødseth wrote:

Hi,

I'm guilty of python-pymongo, go and erlang-cl. I was unaware of the need to use communitypkg instead of extrapkg for community packages, until now, and will start using communitypkg instead.

That doesn't make much sense to me. I mean, how have you been maintaining packages so far without using communitypkg?

On 3 January 2013 15:09, Alexander Rødseth wrote:

Hi,

...

That doesn't make much sense to me. I mean, how have you been maintaining packages so far without using communitypkg?

Sorry, I was a bit too quick there. I have been using communitypkg all along. I confused it with extra-i686-build and extra-x86_64-build, which I do use for community packages. I have not used extrapkg at all, only communitypkg.

That does make more sense; thanks for clearing that up. :)

On 04/01/13 00:42, Alexander Rødseth wrote:

Hi again,

2013/1/3 Evangelos Foutras :

...

On 3 January 2013 15:09, Alexander Rødseth wrote: That does make more sense; thanks for clearing that up. :)

Thanks for clearing that up yourself. :)

But, now I'm confused, because I never used "extrapkg" at all on those three packages that I maintain. I don't see any indication anywhere in the changelog for those three that "extrapkg" have been used either (if that's where it would show up).

Allan, what is your source for that "extrapkg" has been used on these three?

python-pymongo go erlang-cl

There were directories in the repos/ directory of SVN that should not be there. Dirrectories like extra-x86_64. Either than or directories name "x86_64" which implied using archrelease manually and wrong...

And what could be the reason that someone would run extrapkg on these?

Stupidity.

[2013-01-04 01:08:20 +0100] Alexander Rødseth:

"Stupidity" in response to creating two directories by mistake and svn commit messages like "fix shit". Are you 12?

Can you never just acknowledge your mistakes and move on? This list is not to discuss proper use of the word "stupidity"; it's to get things forward. Do your linguistic nitpicking somewhere else. Thanks. -- Gaetan