On Thu, 2013-05-23 at 11:00 +0200, Erik Hesselink wrote:
> Hi all,
>
> I just upgraded our internal hackage to the latest HEAD. I found that
> the behavior of the 'trustees' group has changed. Previously, they
> could upload any (existing) package, but that doesn't work anymore.
Ah yes.
> This f
Hi all,
I just upgraded our internal hackage to the latest HEAD. I found that
the behavior of the 'trustees' group has changed. Previously, they
could upload any (existing) package, but that doesn't work anymore.
This functionality was very useful for us, since otherwise, we'd have
to add all our
On Wed, 2013-04-10 at 23:58 +0400, Lennart Kolmodin wrote:
> 2013/4/5 Duncan Coutts
>
> > On Thu, 2013-04-04 at 22:38 +0400, Lennart Kolmodin wrote:
> >
> > > I tried to login with my username/pw, but failed.
> > >
> > > Here's what I did:
> > > I go to a package I've published and hit "edit pack
2013/4/5 Duncan Coutts
> On Thu, 2013-04-04 at 22:38 +0400, Lennart Kolmodin wrote:
>
> > I tried to login with my username/pw, but failed.
> >
> > Here's what I did:
> > I go to a package I've published and hit "edit package information" in
> the
> > Maintainers' corner.
> > It prompts me to log
On Thu, 2013-04-04 at 22:38 +0400, Lennart Kolmodin wrote:
> I tried to login with my username/pw, but failed.
>
> Here's what I did:
> I go to a package I've published and hit "edit package information" in the
> Maintainers' corner.
> It prompts me to login.
> If I hit cancel, it shows No author
2013/3/13 Duncan Coutts
> Hi folks,
>
> I believe we're ready for alpha testing for hackage 2. The
> server is up at:
>
> http://new-hackage.haskell.org/
>
> Key points:
> * All the old data is imported (including docs)
> * Uploading is enabl
Hi folks,
I believe we're ready for alpha testing for hackage 2. The
server is up at:
http://new-hackage.haskell.org/
Key points:
* All the old data is imported (including docs)
* Uploading is enabled
* Live mirroring is also enabled
* Per-package maintainer group
vice versa?
Chris
On 18/12/2012 00:13, "Duncan Coutts" wrote:
>On Mon, 2012-12-17 at 18:45 +, Duncan Coutts wrote:
>> Hi folks,
>>
>> You may have noticed the steady stream of hackage 2 patches. The new
>> server is up again at:
>>
>>
On Mon, 2012-12-17 at 18:45 +, Duncan Coutts wrote:
> Hi folks,
>
> You may have noticed the steady stream of hackage 2 patches. The new
> server is up again at:
>
> http://new-hackage.haskell.org/
>
> Key points:
> * We've got live mirroring going (s
Hi folks,
You may have noticed the steady stream of hackage 2 patches. The new
server is up again at:
http://new-hackage.haskell.org/
Key points:
* We've got live mirroring going (sync every 30 min).
* All the old accounts are imported and the per-package maintainer
g
On Fri, Sep 07, 2012 at 04:54:08PM +0200, Erik Hesselink wrote:
> On Fri, Sep 7, 2012 at 4:28 PM, Ian Lynagh wrote:
> > On Fri, Sep 07, 2012 at 04:22:24PM +0200, Erik Hesselink wrote:
> >>
> >> I created a ticket for hackage2. Should I mark it as such (but not
> >> important)? Or will that interfe
On Fri, Sep 07, 2012 at 03:54:08PM +0100, Erik Hesselink wrote:
> Hmm, apparently I can't add labels. It's issue 1028. I don't think
> it's important to fix before migrating, but it would be nice if
> someone with privileges could label it.
The issue there is mishandling unknown repository types,
On Fri, Sep 7, 2012 at 4:28 PM, Ian Lynagh wrote:
> On Fri, Sep 07, 2012 at 04:22:24PM +0200, Erik Hesselink wrote:
>>
>> I created a ticket for hackage2. Should I mark it as such (but not
>> important)? Or will that interfere with this list?
>
> Definitely mark it hackage2. Mark it important if y
On Fri, Sep 7, 2012 at 8:48 AM, Ian Lynagh wrote:
>
> I think it would be best to use lowest-common-denominator SQL, so that
> one can set up a Hackage 2 instance with postgreq, mysql, sqlite, or
> another DB backend.
>
>
While I think that's a laudable goal in theory,
Hi Erik,
On Fri, Sep 07, 2012 at 04:22:24PM +0200, Erik Hesselink wrote:
>
> I created a ticket for hackage2. Should I mark it as such (but not
> important)? Or will that interfere with this list?
Definitely mark it hackage2. Mark it important if you think that it
needs to be fixed before we mi
Hi Ian,
I created a ticket for hackage2. Should I mark it as such (but not
important)? Or will that interfere with this list?
Erik
On Fri, Sep 7, 2012 at 4:07 PM, Ian Lynagh wrote:
>
> Hi all,
>
> FYI, I've been making tickets labelled 'hackage2' and 'important' for
> issues that we need to loo
Hi all,
FYI, I've been making tickets labelled 'hackage2' and 'important' for
issues that we need to look at before migrating to Hackage2.
The list is here:
https://github.com/haskell/cabal/issues?labels=hackage2%2Cimportant&page=1&state=open
Currently we have:
* https://github.com/haskell/caba
via already
> existing third-party plugins.Compared to MySQL, it's definitely less
> fluff, more stuff.
I think it would be best to use lowest-common-denominator SQL, so that
one can set up a Hackage 2 instance with postgreq, mysql, sqlite, or
another D
On 6 September 2012 21:06, Duncan Coutts wrote:
> On 6 September 2012 19:49, Ian Lynagh wrote:
>> * Only a single process can use the database at once. For example, if
>> the admins want a tool that will make it easier for them to approve
>> user requests, then that tool needs to be integrate
On Thu, Sep 6, 2012 at 2:49 PM, Ian Lynagh wrote:
>
> * Only a single process can use the database at once. For example, if
> the admins want a tool that will make it easier for them to approve
> user requests, then that tool needs to be integrated into the Hackage
> server (or talk to it o
On 6 September 2012 19:49, Ian Lynagh wrote:
>
> Hi all,
>
> I've had a bit of experience with Hackage 2 and acid-state now, and I'm
> not convinced that it's the best fit for us:
>
> * It's slow. It takes about 5 minutes for me to stop and then start the
On Thu, Sep 06, 2012 at 08:52:28PM +0100, Ian Lynagh wrote:
> On Thu, Sep 06, 2012 at 08:32:38PM +0100, Duncan Coutts wrote:
> >
> > From the point of view of an existing user, they will go to the new
> > site, go to a special page, enter their username and their old
> > password and a new passwor
On Thu, Sep 06, 2012 at 08:32:38PM +0100, Duncan Coutts wrote:
>
> >From the point of view of an existing user, they will go to the new
> site, go to a special page, enter their username and their old
> password and a new password (which can be the same if they like). This
> is a one off. After th
, Ian Lynagh wrote:
>
> Hi all,
>
> I've had a bit of experience with Hackage 2 and acid-state now, and I'm
> not convinced that it's the best fit for us:
>
> * It's slow. It takes about 5 minutes for me to stop and then start the
> server. It'
On 6 September 2012 19:53, Ian Lynagh wrote:
> On Thu, Sep 06, 2012 at 07:14:53PM +0100, Ross Paterson wrote:
>> On Thu, Sep 06, 2012 at 06:49:36PM +0100, Matthew Gruen wrote:
>> > To my knowledge, It's technically possible to import the old accounts.
>>
>> Why is that? I think that's worth explo
On Thu, Sep 6, 2012 at 11:53 AM, Ian Lynagh wrote:
> But if that's not the case then I can look into importing them.
>
I think that making the effort to import that data would be well
worthwhile. Thanks for looking into it.
___
cabal-devel mailing list
On Thu, Sep 6, 2012 at 11:49 AM, Ian Lynagh wrote:
> Someone pointed out that one disadvantage of traditional databases is
> that they discourage you from writing as if everything was Haskell
> datastructures in memory. For example, if you have things of type
> data Foo = Foo {
> str :
On Mon, Sep 3, 2012 at 4:35 PM, Leon Smith wrote:
> The thing is, since we have an account approval process and that we have
> a full, public log of everything that everybody's uploaded, people are
> going to notice when somebody uploads something they shouldn't.
No, it has already happened
On Thu, Sep 06, 2012 at 07:14:53PM +0100, Ross Paterson wrote:
> On Thu, Sep 06, 2012 at 06:49:36PM +0100, Matthew Gruen wrote:
> > To my knowledge, It's technically possible to import the old accounts.
>
> Why is that? I think that's worth exploring, as you'd be losing
> associations between 115
Hi all,
I've had a bit of experience with Hackage 2 and acid-state now, and I'm
not convinced that it's the best fit for us:
* It's slow. It takes about 5 minutes for me to stop and then start the
server. It's actually surprising just how slow it is, so it might be
On Thu, Sep 06, 2012 at 06:49:36PM +0100, Matthew Gruen wrote:
> To my knowledge, It's technically possible to import the old accounts.
Why is that? I think that's worth exploring, as you'd be losing
associations between 1150 users and 24456 uploads of 4442 packages.
(Not entirely, because the ol
On Thu, Sep 6, 2012 at 7:49 PM, Matthew Gruen wrote:
> I'm a little bit confused on the exact set up. The uploaders group seems to
> be roughly the same thing as the trustees group. (Except uploaders has an
> AND relationship with per-package groups as far as membership requirements
> for upload,
On Thu, Sep 6, 2012 at 10:28 AM, Duncan Coutts wrote:
> On 5 September 2012 20:22, Erik Hesselink wrote:
>
> >> Also, we haven't had a single problem that I'm aware of on Ross
> Paterson's
> >> watch as bouncer for Hackage 1.The point I'm trying to make is that
> a
> >> technical solution i
On 5 September 2012 20:22, Erik Hesselink wrote:
>> Also, we haven't had a single problem that I'm aware of on Ross Paterson's
>> watch as bouncer for Hackage 1.The point I'm trying to make is that a
>> technical solution imposes additional administrative and technical overhead
>> whereas so
The User accounts page, echoing the Hackage 1 version, says "Passwords
are stored encrypted, so if you forget yours we can't recover it, but
will need to assign a new one. Just ask."
But the account registration page doesn't even ask for an email address,
so it would be difficult for administrator
; use for the global uploaders group. So I'd propose to eventually
>> switch from the current situation, and have only per-package
>> uploaders, and no global uploaders.
>
> As a LtU admin (something more of a nightclub bouncer, really), I dislike
> the current Hackag
ecommended replacement (the "deprecated" and "superseded by" fields of
> > > the per-package "tags" file), e.g. partial-lens and binary-strict-0.3.1.
> > > These don't seem to be in Hackage 2.
> >
> > I think you can reach this function
On Mon, Sep 03, 2012 at 03:38:19PM +0100, Ross Paterson wrote:
> A few minor issues:
Thanks for the feedback!
> Several packages lack documentation. They don't say why (an issue in
> itself),
I've made a ticket for this:
https://github.com/haskell/cabal/issues/1024
> but it appears to be libra
> uploaders, and no global uploaders.
As a LtU admin (something more of a nightclub bouncer, really), I dislike
the current Hackage 2 user account process in a lot of respects. But the
approval process has worked remarkably well for LtU, we haven't had a
single spam message since requir
of
> > the per-package "tags" file), e.g. partial-lens and binary-strict-0.3.1.
> > These don't seem to be in Hackage 2.
>
> I think you can reach this functionality by going to a package and
> clicking 'maintain'. There, you can edit deprecation and p
rict-0.3.1.
> These don't seem to be in Hackage 2.
I think you can reach this functionality by going to a package and
clicking 'maintain'. There, you can edit deprecation and preferred
versions. I haven't tested if this works, though.
Erik
__
A few minor issues:
In Hackage 1 packages can be deprecated, optionally indicating a
recommended replacement (the "deprecated" and "superseded by" fields of
the per-package "tags" file), e.g. partial-lens and binary-strict-0.3.1.
These don't seem to be i
On Sat, Sep 1, 2012 at 5:10 PM, Ian Lynagh wrote:
> On Fri, Aug 31, 2012 at 01:57:55AM +0100, Ian Lynagh wrote:
>>
>> On Thu, Aug 30, 2012 at 08:13:01PM -0400, Leon Smith wrote:
>> > Ok, I tried to upload the most recent version of postgresql-simple, and I
>> > couldn't because I'm not the mainta
On Sat, Sep 1, 2012 at 7:25 PM, Ian Lynagh wrote:
> On Sat, Sep 01, 2012 at 07:11:54PM +0200, Erik Hesselink wrote:
>>
>> It's still not working. I'm trying to upload a new version of kqueue
>> (0.1.2.4). I start from
>> http://new-hackage.haskell.org/packages/upload, select the file and
>> press
On Sat, Sep 01, 2012 at 07:11:54PM +0200, Erik Hesselink wrote:
>
> It's still not working. I'm trying to upload a new version of kqueue
> (0.1.2.4). I start from
> http://new-hackage.haskell.org/packages/upload, select the file and
> press upload. This posts to http://new-hackage.haskell.org/pack
On Sat, Sep 1, 2012 at 5:11 PM, Ian Lynagh wrote:
> On Fri, Aug 31, 2012 at 11:27:46AM +0200, Erik Hesselink wrote:
>> On Fri, Aug 31, 2012 at 11:12 AM, Erik Hesselink wrote:
>> > On Fri, Aug 31, 2012 at 2:13 AM, Leon Smith wrote:
>> >> Ok, I tried to upload the most recent version of postgresql
On Fri, Aug 31, 2012 at 11:27:46AM +0200, Erik Hesselink wrote:
> On Fri, Aug 31, 2012 at 11:12 AM, Erik Hesselink wrote:
> > On Fri, Aug 31, 2012 at 2:13 AM, Leon Smith wrote:
> >> Ok, I tried to upload the most recent version of postgresql-simple, and I
> >> couldn't because I'm not the mainta
On Fri, Aug 31, 2012 at 01:57:55AM +0100, Ian Lynagh wrote:
>
> On Thu, Aug 30, 2012 at 08:13:01PM -0400, Leon Smith wrote:
> > Ok, I tried to upload the most recent version of postgresql-simple, and I
> > couldn't because I'm not the maintainer for that package.
>
> I wasn't involved in the des
On Aug 31, 2012 11:56 AM, "Ian Lynagh" wrote:
>
> On Thu, Aug 30, 2012 at 08:42:34PM -0500, Antoine Latter wrote:
> >
> > After digging a bit, the code that does this is a part of converting
> > the legacy data into the new-style backup tarball. I'm too behind on
> > how things work to know if tha
On Thu, Aug 30, 2012 at 08:42:34PM -0500, Antoine Latter wrote:
>
> After digging a bit, the code that does this is a part of converting
> the legacy data into the new-style backup tarball. I'm too behind on
> how things work to know if that's still a thing that happens or is at
> all useful :-)
I
On Fri, Aug 31, 2012 at 11:12 AM, Erik Hesselink wrote:
> On Fri, Aug 31, 2012 at 2:13 AM, Leon Smith wrote:
>> Ok, I tried to upload the most recent version of postgresql-simple, and I
>> couldn't because I'm not the maintainer for that package.
>
> What is your account name? I can add you as a
d the admins having to get involved for
>> every package, as well as every person.
>>
>
> At one point I think we tried to populate the per-package uploaders
> group as a part of the import with everyone who had historically
> uploaded the package - this relies on the historic
veryone who had historically
uploaded the package - this relies on the historic user names lining
up with the current user accounts as imported. I guess that also
relies on order-of-operations of the import getting users first.
We get by with social conventions now, so it wouldn't be terrible to
get by with them on Hackage 2.
Antoine
___
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org/mailman/listinfo/cabal-devel
[moving to cabal-dev@]
On Thu, Aug 30, 2012 at 08:13:01PM -0400, Leon Smith wrote:
> Ok, I tried to upload the most recent version of postgresql-simple, and I
> couldn't because I'm not the maintainer for that package.
>
> Has anybody ever uploaded a package that they shouldn't have on the old
Hi all,
I'd like to add "logged in info" to the Hackage 2 page template; i.e. if
not logged in then put a small login form somewhere, and if you are
logged in then show the username and provide a logout button.
I've started experimenting, and ran into a problem with the ca
ated data (i.e. actions they
perform on the Hackage site) will be the most valuable (as the
packages can be regenerated from source if need be.) For example,
using this data is how we're going to do ranking of packages. In fact,
this data is what should make Hackage 2 and improvement over Hackage
1.
rite a test prog that reads the index
>> file and look at peak memory use. Then try sharing stuff and see how
>> much it drops. This sharing optimisation would still be useful even if
>> later we go and redo GenericPackageDescription to be more compact.
>
> This should not
g stuff and see how
> much it drops. This sharing optimisation would still be useful even if
> later we go and redo GenericPackageDescription to be more compact.
This should not hold up the launch of Hackage 2 (which is very
important) but I think it's an important issue that we need
On Tue, Jul 3, 2012 at 2:27 PM, Ian Lynagh wrote:
> On Mon, Jul 02, 2012 at 08:14:01PM +0100, Duncan Coutts wrote:
>> Something to keep in mind is memory usage.
>
> Will do, but currently I don't think this is a blocker for deploying
> 2.0.
>
Isn't it the reason why the test server
(http://hackag
On Mon, Jul 02, 2012 at 08:14:01PM +0100, Duncan Coutts wrote:
> On Mon, 2012-07-02 at 12:25 +0100, Ian Lynagh wrote:
>
> > Conclusion
> > --
> >
> > I think the following are the blockers for deploying Hackage 2:
> >
> > * #911 upload perms; m
On Mon, Jul 2, 2012 at 4:07 PM, Conrad Parker wrote:
>
> I think we should avoid manual approvals; I know several people who
> have excellent, working, used in-production, cabalified Haskell code
> but for whatever reason they are reluctant to request an account --
> however they have code on git
On 3 July 2012 03:14, Duncan Coutts wrote:
> On Mon, 2012-07-02 at 12:25 +0100, Ian Lynagh wrote:
>> Hi all,
>>
>> I'm planning to spend some time, on behalf of the Industrial Haskell
>> Group, working on Hackage 2 in the coming weeks.
>
> [..]
>
On Mon, 2012-07-02 at 12:25 +0100, Ian Lynagh wrote:
> Hi all,
>
> I'm planning to spend some time, on behalf of the Industrial Haskell
> Group, working on Hackage 2 in the coming weeks.
[..]
> Now #913 I assume is not a blocker. #919 I assume is also not a blocker.
>
Hi all,
I'm planning to spend some time, on behalf of the Industrial Haskell
Group, working on Hackage 2 in the coming weeks.
As such, I've been trying to work out what the blockers are in terms of
actually getting the hackage 2 server live. I've started from the
"Curre
On 14 February 2012 16:10, Ben Gamari wrote:
> It seems the first task will be to identify exactly what needs to be
> done before we can begin the transition and record these tasks in a
> single place. I don't have a particularly strong opinion concerning
> where this should be (Trac, the Hackage
#2: move TODO stuff into this tracking system
+---
Reporter: ijones |Owner: ijones
Type: task | Status: closed
Priority: normal |Milestone:
Component: miscell
#2: move TODO stuff into this tracking system
-+--
Reporter: ijones |Owner: ijones
Type: task| Status: closed
Priority: normal |Milestone:
Component: misc| Version: HEA
67 matches
Mail list logo
