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

2012-08-01 Thread Arch Website Notification
=== Signoff report for [community-testing] ===
https://www.archlinux.org/packages/signoffs/

There are currently:
* 3 new packages in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 0 fully signed off packages
* 22 packages missing signoffs
* 2 packages 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.)


== New packages in [community-testing] in last 24 hours (3 total) ==

* systemd-arch-units-20120704-2 (any)
* tp_smapi-0.41-5 (i686)
* tp_smapi-0.41-5 (x86_64)


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

* systemd-arch-units-20120704-2 (any)
0/2 signoffs
* cdfs-2.6.27-26 (i686)
0/2 signoffs
* mailman-2.1.15-2 (i686)
0/2 signoffs
* ndiswrapper-1.57-18 (i686)
0/2 signoffs
* open-vm-tools-modules-2012.05.21-6 (i686)
0/2 signoffs
* r8168-8.031.00-8 (i686)
0/2 signoffs
* rt3562sta-2.4.1.1-11 (i686)
0/2 signoffs
* sage-mathematics-5.1-3 (i686)
0/2 signoffs
* slmodem-2.9.11-67 (i686)
0/2 signoffs
* vhba-module-20120422-6 (i686)
0/2 signoffs
* virtualbox-modules-4.1.18-6 (i686)
0/2 signoffs
* cdfs-2.6.27-26 (x86_64)
0/2 signoffs
* mailman-2.1.15-2 (x86_64)
0/2 signoffs
* ndiswrapper-1.57-18 (x86_64)
0/2 signoffs
* open-vm-tools-modules-2012.05.21-6 (x86_64)
0/2 signoffs
* r8168-8.031.00-8 (x86_64)
0/2 signoffs
* rt3562sta-2.4.1.1-11 (x86_64)
0/2 signoffs
* sage-mathematics-5.1-3 (x86_64)
0/2 signoffs
* vhba-module-20120422-6 (x86_64)
0/2 signoffs
* virtualbox-modules-4.1.18-6 (x86_64)
0/2 signoffs

== Incomplete signoffs for [unknown] (2 total) ==

* tp_smapi-0.41-5 (i686)
0/2 signoffs
* tp_smapi-0.41-5 (x86_64)
0/2 signoffs


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

* mailman-2.1.15-2 (x86_64), since 2012-07-15
* mailman-2.1.15-2 (i686), since 2012-07-15


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

1. allan - 11 signoffs
2. stephane - 8 signoffs
3. lfleischer - 6 signoffs
4. eric - 4 signoffs
5. tomegun - 2 signoffs



Re: [aur-general] Fwd: [pacman-dev] Help adding support for BZR, CVZ, DARCS to makepkg

2012-08-01 Thread Menachem Moystoviz
On Mon, Jul 23, 2012 at 5:10 PM, Markus Unterwaditzer
 wrote:
> Am I understanding this correctly when I read that makepkg is going to have 
> sort of native support for VCS?
>
> -- Markus
>
> Dave Reisner  wrote:
>
>>Forwarding to aur-general, as there's likely a larger corpus of people
>>who could potentially be affected by this...
>>
>>Allan's a bit overly dramatic about this -- the current (old) PKGBUILDs
>>will continue to mostly work, but I would expect that they'll break in
>>quiet and interesting ways (e.g. pkgver won't be updated).
>>
>>- Forwarded message from Allan McRae  -
>>
>>> Date: Mon, 23 Jul 2012 21:57:34 +1000
>>> From: Allan McRae 
>>> To: Discussion list for pacman development 
>>> Subject: [pacman-dev] Help adding support for BZR, CVZ, DARCS to
>>makepkg
>>>
>>> On my VCS branch, makepkg now supports git, svn and hg.  That
>>accounts
>>> for ~91.5% of all VCS PKGBUILDs in the AUR.  Here are rough AUR
>>package
>>> counts for those that are interested:
>>>
>>> git: 4002
>>> svn: 1771
>>> hg: 498
>>> bzr: 364
>>> cvs: 186
>>> darcs: 29
>>>
>>> I will write the code to add bzr, cvs and darcs support back, but I
>>need
>>> help given I know nothing about these systems.
>>>
>>>
>>> What I will need:
>>>
>>> 1) How to checkout a repo to a given folder
>>>
>>> 2) What url "fragments" need supported (e.g. git can build from a
>>> branch, tag or commit; svn can build from a given revision).
>>>
>>> 3) How to create a working copy of the checked out repo (i.e. "copy"
>>the
>>> primary checkout folder) and how to get it to the specified
>>> branch/tag/commit/whatever.  That can be in all one step.
>>>
>>>
>>> makepkg will not support these protocols with pacman-4.1 if I don't
>>get
>>> that information (or someone else does not provide a patch).
>>>
>>> Allan
>>>
>>
>>- End forwarded message -
>

