Re: [aur-general] AUR 3.0.0 released

2014-06-05 Thread Lukas Fleischer
On Thu, 05 Jun 2014 at 08:12:23, Florian Bruhin wrote:
> * Hector Martinez-Seara  [2014-06-05 08:56:00 +0300]:
> > Notice that before AUR 3 just calling "makepkg --source" was enough. Any
> > good reason
> > for this change? If there any possibility as Philip proposes that this is
> > done in the serve side?
> [...]
> But I agree, adjusting the permissions probably should (and AFAIK
> could be done safely) on the server side.
> 

No, we do not (and will never) modify the tarball on the server-side. If
that really annoys you, just write a simple wrapper script around
mkaurball or patch mkaurball so that it adjusts the permissions.

Note that this issue will vanish soon anyway since the next major AUR
release will provide Git repositories for all AUR packages. You will no
longer need to create source tarballs.

> Florian
> 
> -- 
> http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
>  GPG 0xFD55A072 | http://the-compiler.org/pubkey.asc
>  I love long mails! | http://email.is-not-s.ms/


Re: [aur-general] AUR 3.0.0 released

2014-06-05 Thread Florian Bruhin
* Lukas Fleischer  [2014-06-05 09:03:29 +0200]:
> Note that this issue will vanish soon anyway since the next major AUR
> release will provide Git repositories for all AUR packages. You will no
> longer need to create source tarballs.

That sounds intresting! Is there some kind of specification or some
more notes regarding this? I wonder how permissions/merges/etc. will
be dealt with.

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
 GPG 0xFD55A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


pgppKapleloOk.pgp
Description: PGP signature


Re: [aur-general] AUR 3.0.0 released

2014-06-05 Thread Lukas Fleischer
On Thu, 05 Jun 2014 at 09:08:48, Florian Bruhin wrote:
> * Lukas Fleischer  [2014-06-05 09:03:29 +0200]:
> > Note that this issue will vanish soon anyway since the next major AUR
> > release will provide Git repositories for all AUR packages. You will no
> > longer need to create source tarballs.
> 
> That sounds intresting! Is there some kind of specification or some
> more notes regarding this? I wonder how permissions/merges/etc. will
> be dealt with.
> 

Check [1] for some of the implementation details.

> Florian
> 
> -- 
> http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
>  GPG 0xFD55A072 | http://the-compiler.org/pubkey.asc
>  I love long mails! | http://email.is-not-s.ms/

[1] https://mailman.archlinux.org/pipermail/aur-dev/2014-June/002770.html


Re: [aur-general] AUR 3.0.0 released

2014-06-05 Thread William Giokas
On Thu, Jun 05, 2014 at 09:28:15AM +0200, Lukas Fleischer wrote:
> On Thu, 05 Jun 2014 at 09:08:48, Florian Bruhin wrote:
> > * Lukas Fleischer  [2014-06-05 09:03:29 +0200]:
> > > Note that this issue will vanish soon anyway since the next major AUR
> > > release will provide Git repositories for all AUR packages. You will no
> > > longer need to create source tarballs.
> > 
> > That sounds intresting! Is there some kind of specification or some
> > more notes regarding this? I wonder how permissions/merges/etc. will
> > be dealt with.
> > 
> 
> Check [1] for some of the implementation details.

On top of that, looking directly at permissions, git only tracks the
executable bit, so the only permissions that git knows of for regular
files is 755 and 644.

As a demonstration::

$ git ls-files
x
$ ls -l
-rw-r--r-- 1 wgiokas users 0 Jun  5 02:47 x
$ chmod u+x x
$ ls -l
-rwxr--r-- 1 wgiokas users 0 Jun  5 02:47 x
$ git diff
diff --git a/x b/x
old mode 100644
new mode 100755

> 
> > Florian
> > 
> > -- 
> > http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
> >  GPG 0xFD55A072 | http://the-compiler.org/pubkey.asc
> >  I love long mails! | http://email.is-not-s.ms/
> 
> [1] https://mailman.archlinux.org/pipermail/aur-dev/2014-June/002770.html

-- 
William Giokas | KaiSforza | http://kaictl.net/
GnuPG Key: 0x73CD09CF
Fingerprint: F73F 50EF BBE2 9846 8306  E6B8 6902 06D8 73CD 09CF


pgpeemF0jzUdR.pgp
Description: PGP signature


[aur-general] Signoff report for [community-testing]

2014-06-05 Thread Arch Website Notification
=== Signoff report for [community-testing] ===
https://www.archlinux.org/packages/signoffs/

