2016. 07. 28, csütörtök keltezéssel 12.13-kor Balló György ezt írta:

2016. 07.  23, szombat keltezéssel 10.45-kor Balló György ezt írta:

...

2016. 07.  23, szombat keltezéssel 13.39-kor Nicola Squartini via aur- general ezt írta:

...

Hi,

My name is Nicola Squartini, long time Arch Linux user and enthusiast. I would like to become a Trusted User and György Balló offered to sponsor my application.

I confirm my sponsorship. The Atom editor and the Electron application framework are very popular nowadays, definitely we want to see them in our repositories. It's not easy to build them entirely from sources, but Nicola did a great job.

Lets start the discussion period of 5 days now.

The discussion period is over, and the voting period starts. TUs, please vote: https://aur.archlinux.org/tu/?id=86

The voting period is over. The results: Yes: 27 No: 4 Abstain: 2 Congratulation! Nicola, you become a Trusted User now. :) -- György Balló Trusted User

On Thu, Aug 4, 2016 at 12:40 PM, Johannes Löthberg via aur-general wrote:

On 04/08, Balló György via aur-general wrote:

...

2016. 07. 28, csütörtök keltezéssel 12.13-kor Balló György ezt írta:

...

2016. 07. 23, szombat keltezéssel 10.45-kor Balló György ezt írta:

...

2016. 07. 23, szombat keltezéssel 13.39-kor Nicola Squartini via aur- general ezt írta:

...

Hi,

My name is Nicola Squartini, long time Arch Linux user and enthusiast. I would like to become a Trusted User and György Balló offered to sponsor my application.

I confirm my sponsorship. The Atom editor and the Electron application framework are very popular nowadays, definitely we want to see them in our repositories. It's not easy to build them entirely from sources, but Nicola did a great job.

Lets start the discussion period of 5 days now.

The discussion period is over, and the voting period starts. TUs, please vote: https://aur.archlinux.org/tu/?id=86

The voting period is over. The results:

Yes: 27 No: 4 Abstain: 2

Congratulation! Nicola, you become a Trusted User now. :)

Congrats, and welcome to the team!

Welcome to the team!

On Thu, 2016-08-04 at 12:25 +0200, Balló György via aur-general wrote:

The voting period is over. The results:

Yes: 27 No: 4 Abstain: 2

Congratulation! Nicola, you become a Trusted User now. :)

-- György Balló Trusted User

Such a great news! I feel really honored to be part of the community. Thanks everyone for your trust in me, I will not disappoint you, and thank you György! Nicola

On Thu, Aug 04, 2016 at 10:12:10PM +0900, Nicola Squartini via aur-general wrote:

On Thu, 2016-08-04 at 12:25 +0200, Balló György via aur-general wrote:

...

The voting period is over. The results:

Yes: 27 No: 4 Abstain: 2

Congratulation! Nicola, you become a Trusted User now. :)

-- György Balló Trusted User

Such a great news! I feel really honored to be part of the community.

Thanks everyone for your trust in me, I will not disappoint you, and thank you György!

Nicola

Welcome on board. -- Ike

On Fri, 2016-08-05 at 11:03 +0200, Magnus Therning wrote:

Congratulation!Nicola, you become a Trusted User now. :)

I'm glad to see Nicola become a TU.

I was planning to weigh in on the discussion, even though I'm not a TU myself, since I've had a very impression of Nicola when interacting with him in the context of ArchHaskell.

/M

Enough, enough, too much flattering :) Nicola

On Sun, Jul 24, 2016 at 05:51:52PM +0900, Nicola Squartini via aur-general wrote:

Evolution shows "Good signature" to me.

On Sun, 2016-07-24 at 09:00 +0530, Pierre Neidhardt via aur-general wrote:

...

Don't want to sound picky, but it seems like the PGP signature of your e-mail is wrong :p

Same as Pierre here. For your second mail from today: gpg: Signature made Sun 24 Jul 2016 10:51:52 AM CEST gpg: using RSA key C847B6AEB0544167 gpg: BAD signature from "Nicola Squartini " [unknown]

On Sun, 2016-07-24 at 02:28 -0700, Patrick Burroughs (Celti) wrote:

On Sun, 24 Jul 2016 17:51:52 +0900

...

Nicola Squartini via aur-general wrote:

...

Evolution shows "Good signature" to me.

On Sun, 2016-07-24 at 09:00 +0530, Pierre Neidhardt via aur-general wrote:

...

Don't want to sound picky, but it seems like the PGP signature of your e-mail is   wrong :p

Your message fails verification here, too, both using claws-mail's

...

PGP/MIME plugin and downloading the raw message and verifying it using gpg on the command line. Have you tried manually verifying your own message yourself? Evolution may be doing non-standard things.

As an addendum, the Arch Linux Code of Conduct requires bottom– or inline-posting, not top-posting. I think any prospective TU should familiarise themselves with it, if they haven't already.

~Celti