As Markus said, is there native support in makepkg for VCSs (i.e. git,
bzr, hg, darcs, svn,...) or is this just a discussion regarding a
feature request?
If it's the former, how come it's not documented in the wiki? It would
simplify my git PKGBUILDS greatly.
If it's the latter, then I'm very interested, and am willing to
provide any assistance needed - just point me to the code.

M


[aur-general] [Request merge] kdeplasma-addons-applets-miniplayer / kdeplasma-applets-miniplayer

2012-08-01 Thread SpinFlo
please merge https://aur.archlinux.org/packages.php?ID=54477 into
https://aur.archlinux.org/packages.php?ID=60825

greetings


Re: [aur-general] Remove request for a package

2012-08-01 Thread Thibault Suzanne

Hi

I recently created a package mlorg-git. Unfortunately, the first 
PKGBUILD uloaded on the AUR named the package mlorg. I noticed the error 
and submitted a new package named mlorg-git, and then flagged 
out-of-date the mlorg package. Is it possible to delete the mlorg one ?


mlorg: https://aur.archlinux.org/packages.php?ID=61386
mlorg-git: https://aur.archlinux.org/packages.php?ID=61387

Thanks
Thibault Suzanne



Re: [aur-general] Fwd: [pacman-dev] Help adding support for BZR, CVZ, DARCS to makepkg

2012-08-01 Thread Buce
On Wed, Aug 1, 2012 at 6:05 AM, Menachem Moystoviz wrote:

> On Mon, Jul 23, 2012 at 5:10 PM, Markus Unterwaditzer
>  wrote:
> > Am I understanding this correctly when I read that makepkg is going to
> have sort of native support for VCS?
> >
> > -- Markus
> >
> > Dave Reisner  wrote:
> >
> >>Forwarding to aur-general, as there's likely a larger corpus of people
> >>who could potentially be affected by this...
> >>
> >>Allan's a bit overly dramatic about this -- the current (old) PKGBUILDs
> >>will continue to mostly work, but I would expect that they'll break in
> >>quiet and interesting ways (e.g. pkgver won't be updated).
> >>
> >>- Forwarded message from Allan McRae  -
> >>
> >>> Date: Mon, 23 Jul 2012 21:57:34 +1000
> >>> From: Allan McRae 
> >>> To: Discussion list for pacman development 
> >>> Subject: [pacman-dev] Help adding support for BZR, CVZ, DARCS to
> >>makepkg
> >>>
> >>> On my VCS branch, makepkg now supports git, svn and hg.  That
> >>accounts
> >>> for ~91.5% of all VCS PKGBUILDs in the AUR.  Here are rough AUR
> >>package
> >>> counts for those that are interested:
> >>>
> >>> git: 4002
> >>> svn: 1771
> >>> hg: 498
> >>> bzr: 364
> >>> cvs: 186
> >>> darcs: 29
> >>>
> >>> I will write the code to add bzr, cvs and darcs support back, but I
> >>need
> >>> help given I know nothing about these systems.
> >>>
> >>>
> >>> What I will need:
> >>>
> >>> 1) How to checkout a repo to a given folder
> >>>
> >>> 2) What url "fragments" need supported (e.g. git can build from a
> >>> branch, tag or commit; svn can build from a given revision).
> >>>
> >>> 3) How to create a working copy of the checked out repo (i.e. "copy"
> >>the
> >>> primary checkout folder) and how to get it to the specified
> >>> branch/tag/commit/whatever.  That can be in all one step.
> >>>
> >>>
> >>> makepkg will not support these protocols with pacman-4.1 if I don't
> >>get
> >>> that information (or someone else does not provide a patch).
> >>>
> >>> Allan
> >>>
> >>
> >>- End forwarded message -
> >
>
> As Markus said, is there native support in makepkg for VCSs (i.e. git,
> bzr, hg, darcs, svn,...) or is this just a discussion regarding a
> feature request?
> If it's the former, how come it's not documented in the wiki? It would
> simplify my git PKGBUILDS greatly.
> If it's the latter, then I'm very interested, and am willing to
> provide any assistance needed - just point me to the code.
>
> M
>

