Re: SSH key for upload access

[Jon Turney]

On 18/04/2017 16:23, Adam Dinwoodie wrote:

On 18 April 2017 at 16:21, Adam Dinwoodie wrote:

Name: Adam Dinwoodie
Package: git


Replying so the original email is still in the correct format: I'm
sending in a new key because I've managed to lose the password for my
previous upload SSH key.


Done.

[ITP] libftdi1 & libconfuse

[Åke Rehnman]

Hello all,

One more effort to try getting some attention towards libftdi and 
libconfuse packages...


Both libftdi and libconfuse are available in ubuntu and debian + others. 
Libftdi is used with openocd among others. Libconfuse is used by eeprom 
programmer for libftdi.


libftdi1 is released under LGPL 2.1 and eeprom programmer under GPL 2. 
See https://www.intra2net.com/en/developer/libftdi/index.php


libconfuse is released under ISC License. See 
https://github.com/martinh/libconfuse/blob/master/LICENSE


Regards

/Ake

Libftdi1:

category: Libs
requires: bash cygwin libconfuse1 libgcc1 libstdc++6 libusb1.0 libconfuse1
sdesc: "Library to control and program the FTDI USB controller"
ldesc: "libFTDI is an open source library to talk to FTDI chips: FT232BM, FT245BM, 
FT2232C, FT2232D, FT245R, FT232H and FT230X including the popular bitbang mode. The 
library is linked with your program in userspace, no kernel driver required. libFTDI 
works perfectly with Linux, Windows, MacOS X and BSD variants thanks to libusb."


Libconfuse:

category: Libs
requires: cygwin libintl8
sdesc: "Library for parsing configuration files"
ldesc: "libConfuse is a configuration file parser library, licensed under the terms 
of the ISC license, and written in C."


Files available here: https://stm8-binutils-gdb.sourceforge.io/cygwin/

Re: SSH key for upload access

[Adam Dinwoodie]

On 18 April 2017 at 16:21, Adam Dinwoodie wrote:
> Name: Adam Dinwoodie
> Package: git

Replying so the original email is still in the correct format: I'm
sending in a new key because I've managed to lose the password for my
previous upload SSH key.

SSH key for upload access

[Adam Dinwoodie]

Name: Adam Dinwoodie
Package: git
 BEGIN SSH2 PUBLIC KEY 
B3NzaC1yc2EDAQABAAACAQC6Q+n5YorDTYF9bag+N80WCSatVBTjG5Ia4s3dhk
F3SQk2U+RJZmmLhQU8cwWqw6r7OpBJIhtzxHYkUQ4qsiXVh8tSUE6SQ6eqor1k2UnKLS4p
g2OVLkCQU3sdqr6v6NdlwvDiH22tO4Xf9S5uh9yQJ9RGkQrpxkV8BZyaiz08hakfYYNn62
xl2vzeKc7EXDAH9GAI7M/LW2oHws9IAMuM/INqtU7bSqVEuQrw18WK9qT61FjP8+9hQFIK
Zy84yA1fNxRjx0MobVGCK4VpCHPaJC8sUzMaQ/UqZ++tGKANluL5FQUiAWv0jAd+MgDugm
8tmwCnZsVv6PfgjUzGLkokTG4uGElabl+sk0RAec0oN/lD50DgMInmL8xsq8mzw1diGtIC
otkl8y0y4x7FQ1fNTBgwyj3PRdg5lwiFZ98xSdKgY0V4RS/vwepSEWOOwTgPcW4dMu
Th+0xc2nyMkhAV5LGbSRxpnhQjL3GiSd/2HBa+055d+g2D7XOrPUCW93QbpyDoA6Go/IDq
r9oKEyJMizjVn/BPz08oV+xnlFGyiyreS9qwfYezloecFqGMAaF9v38pdDQfs5OuU8XQBX
FPjYYYXYkTtA+F9Aewj9FTYNyTjDudQdF7T7bZktoF/+D3YaVcr94P4UzezZjUDodMqu0L
OOWU2Y4fBRQhhw==
 END SSH2 PUBLIC KEY 