Yes, I tried manually: I cut the text between the boundary lines ("--=- ILIhghLlBNnOJ+9zADhK" in the first email), then I replaced <LF> with <CR><LF>, and verified the signature. It may be whether or not the mail client includes the final <CR><LF> in the signature computation.

On 07/24/2016 01:29 PM, Nicola Squartini via aur-general wrote:

On Sun, 24 Jul 2016 02:28:24 -0700 "Patrick Burroughs (Celti)" wrote:

...

Your message fails verification here, too, both using claws-mail's PGP/MIME plugin and downloading the raw message and verifying it using gpg on the command line. Have you tried manually verifying your own message yourself? Evolution may be doing non-standard things.

I'm using claws-mail now, and it verifies my signature. Can you tell me if this email if verified?

Looks good now ^.^ cheers, Levente

On Sun, 2016-07-24 at 05:23 -0700, Patrick Burroughs (Celti) wrote:

perhaps it was sending both HTML and plaintext, signing the wrong one, and then mailman stripped the HTML (ruining the signature) once it was sent?

~Celti

I was indeed sending both (I disabled HTML now), and it was signing both. In fact following the procedure that I described above [1], gpg was correctly verifing the content, and the text between the boundary lines included both plain/text and HTML. [1] https://tools.ietf.org/html/rfc3156

On Sun, 2016-07-24 at 14:30 +0200, Levente Polyak wrote:

Hi Nicola,

sounds great to get atom/electron into [community].

On 07/23/2016 06:39 AM, Nicola Squartini via aur-general wrote:

...

When I first started using Atom, I didn't like the fact that the official installation procedure would push precompiled stuff into my system: as every old school Linux guy, I feel itchy using binaries not compiled by me or by the distribution of my choice.

That's the right spirit ^.^

As I always do, I take a look at those stuff and give you some feedback:

black-screen ============= - source filenames should be globally unique and must be unique when a   package gets moved into the repos. the SRCDST of all packages could   be the very same directory. Github sources are only containing   version in the tarball, therefor those should be prefixed with   something like:     ${pkgname}-${pkgver}.tar.gz::https://github...

Thanks for the tip!

caprine ======== - same unique source filename like black-screen

flaccuraterip ============== - any access to both, ${srcdir} and ${pkgdir} must be put into quotes   as they may contain spaces. both used in build() and package()

If I remember, the very first PKGBUILD was generated by a script, and I only updated the version and dependency after that. I will quote those variables.

func.

mancy ====== - same source filename uniqueness as black-screen

min ==== - again this annoying unique source filename thingie :P

haskell-happstack ================== To be honest I did not take too much time looking at the haskell repo thingie, however a small thing came into my mind while reading the build scripts: (I know you don't plan to move those, its just a small side note nothing more!): - everything that gets pulled into the repos must be able to build   without special scripts/setup, f.e. by the wrapper extra-x86_64- build   from the devtools package.

The PKGBUILDs there are managed by Magnus Therning's excellent cblrepo tool [1]. My main job there is to write patches when something goes wrong with dependencies (Haskell is very strict also about dependencies).

On 07/23/2016 06:39 AM, Nicola Squartini via aur-general wrote:

...

Haskell programming language (my favourite language, btw)

Any chance you feel like you need a new project and want to make xmonad work with wayland? :P :D

Then I should call it wmonad :D

On 07/23/2016 06:39 AM, Nicola Squartini via aur-general wrote:

...

Please don't hesitate to ask me questions, if you have any

Just our of personal interest, where are you from?

I'm from Italy, but currently I live in Japan.

cheers and have a nice Sunday, Levente

On Mon, 2016-07-25 at 15:17 +0200, Johannes Löthberg via aur-general wrote:

I've thought about using cblrepo to maintain a few things, but was  wondering how you add and make sure the ghc/distro packages are up to  date in the cblrepo database?

You use cblrepo to add new packages to your repo, or add dependencies already provided by other repos (for example my [haskell-happstack] depends on many packages in [haskell-core]). [1] cblrepo also tells you what packages in your repo have been updated in cabal, using `cblrepo update` and `cblrepo upgrades`. What it doesn't do is to track whether dependencies in [haskell-core] have been upgraded. For that I wrote a script [2]; check if it works for you. [1] https://github.com/magthe/cblrepo#using-it [2] https://github.com/tensor5/haskell-happstack/blob/master/updates.sh

On Sun, 2016-07-24 at 14:30 +0200, Levente Polyak wrote:

Any chance you feel like you need a new project and want to make xmonad work with wayland? :P :D

Judging from the comment on GitHub issue [1] it seems that unfortunatly such thing is impossible. [1] https://github.com/xmonad/xmonad/issues/38

On Mon, 2016-07-25 at 09:24 +0200, Massimiliano Torromeo wrote:

I packaged in the AUR a couple of years ago but to move it in [community] it  required to much patching to decouple it's components and, again, decided it  was not worth it. I then dropped it and moved along to use other frameworks.

The Meteor team is working on making it possible to decouple, and starting from version 1.4 Meteor will upgrade to Mongo 3.2 and Node 4.