There are currently:
* 0 new packages in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 0 fully signed off packages
* 1 package missing signoffs
* 1 package older than 14 days

(Note: the word 'package' as used here refers to packages as grouped by
pkgbase, architecture, and repository; e.g., one PKGBUILD produces one
package per architecture, even if it is a split package.)



== Incomplete signoffs for [community] (1 total) ==

* waf-1.7.15-2 (any)
1/2 signoffs


== All packages in [community-testing] for more than 14 days (1 total) ==

* waf-1.7.15-2 (any), since 2014-03-21


== Top five in signoffs in last 24 hours ==

1. bpiotrowski - 3 signoffs
2. ronald - 2 signoffs
3. anatolik - 1 signoffs



Re: [aur-general] AUR 3.0.0 released

2014-06-05 Thread Lukas Fleischer
On Thu, 05 Jun 2014 at 09:52:11, William Giokas wrote:
> On Thu, Jun 05, 2014 at 09:28:15AM +0200, Lukas Fleischer wrote:
> > On Thu, 05 Jun 2014 at 09:08:48, Florian Bruhin wrote:
> > > * Lukas Fleischer  [2014-06-05 09:03:29 +0200]:
> > > > Note that this issue will vanish soon anyway since the next major AUR
> > > > release will provide Git repositories for all AUR packages. You will no
> > > > longer need to create source tarballs.
> > > 
> > > That sounds intresting! Is there some kind of specification or some
> > > more notes regarding this? I wonder how permissions/merges/etc. will
> > > be dealt with.
> > > 
> > 
> > Check [1] for some of the implementation details.
> 
> On top of that, looking directly at permissions, git only tracks the
> executable bit, so the only permissions that git knows of for regular
> files is 755 and 644.
> [...]

Yes, that's exactly what I wanted to suggest when saying that "this
issue will vanish soon anyway since the next major AUR release will
provide Git repositories for all AUR packages". Sorry for being vague.


Re: [aur-general] orphan request: xfce-theme-greybird

2014-06-05 Thread Evgeniy Alekseev
5 июня 2014 г. 9:29:44 GMT+03:00, Bjoern Franke  пишет:
>please orphan xfce-theme-greybird[1].
>It's marked out of date since 17.03.14, I mailed luolimao on 22.05.14
>and got no reply.

Orphaned, feel free to adopt it.
-- 
С уважением, Е.Алексеев.
Sirencelly yours, E.Alekseev.

e-mail: darkarca...@mail.ru
ICQ: 407-398-235
Jabber: arca...@jabber.ru


Re: [aur-general] Delete request: quassel-mysql

2014-06-05 Thread Evgeniy Alekseev
5 июня 2014 г. 1:42:05 GMT+03:00, Jerome Leclanche  пишет:
>https://aur.archlinux.org/packages/quassel-mysql/
>
>This has long been upstreamed.

Done, thank you.
-- 
С уважением, Е.Алексеев.
Sirencelly yours, E.Alekseev.

e-mail: darkarca...@mail.ru
ICQ: 407-398-235
Jabber: arca...@jabber.ru


[aur-general] AUR 3.1.0 released

2014-06-05 Thread Lukas Fleischer
Hello,

I am pleased to announce that AUR 3.1.0 has just been released. The
official AUR setup [1] has already been updated.

This release includes several bug fixes, the RPC interface now reports
package base IDs, long lists of source files are collapsed and a "Search
wiki" link has been added to the package details page. Versioned
conflicts (provides, replaces) are now displayed properly.

For a comprehensive list of changes, please consult the Git log [2]. As
usual, bugs should be reported to the AUR bug tracker [3].

[1] https://aur.archlinux.org/
[2] https://projects.archlinux.org/aur.git/log/?id=v3.1.0
[3] https://bugs.archlinux.org/index.php?project=2


Re: [aur-general] Orphan request: l3afpad

2014-06-05 Thread Steven Honeyman
Still no email reply from the current maintainer after 2 weeks, and he
hasn't updated or commented on it at all - so would it be possible to
orphan [1] so that I can update it please?

Thanks,
Steven.

[1] https://aur.archlinux.org/packages/l3afpad

