Provide ical-pull or meetup?

[groks]

Just installed ical-pull from the package manager as it appeared as 'new' after a refresh. Looks good.

Couple of problems:

• it is called ical-pull but it offers (provide 'metup)
• it requires 'web but this is not declared in the Packages-requires line in the comments so install compilation fails
• ~/work/org/ical-pull-diary.org is hard-coded

[nicferrier]

Thanks! Give it another go?

[groks]

Eye-balled it, looks good!

I'm having this problem:

https://github.com/nicferrier/elmarmalade/issues/55

...so no updated package is showing up. I'll give it another go if that clears up or I get some time to try the git version.

Thanks.

[nicferrier]

If you have that problem you can switch back to the http urls for the archives. marmalade will send redirects to the https and it should work.

[groks]

Same error even when specifying an http for package-archives...

[nicferrier]

Errr... are you absolutely sure? no one ever reported that before.

[groks]

I've tried with both this:

(setq package-archives '(("marmalade" . "https://marmalade-repo.org/packages/")))

and this:

(setq package-archives '(("marmalade" . "http://marmalade-repo.org/packages/")))

and in both cases, if I set this:

(setq gnutls-log-level 999)

before calling package-refresh-contents then I get this in the *Messages* buffer:

Contacting host: marmalade-repo.org:443
gnutls.c: [5] REC[0xcac9ff0]: Preparing Packet Application Data(23) with length: 1413 and min pad: 0
gnutls.c: [9] ENC[0xcac9ff0]: cipher: AES-256-GCM, MAC: AEAD, Epoch: 1
gnutls.c: [11] WRITE: enqueued 1442 bytes for 0xd. Total 1442 bytes.
gnutls.c: [11] WRITE FLUSH: 1442 bytes in buffer.
gnutls.c: [11] WRITE: wrote 1442 bytes, 0 bytes left.
gnutls.c: [5] REC[0xcac9ff0]: Sent Packet[3] Application Data(23) in epoch 1 and length: 1442
gnutls.c: [10] READ: Got 5 bytes from 0xd
gnutls.c: [10] READ: read 5 bytes from 0xd
gnutls.c: [10] RB: Have 0 bytes into buffer. Adding 5 bytes.
gnutls.c: [10] RB: Requested 5 bytes
gnutls.c: [5] REC[0xcac9ff0]: SSL 3.3 Application Data packet received. Epoch 0, length: 157
gnutls.c: [5] REC[0xcac9ff0]: Expected Packet Application Data(23)
gnutls.c: [5] REC[0xcac9ff0]: Received Packet Application Data(23) with length: 157
gnutls.c: [10] READ: Got 157 bytes from 0xd
gnutls.c: [10] READ: read 157 bytes from 0xd
gnutls.c: [10] RB: Have 5 bytes into buffer. Adding 157 bytes.
gnutls.c: [10] RB: Requested 162 bytes
gnutls.c: [5] REC[0xcac9ff0]: Decrypted Packet[8] Application Data(23) with length: 133
gnutls.c: [13] BUF[REC]: Inserted 133 bytes of Data(23)
gnutls.c: [10] READ: Got 0 bytes from 0xd
gnutls.c: [10] READ: read 0 bytes from 0xd
gnutls.c: [3] ASSERT: gnutls_buffers.c:554
gnutls.c: [3] ASSERT: gnutls_record.c:1058
gnutls.c: [3] ASSERT: gnutls_record.c:1179
gnutls.c: [3] ASSERT: gnutls_record.c:1431
gnutls.c: [0] (Emacs) fatal error: The TLS connection was non-properly terminated.
gnutls.c: [2] (Emacs) Deallocating x509 credentials
gnutls.c: [5] REC[0xcac9ff0]: Start of epoch cleanup
gnutls.c: [5] REC[0xcac9ff0]: End of epoch cleanup
gnutls.c: [5] REC[0xcac9ff0]: Epoch #1 freed

Here's the http-only trace, which looks identical:

Contacting host: marmalade-repo.org:80
gnutls.c: [5] REC[0x143300f0]: Preparing Packet Application Data(23) with length: 1413 and min pad: 0
gnutls.c: [9] ENC[0x143300f0]: cipher: AES-256-GCM, MAC: AEAD, Epoch: 1
gnutls.c: [11] WRITE: enqueued 1442 bytes for 0x15. Total 1442 bytes.
gnutls.c: [11] WRITE FLUSH: 1442 bytes in buffer.
gnutls.c: [11] WRITE: wrote 1442 bytes, 0 bytes left.
gnutls.c: [5] REC[0x143300f0]: Sent Packet[3] Application Data(23) in epoch 1 and length: 1442
gnutls.c: [10] READ: Got 5 bytes from 0x15
gnutls.c: [10] READ: read 5 bytes from 0x15
gnutls.c: [10] RB: Have 0 bytes into buffer. Adding 5 bytes.
gnutls.c: [10] RB: Requested 5 bytes
gnutls.c: [5] REC[0x143300f0]: SSL 3.3 Application Data packet received. Epoch 0, length: 157
gnutls.c: [5] REC[0x143300f0]: Expected Packet Application Data(23)
gnutls.c: [5] REC[0x143300f0]: Received Packet Application Data(23) with length: 157
gnutls.c: [10] READ: Got 157 bytes from 0x15
gnutls.c: [10] READ: read 157 bytes from 0x15
gnutls.c: [10] RB: Have 5 bytes into buffer. Adding 157 bytes.
gnutls.c: [10] RB: Requested 162 bytes
gnutls.c: [5] REC[0x143300f0]: Decrypted Packet[8] Application Data(23) with length: 133
gnutls.c: [13] BUF[REC]: Inserted 133 bytes of Data(23)
gnutls.c: [10] READ: Got 0 bytes from 0x15
gnutls.c: [10] READ: read 0 bytes from 0x15
gnutls.c: [3] ASSERT: gnutls_buffers.c:554
gnutls.c: [3] ASSERT: gnutls_record.c:1058
gnutls.c: [3] ASSERT: gnutls_record.c:1179
gnutls.c: [3] ASSERT: gnutls_record.c:1431
gnutls.c: [0] (Emacs) fatal error: The TLS connection was non-properly terminated.
gnutls.c: [2] (Emacs) Deallocating x509 credentials
gnutls.c: [5] REC[0x143300f0]: Start of epoch cleanup
gnutls.c: [5] REC[0x143300f0]: End of epoch cleanup
gnutls.c: [5] REC[0x143300f0]: Epoch #1 freed

[nicferrier]

you're not M-x package-refresh-contents after the setq's?

[groks]

Yes, I am calling package-refresh-contents after setting package-archives to both https and http. And it seems to be respected as the first line of log out put shows connections to either 443 or 80.