Re: [ITP] DocBook 5 + tools -- Next Steps?

[Holger Bast]

Hi there,
Are the packages docbook5 and daps ok and will they be included in the cygwin 
portage?

What are the next steps for me?

Thx + Bye,
Holger

> Gesendet: Freitag, 07. April 2017 um 12:13 Uhr
> Von: "Holger Bast" 
> An: cygwin-apps@cygwin.com
> Cc: "Jon Turney" 
> Betreff: Re: [ITP] DocBook 5 + tools
>
> Ok, I updated the files and uploaded them on the server.
> 1) License added
> 2) doc und xml files are now separated
> 
> 
> 
> category: Text
> requires: perl 
> sdesc: "DocBook XML 5.0 distribution"
> ldesc: "DocBook is a schema (available in several languages including RELAX 
> NG, SGML and XML DTDs, and W3C XML Schema)
> maintained by the DocBook Technical Committee of OASIS. It is particularly 
> well suited to books and papers about
> computer hardware and software (though it is by no means limited to these 
> applications)."
> 
> http://packages.ubuntu.com/search?keywords=docbook5-xml
> 
> Packages:
> https://virtualheadcrash.net/cygwin/x86/docbook-5.0/docbook-5-5.0-1.hint
> https://virtualheadcrash.net/cygwin/x86/docbook-5.0/docbook-5-5.0-1.tar.xz
> https://virtualheadcrash.net/cygwin/x86/docbook-5.0/docbook-5-5.0-1-src.tar.xz
> 
> 
> 
> 
> > Gesendet: Mittwoch, 05. April 2017 um 19:05 Uhr
> > Von: "Jon Turney" 
> > An: cygwin-apps@cygwin.com
> > Cc: "Holger Bast" 
> > Betreff: Re: [ITP] DocBook 5 + tools
> >
> > On 30/03/2017 16:39, Holger Bast wrote:
> > > Hi there,
> > > I'm interested in maintaining DocBook 5 schemata plus some additional 
> > > tools for docbook (daps and jing-trang). I've never maintained a package 
> > > before, so I think the best way for me would be starting with DocBook 5. 
> > > By creating the cygport file I run into some questions that I would like 
> > > to address:
> > 
> > Thanks for doing this.
> > 
> > For the avoidance of doubt, what license applies to this?
> > 
> > > 1) docbook-5.0 installation path
> > > All docbook-4.x files are installed in 
> > > /usr/share/xml/docbook/ and so on. With DocBook 5 the 
> > > distribution format changed and there is now one folder with all 
> > > necessary information:
> > >
> > [...]
> > >
> > > I propose to put the hole distribution under
> > >
> > > /usr/share/xml/docbook/docbook-5.0/
> > >
> > > so everything is in one place. I also had a look at Ubuntu; they put the 
> > > schema-folders (dtd, rng, schematron (renamed sch), xsd and 
> > > catalog-docbook5.xml) under
> > >
> > > /usr/share/xml/docbook/schema
> > >
> > > and all documentation in their doc-structure. In my opinion, putting 
> > > everything at one place would be the easiest way to work with.
> > 
> > I think the documentation should be under /usr/share/doc, both to 
> > conform with our packaging guidelines (such as they are), and for 
> > discoverability (people may know to look in /usr/share/doc for 
> > documentation)
> > 
> > 
> 

Re: calm now runs on-demand

[Corinna Vinschen]

On Apr 17 12:34, Jon Turney wrote:
> 
> I recently deployed an update to calm which should causes it to run
> on-demand after a maintainer SFTP upload.
> 
> Hopefully this reduces the inconvenience of having to wait till the next
> scheduled run, after an upload is made which fails due to some easily
> correctable problem.
> 
> calm continues to also run on a schedule at :10 and :40 past the hour, so it
> will still note changes which have been made directly on sourceware.
> 
> If you have shell access on sourceware, and make such changes, you can force
> calm to run with '~cygwin-admin/bin/calm scan-(uploads|relarea)'.
> 
> Given that, it probably makes sense to consider reducing the frequency of
> scheduled runs.




Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat


signature.asc
Description: PGP signature