It's the latter AFAIK. I'm not a pacman dev, I just lurk on the pacman-dev
mailing list, so I can't point at specific patches, but the git repo is
here:

http://projects.archlinux.org/

I'm not sure if the relevant code is in the official pacman repo or Allan's
working tree. These may also be of interest:

http://www.archlinux.org/pacman/
http://www.archlinux.org/pacman/HACKING.html
http://www.archlinux.org/pacman/submitting-patches.html

If this isn't the info you need, it might be worthwhile to ask around on
the pacman-dev mailing list. HTH.


Re: [aur-general] Package deletion request

2012-08-01 Thread Ike Devolder
Op dinsdag 31 juli 2012 14:42:40 schreef Patrice Peterson:
> Hi,
> 
> Please delete my tm-tools package [1]. I was being an idiot and didn't
> notice it already existed as tmtools [2].
> 
> Thanks in advance,
> Patrice
> 
> [1] https://aur.archlinux.org/packages.php?ID=59994
> [2] https://aur.archlinux.org/packages.php?ID=55169

it was deleted, but not notified here (now it is :p)
thx

--Ike

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


Re: [aur-general] disown request: zoneminder

2012-08-01 Thread Ike Devolder
Op dinsdag 31 juli 2012 23:13:46 schreef Vojtech Aschenbrenner:
> Hello.
> 
> I'd like to adopt zoneminder[1] package, it compilation fails, patches
> are available and I'd like to repair it.
> 
> Marked out of date since 19th July 2012.
> Author answered once in the comments but did no repair.
> Author is not responding to email.
> 
> Regards
> Vojtech
> 
> [1] https://aur.archlinux.org/packages.php?ID=15847

My general perception is in general buhrietoe is responsive in the comments so 
maybe he/she is on holiday. my opinion is to give it a little bit more time 
since we are in the holiday season.

buhrietoe, if you are not on holiday could you at least leave a comment why 
the patches are not taken or should not be taken, or some other reason. thx

--Ike

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


Re: [aur-general] away

2012-08-01 Thread Ike Devolder
Op maandag 30 juli 2012 06:43:52 schreef Xyne:
> Ike Devolder wrote:
> >Hi,
> >
> >I'll be away for a couple of days, normally everything should get updated
> >automatically while i'm out.
> 
> How are you updating things automatically?
> 
> 
> Regards,
> Xyne

cronjobs on a server :)
i have to add more but most are already to be found:
https://github.com/BlackIkeEagle/archbuild

--Ike

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


Re: [aur-general] Remove request for a package

2012-08-01 Thread Ike Devolder
Op woensdag 1 augustus 2012 15:56:45 schreef Thibault Suzanne:
> Hi
> 
> I recently created a package mlorg-git. Unfortunately, the first
> PKGBUILD uloaded on the AUR named the package mlorg. I noticed the error
> and submitted a new package named mlorg-git, and then flagged
> out-of-date the mlorg package. Is it possible to delete the mlorg one ?
> 
> mlorg: https://aur.archlinux.org/packages.php?ID=61386
> mlorg-git: https://aur.archlinux.org/packages.php?ID=61387
> 
> Thanks
> Thibault Suzanne

mlorg got blown away
thx

--Ike

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


Re: [aur-general] [Request merge] kdeplasma-addons-applets-miniplayer / kdeplasma-applets-miniplayer

2012-08-01 Thread Ike Devolder
Op woensdag 1 augustus 2012 15:51:23 schreef SpinFlo:
> please merge https://aur.archlinux.org/packages.php?ID=54477 into
> https://aur.archlinux.org/packages.php?ID=60825
> 
> greetings

merged, thx

--Ike

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


Re: [aur-general] away

2012-08-01 Thread Dave Reisner
On Wed, Aug 01, 2012 at 05:47:17PM +0200, Ike Devolder wrote:
> Op maandag 30 juli 2012 06:43:52 schreef Xyne:
> > Ike Devolder wrote:
> > >Hi,
> > >
> > >I'll be away for a couple of days, normally everything should get updated
> > >automatically while i'm out.
> > 
> > How are you updating things automatically?
> > 
> > 
> > Regards,
> > Xyne
> 
> cronjobs on a server :)
> i have to add more but most are already to be found:
> https://github.com/BlackIkeEagle/archbuild
> 
> --Ike