On 3 June 2014 17:46, Steven Honeyman  wrote:
> It was 11 days ago I sent the email. Would you like me to reply again
> to this in 3 more days if he has not responded?
>
> Thank-you,
> Steven.
>
>
> On 3 June 2014 11:38, Maxime Gauduin  wrote:
>> On Sat, May 31, 2014 at 4:50 PM, Steven Honeyman 
>> wrote:
>>
>>> The AUR package "l3afpad" is in need of an update as the source file
>>> has changed URL and it will soon stop working when the author takes
>>> his old page down. I'm willing to take over as maintainer for this
>>> package if possible.
>>>
>>> I already emailed the current maintainer, but he hasn't replied.
>>>
>>> https://aur.archlinux.org/packages/l3afpad
>>>
>>> Thanks,
>>> Steven
>>>
>>
>> When did you email him? He last logged in last month so you will need to
>> wait 2 weeks before I can disown the package.
>>
>> --
>> Maxime


Re: [aur-general] Orphan request: l3afpad

2014-06-05 Thread Evgeniy Alekseev
On Thursday 05 June 2014 17:42:12 Steven Honeyman wrote:
> Still no email reply from the current maintainer after 2 weeks, and he
> hasn't updated or commented on it at all - so would it be possible to
> orphan [1] so that I can update it please?
> 
> On 3 June 2014 17:46, Steven Honeyman  wrote:
> > It was 11 days ago I sent the email. Would you like me to reply again
> > to this in 3 more days if he has not responded?
> > 
> > On 3 June 2014 11:38, Maxime Gauduin  wrote:
> >> On Sat, May 31, 2014 at 4:50 PM, Steven Honeyman
> >>  wrote:
> >>> The AUR package "l3afpad" is in need of an update as the source file
> >>> has changed URL and it will soon stop working when the author takes
> >>> his old page down. I'm willing to take over as maintainer for this
> >>> package if possible.
> >>> 
> >>> I already emailed the current maintainer, but he hasn't replied.
> >>> 
> >>> https://aur.archlinux.org/packages/l3afpad
> >>> 
> >> When did you email him? He last logged in last month so you will need to
> >> wait 2 weeks before I can disown the package.

Ok, done.
-- 
С уважением, Е.Алексеев.
Sincerely yours, E.Alekseev.

e-mail: darkarca...@mail.ru
ICQ: 407-398-235
Jabber: arca...@jabber.ru

signature.asc
Description: This is a digitally signed message part.


[aur-general] Packages deletion request

2014-06-05 Thread Audric Schiltknecht
Hello,

Please delete the following packages:

* opensand-margouilla [1] and opensand-env-plane [2]. They are not
needed anymore in the new version of opensand.
* opensand-gse-plugin [3], opensand-ule-plugin [4],
opnsand-rohc-plugin [5], opensand-mpeg-plugin [6] and
opensand-atm-aal5-plugin [7]. All these plugins are now provided in
the new opensand-core version.


Thanks!

[1]: https://aur.archlinux.org/packages/opensand-margouilla/
[2]: https://aur.archlinux.org/packages/opensand-env-plane/
[3]: https://aur.archlinux.org/packages/opensand-gse-plugin/
[4]: https://aur.archlinux.org/packages/opensand-ule-plugin/
[5]: https://aur.archlinux.org/packages/opensand-rohc-plugin/
[6]: https://aur.archlinux.org/packages/opensand-mpeg-plugin/
[7]: https://aur.archlinux.org/packages/opensand-atm-aal5-plugin/


Re: [aur-general] Packages deletion request

2014-06-05 Thread Felix Yan
On Thursday, June 05, 2014 20:19:47 Audric Schiltknecht wrote:
> Hello,
> 
> Please delete the following packages:
> 
> * opensand-margouilla [1] and opensand-env-plane [2]. They are not
> needed anymore in the new version of opensand.
> * opensand-gse-plugin [3], opensand-ule-plugin [4],
> opnsand-rohc-plugin [5], opensand-mpeg-plugin [6] and
> opensand-atm-aal5-plugin [7]. All these plugins are now provided in
> the new opensand-core version.
> 
> 
> Thanks!
> 
> [1]: https://aur.archlinux.org/packages/opensand-margouilla/
> [2]: https://aur.archlinux.org/packages/opensand-env-plane/
> [3]: https://aur.archlinux.org/packages/opensand-gse-plugin/
> [4]: https://aur.archlinux.org/packages/opensand-ule-plugin/
> [5]: https://aur.archlinux.org/packages/opensand-rohc-plugin/
> [6]: https://aur.archlinux.org/packages/opensand-mpeg-plugin/
> [7]: https://aur.archlinux.org/packages/opensand-atm-aal5-plugin/

All removed, thanks.

Regards,
Felix Yan

signature.asc
Description: This is a digitally signed message part.