[ANNOUNCEMENT] djview 4.10.6-2
The following packages have been uploaded to the Cygwin distribution: * djview-4.10.6-2 This package contains the djview4 viewer. This new viewer relies on the DjVulibre library and the Qt4 toolkit. This release disables the browser plugin. -- Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] python-twisted 16.6.0-1
The following packages have been uploaded to the Cygwin distribution: * python2-constantly-15.1.0-1 * python2-incremental-16.10.1-1 * python2-twisted-16.6.0-1 * python3-constantly-15.1.0-1 * python3-incremental-16.10.1-1 * python3-twisted-16.6.0-1 Twisted is a networking engine written in Python, supporting numerous protocols. It contains a web server, numerous chat clients, chat servers, mail servers, and more. This is an update to a newer version required by kajongg, with the addition of some new dependencies. -- Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] ruby-cairo 1.14.6-2
The following packages have been uploaded to the Cygwin distribution: * ruby-cairo-1.14.6-2 * ruby-cairo-devel-1.14.6-2 * ruby-cairo-doc-1.14.6-2 Ruby bindings for the cairo graphics rendering library. This release was rebuilt without the unused cairo-gl bindings. -- Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] cairo 1.14.10-1
The following packages have been uploaded to the Cygwin distribution: * libcairo2-1.14.10-1 * libcairo-devel-1.14.10-1 * libcairo-doc-1.14.10-1 * mingw64-i686-cairo-1.14.10-1 * mingw64-x86_64-cairo-1.14.10-1 Cairo is a 2D graphics library with support for multiple output devices. Currently supported output targets include the X Window System (via both Xlib and XCB), quartz, win32, and image buffers, as well as PDF, PostScript, and SVG file output. This is an update to the latest upstream stable release: https://www.cairographics.org/news/cairo-1.14.10/ The unused and unmaintained cairo-gl backend has been disabled in this release. -- Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] KDE Applications 17.04.3
The following packages have been uploaded to the Cygwin distribution: * ark-17.04.3-1 * artikulate-17.04.3-1 * blinken-17.04.3-1 * bomber-17.04.3-1 * bovo-17.04.3-1 * cervisia-17.04.3-1 * dolphin-17.04.3-1 * dolphin5-part-17.04.3-1 * dolphin-devel-17.04.3-1 * dolphin-plugins-17.04.3-1 * dragon-17.04.3-1 * filelight-17.04.3-1 * granatier-17.04.3-1 * gwenview-17.04.3-1 * jovie-17.04.3-1 * juk-17.04.3-1 * kaccessible-17.04.3-1 * kajongg-17.04.3-1 * kalgebra-17.04.3-1 * kalzium-17.04.3-1 * kanagram-17.04.3-1 * kapman-17.04.3-1 * kapptemplate-17.04.3-1 * kate-17.04.3-1 * katomic-17.04.3-1 * kblackbox-17.04.3-1 * kblocks-17.04.3-1 * kbounce-17.04.3-1 * kbrickbuster-16.12.3-1 * kbruch-17.04.3-1 * kcalc-17.04.3-1 * kcharselect-17.04.3-1 * kcolorchooser-17.04.3-1 * kcron-17.04.3-1 * kdebugsettings-17.04.3-1 * kde-dev-scripts-17.04.3-1 * kde-dev-utils-17.04.3-1 * kdeedu-data-17.04.3-1 * kdegraphics-mobipocket-17.04.3-1 * kdegraphics-thumbnailers-17.04.3-1 * kde-l10n-ar-17.04.3-1 * kde-l10n-ast-17.04.3-1 * kde-l10n-bg-17.04.3-1 * kde-l10n-bs-17.04.3-1 * kde-l10n-ca-17.04.3-1 * kde-l10n-ca-valencia-17.04.3-1 * kde-l10n-cs-17.04.3-1 * kde-l10n-da-17.04.3-1 * kde-l10n-de-17.04.3-1 * kde-l10n-el-17.04.3-1 * kde-l10n-en_GB-17.04.3-1 * kde-l10n-eo-17.04.3-1 * kde-l10n-es-17.04.3-1 * kde-l10n-et-17.04.3-1 * kde-l10n-eu-17.04.3-1 * kde-l10n-fa-17.04.3-1 * kde-l10n-fi-17.04.3-1 * kde-l10n-fr-17.04.3-1 * kde-l10n-ga-17.04.3-1 * kde-l10n-gl-17.04.3-1 * kde-l10n-he-17.04.3-1 * kde-l10n-hi-17.04.3-1 * kde-l10n-hr-17.04.3-1 * kde-l10n-hu-17.04.3-1 * kde-l10n-ia-17.04.3-1 * kde-l10n-id-17.04.3-1 * kde-l10n-is-17.04.3-1 * kde-l10n-it-17.04.3-1 * kde-l10n-ja-17.04.3-1 * kde-l10n-kk-17.04.3-1 * kde-l10n-km-17.04.3-1 * kde-l10n-ko-17.04.3-1 * kde-l10n-lt-17.04.3-1 * kde-l10n-lv-17.04.3-1 * kde-l10n-mr-17.04.3-1 * kde-l10n-nb-17.04.3-1 * kde-l10n-nds-17.04.3-1 * kde-l10n-nl-17.04.3-1 * kde-l10n-nn-17.04.3-1 * kde-l10n-pa-17.04.3-1 * kde-l10n-pl-17.04.3-1 * kde-l10n-pt-17.04.3-1 * kde-l10n-pt_BR-17.04.3-1 * kde-l10n-ro-17.04.3-1 * kde-l10n-ru-17.04.3-1 * kde-l10n-sk-17.04.3-1 * kde-l10n-sl-17.04.3-1 * kde-l10n-sr-17.04.3-1 * kde-l10n-sv-17.04.3-1 * kde-l10n-tr-17.04.3-1 * kde-l10n-ug-17.04.3-1 * kde-l10n-uk-17.04.3-1 * kde-l10n-wa-17.04.3-1 * kde-l10n-zh_CN-17.04.3-1 * kde-l10n-zh_TW-17.04.3-1 * kde-runtime-17.04.3-1 * kdesdk-kioslaves-17.04.3-1 * kdesdk-thumbnailers-17.04.3-1 * kdf-17.04.3-1 * kdialog-17.04.3-1 * kdiamond-17.04.3-1 * keditbookmarks-17.04.3-1 * kf5-kio-extras-17.04.3-1 * kf5-kross-python-17.04.3-1 * kf5-kross-ruby-17.04.3-1 * kfilereplace-17.04.3-1 * kfind-17.04.3-1 * kfourinline-17.04.3-1 * kgeography-17.04.3-1 * kget-17.04.3-1 * kgoldrunner-17.04.3-1 * khangman-17.04.3-1 * khelpcenter-17.04.3-1 * kig-17.04.3-1 * kigo-17.04.3-1 * killbots-17.04.3-1 * kimagemapeditor-17.04.3-1 * kiriki-17.04.3-1 * kiten-17.04.3-1 * kjumpingcube-17.04.3-1 * klettres-17.04.3-1 * klickety-17.04.3-1 * klines-17.04.3-1 * klinkstatus-17.04.3-1 * kmag-17.04.3-1 * kmahjongg-17.04.3-1 * kmines-17.04.3-1 * kmix-17.04.3-1 * kmousetool-17.04.3-1 * kmouth-17.04.3-1 * kmplot-17.04.3-1 * knavalbattle-17.04.3-1 * knetwalk-17.04.3-1 * kolf-17.04.3-1 * kollision-17.04.3-1 * kolourpaint-17.04.3-1 * kompare-17.04.3-1 * konqueror-17.04.3-1 * konquest-17.04.3-1 * konsole-17.04.3-1 * konsole5-part-17.04.3-1 * kpartloader-17.04.3-1 * kpat-17.04.3-1 * kprofilemethod-17.04.3-1 * kqtquickcharts-17.04.3-1 * kqtquickcharts-devel-17.04.3-1 * krdc-17.04.3-1 * kreversi-17.04.3-1 * krfb-17.04.3-1 * kruler-17.04.3-1 * kshisen-17.04.3-1 * ksirk-17.04.3-1 * ksnakeduel-17.04.3-1 * ksnapshot-17.04.3-1 * kspaceduel-17.04.3-1 * ksquares-17.04.3-1 * kstars-17.04.3-1 * kstartperf-17.04.3-1 * ksudoku-17.04.3-1 * ksystemlog-17.04.3-1 * kteatime-17.04.3-1 * ktimer-17.04.3-1 * ktouch-17.04.3-1 * ktron-17.04.3-1 * ktuberling-17.04.3-1 * kturtle-17.04.3-1 * kubrick-17.04.3-1 * kuiviewer-17.04.3-1 * kwalletmanager5-17.04.3-1 * kwalletmanager-common-17.04.3-1 * kwebkitpart-1.3.5-0.1.20170506git * kwordquiz-17.04.3-1 * kwrite-17.04.3-1 * libanalitza8-17.04.3-1 * libanalitza-common-17.04.3-1 * libanalitza-devel-17.04.3-1 * libastro1-17.04.3-1 * libastro-devel-17.04.3-1 * libkasten3_3-17.04.3-1 * libkasten3-devel-17.04.3-1 * libkcddb4-16.08.3-1 * libkcddb-common-16.08.3-1 * libkcddb-devel-16.08.3-1 * libkdecore5-4.14.34-1 * libkdecore-devel-4.14.34-1 * libKEduVocDocument5-17.04.3-1 * libKEduVocDocument-devel-17.04.3-1 * libKF5BalooWidgets5-17.04.3-1 * libKF5BalooWidgets-devel-17.04.3-1 * libKF5Blog5-17.04.3-1 * libKF5Blog-devel-17.04.3-1 * libKF5CalendarCore5-17.04.3-1 * libKF5CalendarCore-devel-17.04.3-1 * libKF5CalendarUtils5-17.04.3-1 * libKF5CalendarUtils-devel-17.04.3-1 * libKF5Cddb5-17.04.3-1 * libKF5Cddb-devel-17.04.3-1 * libKF5Contacts5-17.04.3-1 * libKF5Contacts-devel-17.04.3-1 * libKF5GrantleeTheme5-17.04.3-1 * libKF5GrantleeTheme-devel-17.04.3-1 * libKF5Holidays5-17.04.3-1 * libKF5Holidays-devel-17.04.3-1 * libKF5I18n5-5.35.0-2 * libKF5I18n-devel-5.35.0-2 * libKF5IdentityManage
NTFS inode ouput from ls -i
I just had to deal with the output from chkdsk on my Windows 7 pro that lists MFT record numbers just like ifind and icat do in the Sleuth Kit as summarized in: https://cygwin.com/ml/cygwin/2012-11/msg00172.html The chkdsk MFT record numbers are exactly what ifind and icat display/use. I also discovered when doing "ls -i" on NTFS file systems mounted on my Ubuntu 16.04 linux system that the "ls -i" numbers reported are the same as the chkdsk, ifind, and icat record numbers. These are all the lower 32 bits of the 64 bit numbers reported by "ls -i" with the current cygwin. Had the cygwin "find -inum" and "ls -i" used these 32 bit numbers, my task would have been easier. From the above link, Corinna found it odd that ifind and icat would use the 32 bit numbers. I would have preferred them when dealing with chkdsk issues. What's the current thinking about this? Harry -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: How to repeat a bash shell script until success
On July 14, 2017 9:06:02 AM EDT, cyg Simple <> wrote: >On 7/14/2017 1:27 AM, Gary Johnson wrote: >> On 2017-07-12, Bryan Dunphy wrote: >>> I have a shell script, originally created for Mac OS X. that waits >>> for an external drive to be mounted (by . >> > >In reality the OP script appears to be executed in a crontab system and >executed every X minutes. So a change to the OP question is needed >which is answered at[1]. Let's remember some people have no real clue >as to what question they should ask and we need to interpret what is >being asked into what should have been asked. If interpretation isn't >possible then asking for a use case would be warranted. > >[1] >https://stackoverflow.com/questions/707184/how-do-you-run-a-crontab-in-cygwin-on-windows cyg Simple, Thanks much for this. It seems the link is misleading, because it says cygrunsrv and cron-config must be used to get Cron to work. I've been frustrated without admin, being unable to use these. It turns out simply adding /usr/sbin/cron to .bashrc will make Cron available. Or, slightly more complicated, to avoid "lock" errors: $HOME/bin/startcron Containing: #!/bin/bash if P=$(pgrep cron) then echo "already running, PID is $P" else echo "not running, starting now" /usr/sbin/cron fi Thanks! -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: How to repeat a bash shell script until success
On 7/15/2017 2:56 AM, Sorin Adrian Savu wrote: > On Fri, Jul 14, 2017 at 4:06 PM, cyg Simple wrote: >> >> On 7/14/2017 1:27 AM, Gary Johnson wrote: >>> On 2017-07-12, Bryan Dunphy wrote: I have a shell script, originally created for Mac OS X. that waits for an external drive to be mounted (by testing an “ls” of the volume’s root directory for success) then runs an “rsync” command. How do I get the script to be run repeatedly until successful exit under Cygwin? Here is the unmodified Mac OS version of the script: #!/bin/bash if ls /Volumes/Shared >/dev/null 2>/dev/null then rsync -avz --compress-level=9 --delete-during --partial --exclude 'cache/' aleph.gutenberg.org::gutenberg /Volumes/Shared/Project-Gutenberg exit 0 else exit 1 fi >>> >>> Let the name of your script be "myscript". The following will run >>> myscript every two seconds until it succeeds. >>> >>> while ! myscript; do sleep 2; done >>> >>> This is really a bash programming question and is not specific to >>> Cygwin. >>> >> >> In reality the OP script appears to be executed in a crontab system and >> executed every X minutes. So a change to the OP question is needed >> which is answered at[1]. Let's remember some people have no real clue >> as to what question they should ask and we need to interpret what is >> being asked into what should have been asked. If interpretation isn't >> possible then asking for a use case would be warranted. >> >> [1] >> https://stackoverflow.com/questions/707184/how-do-you-run-a-crontab-in-cygwin-on-windows > > > Actually, the correct question would be: how do I run a bash script > when a USB stick is mounted ? > > Which is doable via Task Scheduler and a event log trigger. See > https://answers.microsoft.com/en-us/windows/forum/windows_vista-windows_programs/task-scheduler-how-to-automatically-synchronize-my/45a49d83-b1d8-4d37-8896-3d2696cf9795 > on how to locate the appropriate event, > > As for the script: > > - don't use ls for checking file/directory presence use -f/-d (man test) > - you will need to adjust paths (cygwin has windows drives under > /cygdrive (cygpath -h) > And don't forget the user has the option to change /cygdrive to something else including / which is my preference. > On how to run the script from Task Scheduler use an action like this: > > C:\Tools\cygwin64\bin\bash.exe -c /cygdrive/c/tools/cygwin64/home/bryan/bkp.sh > (adjust your paths accordingly ) Yes, if you don't want to run cygserver, this is another option. But if you're moving from a *nix based system then using cron under cygserver is what you want. -- cyg Simple -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: gpg ca-cert-file=[which file???]
On 7/16/17, René Berber wrote: > On 7/16/2017 11:38 AM, Lee wrote: > > [snip] >> ok... man update-ca-trust >> FILES >> /etc/pki/tls/certs/ca-bundle.trust.crt >> Classic filename, file contains a list of CA certificates in >> the extended BEGIN/END TRUSTED CERTIFICATE file format, >> which includes trust (and/or distrust) flags specific to >> certificate usage. This file is a symbolic link that refers >> to the consolidated output created by the update-ca-trust >> command. > [snip] >> It looks like there's some certs in >> /etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt that I don't >> want to trust.. but how to tell which ones & how to set >> distrust/blacklist trust flags on them? or maybe I need to copy them >> to /etc/pki/ca-trust/source/blacklist/ ??? >> >> Anyone have any pointers on how to distrust certs in >> ca-bundle.trust.crt (assuming that _is_ the file I should be using) or >> even how to show exactly what's in there? >> $ grep "#" ca-bundle.trust.crt >> shows lots of comments but >> $ openssl x509 -in ca-bundle.trust.crt -noout -subject -dates >> just shows me the first cert :( > > You should refer to the package announcement, and direct any questions > about the package (not about its use) to its maintainer. I came across this when looking for the ca-certificates package announcement: https://cygwin.com/ml/cygwin/2013-05/msg00385.html it's from 2013: It has been brought to my attention that gnutls does not seem to be configured to use ca-certificates by default. This can be enabled by adding --with-default-trust-store-file=/usr/ssl/certs/ca-bundle.crt to configure flags I'm still not clear about which trust store I should be using - ca-bundle.crt or ca-bundle.trust.crt > As I understand the package is just a bundle of the files distributed by > Mozilla (which is the maintainer of the root certs). For questions > about those files, its contents, or its use... refer to Mozilla. As far as I can tell, Mozilla thinks using their trust store for anything other than firefox is out of scope - eg: https://groups.google.com/forum/#!topic/mozilla.dev.security.policy/NHW4JA6xoAY mozilla.dev.security.policy › Configuring Graduated Trust for Non-Browser Consumption > Actually Mozilla distributes one file, which is then processed to create > all the files that you see. > > The link you show to Mozilla about the trust on CNNIC also points out > that the exception is made in code (i.e. hard-coded), and if you look > above it clearly states: "The status of whether a root is approved to > issue EV certificates or not is stored in PSM rather than certdata.txt", > this certdata.txt is precisely the file I'm talking about above, so > don't expect any of those Extended Validation changes to be present (and > you can ask Mozilla why they do it in code, instead of in the certs). I don't care about EV right now. I don't want to trust any certificate issued by CNNIC & a few other CAs. How do I do that? Thanks Lee -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: rebase segmentation fault
On Jul 17 10:35, Corinna Vinschen wrote: > On Jul 16 19:16, Denis Excoffier wrote: > > Hello, > > > > I have a Cygwin installation under Windows 7 (32 bits). > > > > After 'rebase-trigger full' and 'Setup', autorebase seems to finish > > okay, but the /etc/rebase.db.i386 remains absent after that. Not a > > real problem after all (since rebase was functioning well until some > > recent date and all is already rebased), but some third party builds > > (like e.g. perl) insist on the presence of the /etc/rebase.db.i386 > > database. > > > > Indeed, rebase segfaults in rebase.c and nothing is rebased. This > > occurs (see rebase-4.4.2) immediately after "Skip trailing entries as > > long as there is no hole." because at some point, all > > img_info_list[end].base are equal to 0, the while() is getting always > > true, and the variable 'end' is decremented by 1 at every iteration, > > until it reaches -1 where the segfault occurs. > > Patches welcome! Never mind: https://sourceware.org/git/?p=cygwin-apps/rebase.git;a=commitdiff;h=a7d415a Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat signature.asc Description: PGP signature
Re: rebase segmentation fault
On Jul 16 19:16, Denis Excoffier wrote: > Hello, > > I have a Cygwin installation under Windows 7 (32 bits). > > After 'rebase-trigger full' and 'Setup', autorebase seems to finish > okay, but the /etc/rebase.db.i386 remains absent after that. Not a > real problem after all (since rebase was functioning well until some > recent date and all is already rebased), but some third party builds > (like e.g. perl) insist on the presence of the /etc/rebase.db.i386 > database. > > Indeed, rebase segfaults in rebase.c and nothing is rebased. This > occurs (see rebase-4.4.2) immediately after "Skip trailing entries as > long as there is no hole." because at some point, all > img_info_list[end].base are equal to 0, the while() is getting always > true, and the variable 'end' is decremented by 1 at every iteration, > until it reaches -1 where the segfault occurs. Patches welcome! Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat signature.asc Description: PGP signature