So you're blindly signing and pushing packages based on the fact that
they compile?


Re: [aur-general] away

2012-08-01 Thread Ike Devolder
Op woensdag 1 augustus 2012 11:49:58 schreef Dave Reisner:
> On Wed, Aug 01, 2012 at 05:47:17PM +0200, Ike Devolder wrote:
> > Op maandag 30 juli 2012 06:43:52 schreef Xyne:
> > > Ike Devolder wrote:
> > > >Hi,
> > > >
> > > >I'll be away for a couple of days, normally everything should get
> > > >updated
> > > >automatically while i'm out.
> > > 
> > > How are you updating things automatically?
> > > 
> > > 
> > > Regards,
> > > Xyne
> > 
> > cronjobs on a server :)
> > i have to add more but most are already to be found:
> > https://github.com/BlackIkeEagle/archbuild
> > 
> > --Ike
> 
> So you're blindly signing and pushing packages based on the fact that
> they compile?

yes why not ?

--Ike

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


Re: [aur-general] away

2012-08-01 Thread Ike Devolder
Op woensdag 1 augustus 2012 18:03:20 schreef u:
> Op woensdag 1 augustus 2012 11:49:58 schreef Dave Reisner:
> > On Wed, Aug 01, 2012 at 05:47:17PM +0200, Ike Devolder wrote:
> > > Op maandag 30 juli 2012 06:43:52 schreef Xyne:
> > > > Ike Devolder wrote:
> > > > >Hi,
> > > > >
> > > > >I'll be away for a couple of days, normally everything should get
> > > > >updated
> > > > >automatically while i'm out.
> > > > 
> > > > How are you updating things automatically?
> > > > 
> > > > 
> > > > Regards,
> > > > Xyne
> > > 
> > > cronjobs on a server :)
> > > i have to add more but most are already to be found:
> > > https://github.com/BlackIkeEagle/archbuild
> > > 
> > > --Ike
> > 
> > So you're blindly signing and pushing packages based on the fact that
> > they compile?
> 
> yes why not ?
> 
> --Ike

i could modify the script that they land in community-testing first

--Ike

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


Re: [aur-general] away

2012-08-01 Thread Taylor Lookabaugh
On 08/01/12 09:04, Ike Devolder wrote:
> Op woensdag 1 augustus 2012 18:03:20 schreef u:
>> Op woensdag 1 augustus 2012 11:49:58 schreef Dave Reisner:
>>> On Wed, Aug 01, 2012 at 05:47:17PM +0200, Ike Devolder wrote:
 Op maandag 30 juli 2012 06:43:52 schreef Xyne:
> Ike Devolder wrote:
>> Hi,
>>
>> I'll be away for a couple of days, normally everything should get
>> updated
>> automatically while i'm out.
>
> How are you updating things automatically?
>
>
> Regards,
> Xyne

 cronjobs on a server :)
 i have to add more but most are already to be found:
 https://github.com/BlackIkeEagle/archbuild

 --Ike
>>>
>>> So you're blindly signing and pushing packages based on the fact that
>>> they compile?
>>
>> yes why not ?
>>
>> --Ike
> 
> i could modify the script that they land in community-testing first
> 
> --Ike
> 
what if the signing key was tampered with? How would you know?

-- 
Taylor Lookabaugh



signature.asc
Description: OpenPGP digital signature


Re: [aur-general] away

2012-08-01 Thread Stéphane Gaudreault

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Le 2012-08-01 12:04, Ike Devolder a écrit :
> Op woensdag 1 augustus 2012 18:03:20 schreef u:
>> Op woensdag 1 augustus 2012 11:49:58 schreef Dave Reisner:
>>> On Wed, Aug 01, 2012 at 05:47:17PM +0200, Ike Devolder wrote:
 Op maandag 30 juli 2012 06:43:52 schreef Xyne:
> Ike Devolder wrote:
>> Hi,
>>
>> I'll be away for a couple of days, normally everything should get
>> updated
>> automatically while i'm out.
>
> How are you updating things automatically?
>
>
> Regards,
> Xyne

 cronjobs on a server :)
 i have to add more but most are already to be found:
 https://github.com/BlackIkeEagle/archbuild

 --Ike
