making teideb repository

newer
Fwd: Re: [oxygen-tei] Synchronize...

James Cummings

24 Sep 2015 24 Sep '15

5:59 p.m.

As Martin predicted if I go into the teideb directory and 'make go' (which runs the apt-ftparchive, gzips the packages and signs them), it fails on the signing process. Martin was composing a list of questions to ask him... so this might be one of them if we wish to continue to release debian packages. (Or we figure it out enough to set up a new package repository, preferrably on www.tei-c.org rather than an Oxford machine.) === You need a passphrase to unlock the secret key for user: "Sebastian Rahtz " 1024-bit DSA key, ID 86A9A497, created 2001-11-27 gpg: Invalid passphrase; please try again ... === -James -- Dr James Cummings, Academic IT Services, University of Oxford TEI Consultations: tei@it.ox.ac.uk

Show replies by date

Lou Burnard

24 Sep 24 Sep

6:14 p.m.

New subject: [tei-council] making teideb repository

I am going to see Sebastian tomorrow morning so will ask him if you like Sent from my Samsung Galaxy Tab®|PRO -------- Original message -------- From: James Cummings Date:09/24/2015 16:59 (GMT+00:00) To: tei-council@lists.tei-c.org Subject: [tei-council] making teideb repository As Martin predicted if I go into the teideb directory and 'make go' (which runs the apt-ftparchive, gzips the packages and signs them), it fails on the signing process. Martin was composing a list of questions to ask him... so this might be one of them if we wish to continue to release debian packages. (Or we figure it out enough to set up a new package repository, preferrably on www.tei-c.orghttp://www.tei-c.org rather than an Oxford machine.) === You need a passphrase to unlock the secret key for user: "Sebastian Rahtz " 1024-bit DSA key, ID 86A9A497, created 2001-11-27 gpg: Invalid passphrase; please try again ... === -James -- Dr James Cummings, Academic IT Services, University of Oxford TEI Consultations: tei@it.ox.ac.uk -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council PLEASE NOTE: postings to this list are publicly archived

Martin Holmes

6:14 p.m.

New subject: [tei-council] making teideb repository

Does it fail because it wants a password you don't have, or because your not SR and so you don't have access to his keys? Did you su rahtz? If we decide to take over building of the packages and move them, there's stuff that has to be done that I don't actually understand. Existing users, who are subscribed to the repo on the Oxford server, will need to remove that repo from their sources and substitute another one. I don't know how (assuming there is a way) to make that requirement known to package users, other than crude things like making the existing repository disappear so that they get errors when they do apt-get update and go off looking for answers. There's some research and learning to do here, so I think we need a little workgroup. Meanwhile, I've asked a simple question on the TEI-L list. If it turns out no-one is using the packages at all, then we might consider abandoning them. Cheers, Martin On 15-09-24 08:59 AM, James Cummings wrote:

...

As Martin predicted if I go into the teideb directory and 'make go' (which runs the apt-ftparchive, gzips the packages and signs them), it fails on the signing process. Martin was composing a list of questions to ask him... so this might be one of them if we wish to continue to release debian packages. (Or we figure it out enough to set up a new package repository, preferrably on www.tei-c.org rather than an Oxford machine.)

=== You need a passphrase to unlock the secret key for user: "Sebastian Rahtz " 1024-bit DSA key, ID 86A9A497, created 2001-11-27

gpg: Invalid passphrase; please try again ... ===

-James

Martin Holmes

6:17 p.m.

New subject: [tei-council] making teideb repository

...

because your not SR

Gawd. Time to resign from being editor of the Journal. On 15-09-24 09:14 AM, Martin Holmes wrote:

...

Does it fail because it wants a password you don't have, or because your not SR and so you don't have access to his keys? Did you su rahtz?

If we decide to take over building of the packages and move them, there's stuff that has to be done that I don't actually understand. Existing users, who are subscribed to the repo on the Oxford server, will need to remove that repo from their sources and substitute another one. I don't know how (assuming there is a way) to make that requirement known to package users, other than crude things like making the existing repository disappear so that they get errors when they do apt-get update and go off looking for answers. There's some research and learning to do here, so I think we need a little workgroup.

Meanwhile, I've asked a simple question on the TEI-L list. If it turns out no-one is using the packages at all, then we might consider abandoning them.

Cheers, Martin

On 15-09-24 08:59 AM, James Cummings wrote:

...
As Martin predicted if I go into the teideb directory and 'make go' (which runs the apt-ftparchive, gzips the packages and signs them), it fails on the signing process. Martin was composing a list of questions to ask him... so this might be one of them if we wish to continue to release debian packages. (Or we figure it out enough to set up a new package repository, preferrably on www.tei-c.org rather than an Oxford machine.)

=== You need a passphrase to unlock the secret key for user: "Sebastian Rahtz " 1024-bit DSA key, ID 86A9A497, created 2001-11-27

gpg: Invalid passphrase; please try again ... ===

-James

James Cummings

6:23 p.m.

New subject: [tei-council] making teideb repository

On 24/09/15 17:14, Martin Holmes wrote:

...

Does it fail because it wants a password you don't have, or because your not SR and so you don't have access to his keys? Did you su rahtz?

I had 'su rahtz' before.

...

If we decide to take over building of the packages and move them, there's stuff that has to be done that I don't actually understand. Existing users, who are subscribed to the repo on the Oxford server, will need to remove that repo from their sources and substitute another one. I don't know how (assuming there is a way) to make that requirement known to package users, other than crude things like making the existing repository disappear so that they get errors when they do apt-get update and go off looking for answers. There's some research and learning to do here, so I think we need a little workgroup.

Yes, luckily, the type of person who is subscribed to the teideb repository is likely to be the type of person who won't mind switching the url to a new one. But yes... I think we need a decision on: - should we be maintaining debian packages? - if so, which packages? - where should it be located?

...

Meanwhile, I've asked a simple question on the TEI-L list. If it turns out no-one is using the packages at all, then we might consider abandoning them.

I use them but don't need to. -James -- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford

Martin Holmes

6:28 p.m.

New subject: [tei-council] making teideb repository

Roberto's response is interesting; I've never really understood what the TEI Oxygen package does. Does anyone know? Does it simply provide a customized version of Oxygen that incorporates TEI stuff? If so, presumably it was obsoleted when the plugin was created. Cheers, Martin On 15-09-24 09:23 AM, James Cummings wrote:

...

On 24/09/15 17:14, Martin Holmes wrote:

...
Does it fail because it wants a password you don't have, or because your not SR and so you don't have access to his keys? Did you su rahtz?

I had 'su rahtz' before.

...
If we decide to take over building of the packages and move them, there's stuff that has to be done that I don't actually understand. Existing users, who are subscribed to the repo on the Oxford server, will need to remove that repo from their sources and substitute another one. I don't know how (assuming there is a way) to make that requirement known to package users, other than crude things like making the existing repository disappear so that they get errors when they do apt-get update and go off looking for answers. There's some research and learning to do here, so I think we need a little workgroup.

Yes, luckily, the type of person who is subscribed to the teideb repository is likely to be the type of person who won't mind switching the url to a new one. But yes... I think we need a decision on: - should we be maintaining debian packages? - if so, which packages? - where should it be located?

...
Meanwhile, I've asked a simple question on the TEI-L list. If it turns out no-one is using the packages at all, then we might consider abandoning them.

I use them but don't need to.

-James

Kevin Hawkins

6:35 p.m.

New subject: [tei-council] making teideb repository

According to http://wiki.tei-c.org/index.php/OXygen, the tei-oxygen Debian packages provides "automatic updates for new versions of the stylesheet library" (by which, I believe, we mean http://wiki.tei-c.org/index.php/Tei-xsl ). --Kevin On 9/24/15 11:28 AM, Martin Holmes wrote:

...

Roberto's response is interesting; I've never really understood what the TEI Oxygen package does. Does anyone know? Does it simply provide a customized version of Oxygen that incorporates TEI stuff? If so, presumably it was obsoleted when the plugin was created.

Cheers, Martin

On 15-09-24 09:23 AM, James Cummings wrote:

...
On 24/09/15 17:14, Martin Holmes wrote:

...
Does it fail because it wants a password you don't have, or because your not SR and so you don't have access to his keys? Did you su rahtz?

I had 'su rahtz' before.

...
If we decide to take over building of the packages and move them, there's stuff that has to be done that I don't actually understand. Existing users, who are subscribed to the repo on the Oxford server, will need to remove that repo from their sources and substitute another one. I don't know how (assuming there is a way) to make that requirement known to package users, other than crude things like making the existing repository disappear so that they get errors when they do apt-get update and go off looking for answers. There's some research and learning to do here, so I think we need a little workgroup.

Yes, luckily, the type of person who is subscribed to the teideb repository is likely to be the type of person who won't mind switching the url to a new one. But yes... I think we need a decision on: - should we be maintaining debian packages? - if so, which packages? - where should it be located?

...
Meanwhile, I've asked a simple question on the TEI-L list. If it turns out no-one is using the packages at all, then we might consider abandoning them.

I use them but don't need to.

-James

James Cummings

6:37 p.m.

New subject: [tei-council] making teideb repository

The benefit, if the package was maintained, is that those of us using ubuntu or debian never have to think to install a new version of oxygen, it just gets updated, added to menus, etc. It takes out the consciously remembering to update your oxygen install. ;-) -James On 24/09/15 17:35, Kevin Hawkins wrote:

...

According to http://wiki.tei-c.org/index.php/OXygen, the tei-oxygen Debian packages provides "automatic updates for new versions of the stylesheet library" (by which, I believe, we mean http://wiki.tei-c.org/index.php/Tei-xsl ). --Kevin

On 9/24/15 11:28 AM, Martin Holmes wrote:

...
Roberto's response is interesting; I've never really understood what the TEI Oxygen package does. Does anyone know? Does it simply provide a customized version of Oxygen that incorporates TEI stuff? If so, presumably it was obsoleted when the plugin was created.

Cheers, Martin

On 15-09-24 09:23 AM, James Cummings wrote:

...
On 24/09/15 17:14, Martin Holmes wrote:

...
Does it fail because it wants a password you don't have, or because your not SR and so you don't have access to his keys? Did you su rahtz?

I had 'su rahtz' before.

...
If we decide to take over building of the packages and move them, there's stuff that has to be done that I don't actually understand. Existing users, who are subscribed to the repo on the Oxford server, will need to remove that repo from their sources and substitute another one. I don't know how (assuming there is a way) to make that requirement known to package users, other than crude things like making the existing repository disappear so that they get errors when they do apt-get update and go off looking for answers. There's some research and learning to do here, so I think we need a little workgroup.

Yes, luckily, the type of person who is subscribed to the teideb repository is likely to be the type of person who won't mind switching the url to a new one. But yes... I think we need a decision on: - should we be maintaining debian packages? - if so, which packages? - where should it be located?