>>>
>>> So you're blindly signing and pushing packages based on the fact that
>>> they compile?
>>
>> yes why not ?
>>
>> --Ike
>
> i could modify the script that they land in community-testing first
>
> --Ike

Compiling != Working, so I think it is a good practice for a maintainer
to test packages before uploading them.

In some case this could be difficult to do (eg massive rebuild for a
libname change) and in these cases it is ok to "blindly" push package on
the basis that is compile and test it later. In any case, I would expect
that a package is minimally tested before it goes to the repos.

Stéphane
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJQGVYvAAoJEOpoNuGrRBGWT7QIALr88yM242d4ub4eQQQgZYJk
Ub6M+6IYwzho8rkO6YwyoNDCREVBWCf30LBbCobBjeUy+s93BByhd9CG7UL9JBaa
UtRc1LCKMczzmJheoH/fAdxHy+my6Ye8NaAh+v8vuK0pd86nJLxkw1TsSCcwtjSi
+F4jLy/FrigkCClPFEY8CKDQY4pl6mbvP4NE559ufZHdLJQTlMMD0HLYCmedb2W4
OWbbMylmXGEmPL9Enx7nk67nh17HceAZVkIUKGwfx1SwWBdDynwZ4/eMISImpSX2
qoYOE5Th7c7I/zpXYRaDWzVzRR32rI4MZE8xsAjMV/kFR6UtQrhBp4vRsMWJIPM=
=nVW1
-END PGP SIGNATURE-



Re: [aur-general] away

2012-08-01 Thread Ike Devolder
Op woensdag 1 augustus 2012 09:14:40 schreef Taylor Lookabaugh:
> On 08/01/12 09:04, Ike Devolder wrote:
> > Op woensdag 1 augustus 2012 18:03:20 schreef u:
> >> Op woensdag 1 augustus 2012 11:49:58 schreef Dave Reisner:
> >>> On Wed, Aug 01, 2012 at 05:47:17PM +0200, Ike Devolder wrote:
>  Op maandag 30 juli 2012 06:43:52 schreef Xyne:
> > Ike Devolder wrote:
> >> Hi,
> >> 
> >> I'll be away for a couple of days, normally everything should get
> >> updated
> >> automatically while i'm out.
> > 
> > How are you updating things automatically?
> > 
> > 
> > Regards,
> > Xyne
>  
>  cronjobs on a server :)
>  i have to add more but most are already to be found:
>  https://github.com/BlackIkeEagle/archbuild
>  
>  --Ike
> >>> 
> >>> So you're blindly signing and pushing packages based on the fact that
> >>> they compile?
> >> 
> >> yes why not ?
> >> 
> >> --Ike
> > 
> > i could modify the script that they land in community-testing first
> > 
> > --Ike
> 
> what if the signing key was tampered with? How would you know?

This machine is not accessible from the internet, but indeed has a connection 
out to the internet.
pacman would warn you that the key is not correct.

--Ike

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


Re: [aur-general] away

2012-08-01 Thread Ike Devolder
Op woensdag 1 augustus 2012 12:15:43 schreef Stéphane Gaudreault:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Le 2012-08-01 12:04, Ike Devolder a écrit :
> > Op woensdag 1 augustus 2012 18:03:20 schreef u:
> >> Op woensdag 1 augustus 2012 11:49:58 schreef Dave Reisner:
> >>> On Wed, Aug 01, 2012 at 05:47:17PM +0200, Ike Devolder wrote:
>  Op maandag 30 juli 2012 06:43:52 schreef Xyne:
> > Ike Devolder wrote:
> >> Hi,
> >>
> >> I'll be away for a couple of days, normally everything should get
> >> updated
> >> automatically while i'm out.
> >
> > How are you updating things automatically?
> >
> >
> > Regards,
> > Xyne
> 
>  cronjobs on a server :)
>  i have to add more but most are already to be found:
>  https://github.com/BlackIkeEagle/archbuild
> 
>  --Ike
> >>>
> >>> So you're blindly signing and pushing packages based on the fact that
> >>> they compile?
> >>
> >> yes why not ?
> >>
> >> --Ike
> >
> > i could modify the script that they land in community-testing first
> >
> > --Ike
>
> Compiling != Working, so I think it is a good practice for a maintainer
> to test packages before uploading them.
>
> In some case this could be difficult to do (eg massive rebuild for a
> libname change) and in these cases it is ok to "blindly" push package on
> the basis that is compile and test it later. In any case, I would expect
> that a package is minimally tested before it goes to the repos.
>
> Stéphane
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.19 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJQGVYvAAoJEOpoNuGrRBGWT7QIALr88yM242d4ub4eQQQgZYJk
> Ub6M+6IYwzho8rkO6YwyoNDCREVBWCf30LBbCobBjeUy+s93BByhd9CG7UL9JBaa
> UtRc1LCKMczzmJheoH/fAdxHy+my6Ye8NaAh+v8vuK0pd86nJLxkw1TsSCcwtjSi
> +F4jLy/FrigkCClPFEY8CKDQY4pl6mbvP4NE559ufZHdLJQTlMMD0HLYCmedb2W4
> OWbbMylmXGEmPL9Enx7nk67nh17HceAZVkIUKGwfx1SwWBdDynwZ4/eMISImpSX2
> qoYOE5Th7c7I/zpXYRaDWzVzRR32rI4MZE8xsAjMV/kFR6UtQrhBp4vRsMWJIPM> =nVW1
> -END PGP SIGNATURE-