...
Meanwhile, I've asked a simple question on the TEI-L list. If it turns out no-one is using the packages at all, then we might consider abandoning them.

I use them but don't need to.

-James

-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford

Kevin Hawkins

6:41 p.m.

New subject: [tei-council] making teideb repository

So the package updates not just the stylesheets but also oXygen itself? If so, I'll update the wiki to make this clear. On 9/24/15 11:37 AM, James Cummings wrote:

...

The benefit, if the package was maintained, is that those of us using ubuntu or debian never have to think to install a new version of oxygen, it just gets updated, added to menus, etc. It takes out the consciously remembering to update your oxygen install. ;-)

-James

On 24/09/15 17:35, Kevin Hawkins wrote:

...
According to http://wiki.tei-c.org/index.php/OXygen, the tei-oxygen Debian packages provides "automatic updates for new versions of the stylesheet library" (by which, I believe, we mean http://wiki.tei-c.org/index.php/Tei-xsl ). --Kevin

On 9/24/15 11:28 AM, Martin Holmes wrote:

...
Roberto's response is interesting; I've never really understood what the TEI Oxygen package does. Does anyone know? Does it simply provide a customized version of Oxygen that incorporates TEI stuff? If so, presumably it was obsoleted when the plugin was created.

Cheers, Martin

On 15-09-24 09:23 AM, James Cummings wrote:

...
On 24/09/15 17:14, Martin Holmes wrote:

...
Does it fail because it wants a password you don't have, or because your not SR and so you don't have access to his keys? Did you su rahtz?

I had 'su rahtz' before.