Well then i'll drop the auto-updaters for community. but in general i find this
very handy. i'll leave the scripts in the git repo for now but i'll drop the
cronjob now.

--Ike

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


Re: [aur-general] disown request: zoneminder

2012-08-01 Thread Vojtech Aschenbrenner
Excerpts from Ike Devolder's message of 2012-08-01 17:45:19 +0200:
> My general perception is in general buhrietoe is responsive in the
> comments so maybe he/she is on holiday. my opinion is to give it a
> little bit more time since we are in the holiday season.
Okay, let's wait a few days/week. Please, send an email to this list
when something changes.

Regards,
Vojtech.


signature.asc
Description: PGP signature


Re: [aur-general] away

2012-08-01 Thread Rashif Ray Rahman
On 2 August 2012 00:30, Ike Devolder  wrote:
> Op woensdag 1 augustus 2012 12:15:43 schreef Stéphane Gaudreault:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Le 2012-08-01 12:04, Ike Devolder a écrit :
>> > Op woensdag 1 augustus 2012 18:03:20 schreef u:
>> >> Op woensdag 1 augustus 2012 11:49:58 schreef Dave Reisner:
>> >>> On Wed, Aug 01, 2012 at 05:47:17PM +0200, Ike Devolder wrote:
>>  Op maandag 30 juli 2012 06:43:52 schreef Xyne:
>> > Ike Devolder wrote:
>> >> Hi,
>> >>
>> >> I'll be away for a couple of days, normally everything should get
>> >> updated
>> >> automatically while i'm out.
>> >
>> > How are you updating things automatically?
>> >
>> >
>> > Regards,
>> > Xyne
>> 
>>  cronjobs on a server :)
>>  i have to add more but most are already to be found:
>>  https://github.com/BlackIkeEagle/archbuild
>> 
>>  --Ike
>> >>>
>> >>> So you're blindly signing and pushing packages based on the fact that
>> >>> they compile?
>> >>
>> >> yes why not ?
>> >>
>> >> --Ike
>> >
>> > i could modify the script that they land in community-testing first
>> >
>> > --Ike
>>
>> Compiling != Working, so I think it is a good practice for a maintainer
>> to test packages before uploading them.
>>
>> In some case this could be difficult to do (eg massive rebuild for a
>> libname change) and in these cases it is ok to "blindly" push package on
>> the basis that is compile and test it later. In any case, I would expect
>> that a package is minimally tested before it goes to the repos.
>>
>> Stéphane
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v2.0.19 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iQEcBAEBAgAGBQJQGVYvAAoJEOpoNuGrRBGWT7QIALr88yM242d4ub4eQQQgZYJk
>> Ub6M+6IYwzho8rkO6YwyoNDCREVBWCf30LBbCobBjeUy+s93BByhd9CG7UL9JBaa
>> UtRc1LCKMczzmJheoH/fAdxHy+my6Ye8NaAh+v8vuK0pd86nJLxkw1TsSCcwtjSi
>> +F4jLy/FrigkCClPFEY8CKDQY4pl6mbvP4NE559ufZHdLJQTlMMD0HLYCmedb2W4
>> OWbbMylmXGEmPL9Enx7nk67nh17HceAZVkIUKGwfx1SwWBdDynwZ4/eMISImpSX2
>> qoYOE5Th7c7I/zpXYRaDWzVzRR32rI4MZE8xsAjMV/kFR6UtQrhBp4vRsMWJIPM=
>> =nVW1
>> -END PGP SIGNATURE-
>
> Well then i'll drop the auto-updaters for community. but in general i find 
> this
> very handy. i'll leave the scripts in the git repo for now but i'll drop the
> cronjob now.
>
> --Ike

Automating like this is very bad practice. I believe a maintainer's
job is to ensure that a package works before making it accessible to
everyone. Of course sometimes we're guilty of assuming stuff "should
probably just work" but let's not automate that attitude.

Otherwise it's OK if you push these to a testing repo me thinks. But
to do justice after you return you should check them one by one :P
Also you can do this on a case-by-case basis depending on how often
things are likely to break. Yet I think just auto building is fine but
not auto pushing.


--
GPG/PGP ID: C0711BF1


Re: [aur-general] away

2012-08-01 Thread Nicola Bignami

Il 01/08/2012 18:30, Ike Devolder ha scritto:

Well then i'll drop the auto-updaters for community. but in general i find this
very handy. i'll leave the scripts in the git repo for now but i'll drop the
cronjob now.

--Ike


Personally I think that your tool to automatically generate the updated 
packages is great and very handy. On the other side, I'm not willing to 
trust a package that has been generated automatically without any sort 
of control to be installed on my system (and I think I'm not the only 
one). The wrong thing IMHO is to automatically push the new package to 
the repo without any real test and check ("it builds" is not an answer).


I'm not a TU, but I think your tools could be used to prepare the new 
updated packages in a local pool, ready to be tested and checked and 
then *manually* fetched to the repo only if everything is fine.


Re: [aur-general] away

2012-08-01 Thread Ike Devolder
Op woensdag 1 augustus 2012 19:10:54 schreef Nicola Bignami:
> Il 01/08/2012 18:30, Ike Devolder ha scritto:
> > Well then i'll drop the auto-updaters for community. but in general i find
> > this very handy. i'll leave the scripts in the git repo for now but i'll
> > drop the cronjob now.
> > 
> > --Ike
> 
> Personally I think that your tool to automatically generate the updated
> packages is great and very handy. On the other side, I'm not willing to
> trust a package that has been generated automatically without any sort
> of control to be installed on my system (and I think I'm not the only
> one). The wrong thing IMHO is to automatically push the new package to
> the repo without any real test and check ("it builds" is not an answer).
> 
> I'm not a TU, but I think your tools could be used to prepare the new
> updated packages in a local pool, ready to be tested and checked and
> then *manually* fetched to the repo only if everything is fine.

i might move to such system over time but now i have no time to do the testing 
of the buildsystem so i will bring in the packages manually as before.

--Ike

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


Re: [aur-general] away

2012-08-01 Thread Jeremiah Dodds
Ike Devolder  writes:

> Op woensdag 1 augustus 2012 11:49:58 schreef Dave Reisner:
>> On Wed, Aug 01, 2012 at 05:47:17PM +0200, Ike Devolder wrote:
>> > Op maandag 30 juli 2012 06:43:52 schreef Xyne:
>> > > Ike Devolder wrote:
>> > > >Hi,
>> > > >
>> > > >I'll be away for a couple of days, normally everything should get
>> > > >updated
>> > > >automatically while i'm out.
>> > > 
>> > > How are you updating things automatically?
>> > > 
>> > > 
>> > > Regards,
>> > > Xyne
>> > 
>> > cronjobs on a server :)
>> > i have to add more but most are already to be found:
>> > https://github.com/BlackIkeEagle/archbuild
>> > 
>> > --Ike
>> 
>> So you're blindly signing and pushing packages based on the fact that
>> they compile?
>
> yes why not ?
>
> --Ike

As mentioned elsewhere in the thread, compiling != working.

I bet that a fair portion of testing the functionality of a given
package could be automated minus needing to write what defines
acceptance for a given package.

I doubt that you could reliably automate functionality testing for all
packages, but quite a few...

-- 
Jeremiah Dodds

github : https://github.com/jdodds
freenode   : exhortatory