...
If we decide to take over building of the packages and move them, there's stuff that has to be done that I don't actually understand. Existing users, who are subscribed to the repo on the Oxford server, will need to remove that repo from their sources and substitute another one. I don't know how (assuming there is a way) to make that requirement known to package users, other than crude things like making the existing repository disappear so that they get errors when they do apt-get update and go off looking for answers. There's some research and learning to do here, so I think we need a little workgroup.

Yes, luckily, the type of person who is subscribed to the teideb repository is likely to be the type of person who won't mind switching the url to a new one. But yes... I think we need a decision on: - should we be maintaining debian packages? - if so, which packages? - where should it be located?

...
Meanwhile, I've asked a simple question on the TEI-L list. If it turns out no-one is using the packages at all, then we might consider abandoning them.

I use them but don't need to.

-James

James Cummings

9 p.m.

New subject: [tei-council] making teideb repository

I wouldn't change the wiki to say that -- since the debian package isn't currently being maintained, but yes the tei-oxygen package in debian/ubuntu provides a copy of oXygen. It comes with the oxygen-tei framework, but if people have a local install of TEI Stylesheets or Schemas is can be made to use them instead. The packages in question are: http://tei.oucs.ox.ac.uk/teideb/ -James On 24/09/15 17:41, Kevin Hawkins wrote:

...

So the package updates not just the stylesheets but also oXygen itself? If so, I'll update the wiki to make this clear.

On 9/24/15 11:37 AM, James Cummings wrote:

...
The benefit, if the package was maintained, is that those of us using ubuntu or debian never have to think to install a new version of oxygen, it just gets updated, added to menus, etc. It takes out the consciously remembering to update your oxygen install. ;-)

-James

On 24/09/15 17:35, Kevin Hawkins wrote:

...
According to http://wiki.tei-c.org/index.php/OXygen, the tei-oxygen Debian packages provides "automatic updates for new versions of the stylesheet library" (by which, I believe, we mean http://wiki.tei-c.org/index.php/Tei-xsl ). --Kevin

On 9/24/15 11:28 AM, Martin Holmes wrote:

...
Roberto's response is interesting; I've never really understood what the TEI Oxygen package does. Does anyone know? Does it simply provide a customized version of Oxygen that incorporates TEI stuff? If so, presumably it was obsoleted when the plugin was created.

Cheers, Martin

On 15-09-24 09:23 AM, James Cummings wrote:

...
On 24/09/15 17:14, Martin Holmes wrote:

...
Does it fail because it wants a password you don't have, or because your not SR and so you don't have access to his keys? Did you su rahtz?

I had 'su rahtz' before.

...
If we decide to take over building of the packages and move them, there's stuff that has to be done that I don't actually understand. Existing users, who are subscribed to the repo on the Oxford server, will need to remove that repo from their sources and substitute another one. I don't know how (assuming there is a way) to make that requirement known to package users, other than crude things like making the existing repository disappear so that they get errors when they do apt-get update and go off looking for answers. There's some research and learning to do here, so I think we need a little workgroup.

Yes, luckily, the type of person who is subscribed to the teideb repository is likely to be the type of person who won't mind switching the url to a new one. But yes... I think we need a decision on: - should we be maintaining debian packages? - if so, which packages? - where should it be located?

...
Meanwhile, I've asked a simple question on the TEI-L list. If it turns out no-one is using the packages at all, then we might consider abandoning them.

I use them but don't need to.

-James

-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford

Martin Holmes

11 p.m.

New subject: [tei-council] making teideb repository

Please don't do that yet. There are a lot of packages in our current TEI debs, many of which have nothing to do with us (such as rnc). We may elect to continue maintaining only the ones that are our business, to make our life simpler, and to my mind, a package for Oxygen is not really our business. It's a piece of commercial software. Either Syncro should provide a deb, or someone might do it as a personal project, but should it be a TEI project? We certainly have a big role in helping to maintain the TEI framework, but distributing the software itself is a different issue. Cheers, Martin On 15-09-24 09:41 AM, Kevin Hawkins wrote:

...

So the package updates not just the stylesheets but also oXygen itself? If so, I'll update the wiki to make this clear.

On 9/24/15 11:37 AM, James Cummings wrote:

...
The benefit, if the package was maintained, is that those of us using ubuntu or debian never have to think to install a new version of oxygen, it just gets updated, added to menus, etc. It takes out the consciously remembering to update your oxygen install. ;-)

-James

On 24/09/15 17:35, Kevin Hawkins wrote:

...
According to http://wiki.tei-c.org/index.php/OXygen, the tei-oxygen Debian packages provides "automatic updates for new versions of the stylesheet library" (by which, I believe, we mean http://wiki.tei-c.org/index.php/Tei-xsl ). --Kevin

On 9/24/15 11:28 AM, Martin Holmes wrote:

...
Roberto's response is interesting; I've never really understood what the TEI Oxygen package does. Does anyone know? Does it simply provide a customized version of Oxygen that incorporates TEI stuff? If so, presumably it was obsoleted when the plugin was created.

Cheers, Martin

On 15-09-24 09:23 AM, James Cummings wrote:

...
On 24/09/15 17:14, Martin Holmes wrote:

...
Does it fail because it wants a password you don't have, or because your not SR and so you don't have access to his keys? Did you su rahtz?

I had 'su rahtz' before.

...
If we decide to take over building of the packages and move them, there's stuff that has to be done that I don't actually understand. Existing users, who are subscribed to the repo on the Oxford server, will need to remove that repo from their sources and substitute another one. I don't know how (assuming there is a way) to make that requirement known to package users, other than crude things like making the existing repository disappear so that they get errors when they do apt-get update and go off looking for answers. There's some research and learning to do here, so I think we need a little workgroup.

Yes, luckily, the type of person who is subscribed to the teideb repository is likely to be the type of person who won't mind switching the url to a new one. But yes... I think we need a decision on: - should we be maintaining debian packages? - if so, which packages? - where should it be located?

...
Meanwhile, I've asked a simple question on the TEI-L list. If it turns out no-one is using the packages at all, then we might consider abandoning them.

I use them but don't need to.

-James

Martin Holmes

10:51 p.m.

New subject: [tei-council] making teideb repository

I was talking specifically about the oxygen package, which I think was just a deb package of generic Oxygen, done in the absence of any such thing from Syncro. Roberto says he uses it because it lets him keep his Oxygen up to date through apt, but since we don't release it in synchronization with the Syncro guys, it's presumably not much use for that purpose. Personally I'm thinking it's not really our business to maintain debian builds of Oxygen. Cheers, Martin On 15-09-24 09:35 AM, Kevin Hawkins wrote:

...

According to http://wiki.tei-c.org/index.php/OXygen, the tei-oxygen Debian packages provides "automatic updates for new versions of the stylesheet library" (by which, I believe, we mean http://wiki.tei-c.org/index.php/Tei-xsl ). --Kevin

On 9/24/15 11:28 AM, Martin Holmes wrote:

...
Roberto's response is interesting; I've never really understood what the TEI Oxygen package does. Does anyone know? Does it simply provide a customized version of Oxygen that incorporates TEI stuff? If so, presumably it was obsoleted when the plugin was created.

Cheers, Martin

On 15-09-24 09:23 AM, James Cummings wrote:

...
On 24/09/15 17:14, Martin Holmes wrote:

...
Does it fail because it wants a password you don't have, or because your not SR and so you don't have access to his keys? Did you su rahtz?

I had 'su rahtz' before.

...
If we decide to take over building of the packages and move them, there's stuff that has to be done that I don't actually understand. Existing users, who are subscribed to the repo on the Oxford server, will need to remove that repo from their sources and substitute another one. I don't know how (assuming there is a way) to make that requirement known to package users, other than crude things like making the existing repository disappear so that they get errors when they do apt-get update and go off looking for answers. There's some research and learning to do here, so I think we need a little workgroup.

Yes, luckily, the type of person who is subscribed to the teideb repository is likely to be the type of person who won't mind switching the url to a new one. But yes... I think we need a decision on: - should we be maintaining debian packages? - if so, which packages? - where should it be located?

...
Meanwhile, I've asked a simple question on the TEI-L list. If it turns out no-one is using the packages at all, then we might consider abandoning them.

I use them but don't need to.

-James

3339

Age (days ago)

3339

Last active (days ago)

List overview

Download

11 comments

4 participants

participants (4)

James Cummings
Kevin Hawkins
Lou Burnard
Martin Holmes