libgnutls-devel depends on missnig libtasn1.la file
Hi, I am attempting to build softare (GNU libmicrohttpd) with cygport on x86, but am getting errors when it links against libgnutls: /usr/bin/sed: can't read /usr/lib/libtasn1.la: No such file or directory libtool: error: '/usr/lib/libtasn1.la' is not a valid libtool archive Likely cause: Cygwin gnutls-devel 3.2.21-1 installs /usr/lib/libgnutls.la and this file references libtasn1.la However /usr/lib/libtasn1.la has been removed as of libtans1-devel 0.49-1. See announce message here: https://cygwin.com/ml/cygwin-announce/2016-08/msg00084.html . Could the maintainers of libgnutls-devel and libtasn1 please resolve this! Here is my libmicrohttpd.cygport file should you need to reproduce the problem: http://pastebin.com/raw/HTwzpbXb -- Peter (A907 E02F A6E5 0CD2 34CD 20D2 6760 79C5 AC40 DD6B) signature.asc Description: PGP signature
Updated: bash-4.3.48-8
A new release of bash, 4.3.48-8, has been uploaded and will soon reach a
mirror near you. It leave 4.3.46-7 as the previous version.
NEWS:
=
This is a minor build that incorporates two official upstream patches,
while I work on the larger project of building bash 4.4 for Cygwin.
This build of bash is immune to the ShellShock vulnerabilities (although
unpatched bash 4.3 is vulnerable, the official upstream patches solve
the issue). By now, you should no longer be running a vulnerable bash,
but to double check you can run the following test to make sure you are
not subject to arbitrary remote code execution due to ShellShock:
$ env 'bad=() { echo vulnerable; }' bash -c bad
If it prints "bash: bad: command not found", your version of bash is
safe and not subject to remote exploits. If it prints "vulnerable", you
need to upgrade now.
There are a few things you should be aware of before using this version:
1. When using binary mounts, cygwin programs try to emulate Linux. Bash
on Linux does not understand \r\n line endings, but interprets the \r
literally, which leads to syntax errors or odd variable assignments.
Therefore, you will get the same behavior on Cygwin binary mounts by
default.
2. d2u is your friend. You can use it to convert any problematic script
into binary line endings.
3. Cygwin text mounts automatically work with either line ending style,
because the \r is stripped before bash reads the file. If you
absolutely must use files with \r\n line endings, consider mounting the
directory where those files live as a text mount. However, text mounts
are not as well tested or supported on the cygwin mailing list, so you
may encounter other problems with other cygwin tools in those directories.
4. This version of bash has a cygwin-specific set option, named "igncr",
to force bash to ignore \r, independently of cygwin's mount style. As
of bash-3.2.3-5, it controls regular scripts, command substitution, and
sourced files; bash-4.3.43-5 adds the read builtin to the list. I hope
to convince the upstream bash maintainer to accept this patch into a
future bash release even on Linux, rather than keeping it a
cygwin-specific patch, but only time will tell. There are several ways
to activate this option:
4a. For a single affected script, add this line just after the she-bang:
(set -o igncr) 2>/dev/null && set -o igncr; # comment is needed
4b. For a single script, invoke bash explicitly with the option, as in
'bash -o igncr ./myscript' rather than the simpler './myscript'.
4c. To affect all scripts, export the environment variable BASH_ENV,
pointing to a file that sets the shell option as desired. Bash will
source this file on startup for every script.
4d. Added in the bash-3.2-2 release: export the environment variable
SHELLOPTS with igncr included in it. It is read-only from within bash,
but you can set it before invoking bash; once in bash, it auto-tracks
the current state of 'set -o igncr'. If exported, then all bash child
processes inherit the same option settings; with the exception added in
3.2.9-11 that certain interactive options are not inherited in
non-interactive use.
4e. bash-4.1.9-1 dropped support for 'shopt -s igncr'; it did not make
sense to support the option through both set and shopt, and SHELLOPTS
proved to be more powerful.
5. You can also experiment with the IFS variable for controlling how
bash will treat \r during variable expansion.
6. There are varying levels of speed at which bash operates. The
fastest is on a binary mount with igncr disabled (the default behavior).
Next would be text mounts with igncr disabled and no \r in the
underlying file. Next would be binary mounts with igncr enabled. And
the slowest that bash will operate is on text mounts with igncr enabled.
7. As additional cygwin extensions, this version of bash includes:
7a. EXECIGNORE - a colon-separated list of glob patterns to ignore
when completing on executables. EXECIGNORE=*.dll is common.
7b. completion_strip_exe - using 'shopt -s completion_strip_exe'
makes completion strip .exe suffixes
8. This version of bash is immune to ShellShock (CVE-2014-6271 and
friends) because it exports functions via 'BASH_FUNC_foo%%=' rather than
'foo=' environment variables. However, doing this has exposed
weaknesses in some other utilities like 'ksh' or 'at' that fail to scrub
their environment to exclude what is not a valid name for them.
9. If you don't like how bash behaves, then propose a patch, rather than
proposing idle ideas. This turn of events has already been talked to
death on the mailing lists by people with many ideas, but few patches.
Thanks to Dan Colascione for providing the EXECIGNORE and
completion_strip_exe patches.
Remember, you must not have any bash or /bin/sh instances running when
you upgrade the bash package. This release requires cygwin-2.6.0-1 or
later. See also the upstream documentation in /usr/share/doc/bash/.
DESCRIPTION:
Bash is an sh-compatible shell that
[ANNOUNCEMENT] Updated: bash-4.3.48-8
A new release of bash, 4.3.48-8, has been uploaded and will soon reach a
mirror near you. It leave 4.3.46-7 as the previous version.
NEWS:
=
This is a minor build that incorporates two official upstream patches,
while I work on the larger project of building bash 4.4 for Cygwin.
This build of bash is immune to the ShellShock vulnerabilities (although
unpatched bash 4.3 is vulnerable, the official upstream patches solve
the issue). By now, you should no longer be running a vulnerable bash,
but to double check you can run the following test to make sure you are
not subject to arbitrary remote code execution due to ShellShock:
$ env 'bad=() { echo vulnerable; }' bash -c bad
If it prints "bash: bad: command not found", your version of bash is
safe and not subject to remote exploits. If it prints "vulnerable", you
need to upgrade now.
There are a few things you should be aware of before using this version:
1. When using binary mounts, cygwin programs try to emulate Linux. Bash
on Linux does not understand \r\n line endings, but interprets the \r
literally, which leads to syntax errors or odd variable assignments.
Therefore, you will get the same behavior on Cygwin binary mounts by
default.
2. d2u is your friend. You can use it to convert any problematic script
into binary line endings.
3. Cygwin text mounts automatically work with either line ending style,
because the \r is stripped before bash reads the file. If you
absolutely must use files with \r\n line endings, consider mounting the
directory where those files live as a text mount. However, text mounts
are not as well tested or supported on the cygwin mailing list, so you
may encounter other problems with other cygwin tools in those directories.
4. This version of bash has a cygwin-specific set option, named "igncr",
to force bash to ignore \r, independently of cygwin's mount style. As
of bash-3.2.3-5, it controls regular scripts, command substitution, and
sourced files; bash-4.3.43-5 adds the read builtin to the list. I hope
to convince the upstream bash maintainer to accept this patch into a
future bash release even on Linux, rather than keeping it a
cygwin-specific patch, but only time will tell. There are several ways
to activate this option:
4a. For a single affected script, add this line just after the she-bang:
(set -o igncr) 2>/dev/null && set -o igncr; # comment is needed
4b. For a single script, invoke bash explicitly with the option, as in
'bash -o igncr ./myscript' rather than the simpler './myscript'.
4c. To affect all scripts, export the environment variable BASH_ENV,
pointing to a file that sets the shell option as desired. Bash will
source this file on startup for every script.
4d. Added in the bash-3.2-2 release: export the environment variable
SHELLOPTS with igncr included in it. It is read-only from within bash,
but you can set it before invoking bash; once in bash, it auto-tracks
the current state of 'set -o igncr'. If exported, then all bash child
processes inherit the same option settings; with the exception added in
3.2.9-11 that certain interactive options are not inherited in
non-interactive use.
4e. bash-4.1.9-1 dropped support for 'shopt -s igncr'; it did not make
sense to support the option through both set and shopt, and SHELLOPTS
proved to be more powerful.
5. You can also experiment with the IFS variable for controlling how
bash will treat \r during variable expansion.
6. There are varying levels of speed at which bash operates. The
fastest is on a binary mount with igncr disabled (the default behavior).
Next would be text mounts with igncr disabled and no \r in the
underlying file. Next would be binary mounts with igncr enabled. And
the slowest that bash will operate is on text mounts with igncr enabled.
7. As additional cygwin extensions, this version of bash includes:
7a. EXECIGNORE - a colon-separated list of glob patterns to ignore
when completing on executables. EXECIGNORE=*.dll is common.
7b. completion_strip_exe - using 'shopt -s completion_strip_exe'
makes completion strip .exe suffixes
8. This version of bash is immune to ShellShock (CVE-2014-6271 and
friends) because it exports functions via 'BASH_FUNC_foo%%=' rather than
'foo=' environment variables. However, doing this has exposed
weaknesses in some other utilities like 'ksh' or 'at' that fail to scrub
their environment to exclude what is not a valid name for them.
9. If you don't like how bash behaves, then propose a patch, rather than
proposing idle ideas. This turn of events has already been talked to
death on the mailing lists by people with many ideas, but few patches.
Thanks to Dan Colascione for providing the EXECIGNORE and
completion_strip_exe patches.
Remember, you must not have any bash or /bin/sh instances running when
you upgrade the bash package. This release requires cygwin-2.6.0-1 or
later. See also the upstream documentation in /usr/share/doc/bash/.
DESCRIPTION:
Bash is an sh-compatible shell that
Re: Installer names not meaningful enough
On 7.12.2016 23:06, Erik Soderquist wrote: On Wed, Dec 7, 2016 at 4:57 PM, Brian Inglis wrote: Use wget -N to prevent duplicate downloads when the name, date, and size don't change. That only works if I am downloading to the same location/name as the source is -- Erik Erik (and others), don't worry about Setup version, please. Use this script: https://gist.github.com/Vlado-99/1d59bf05b70481377ff90bb53e13bb2d it makes things much easier: - Setup is downloaded only if gpg signature changes (only very small .sig file is re-downloaded every time) - gpg signature of Setup is validated (no need to do it manually) - services I use, are stopped and restarted automatically (no need to restart Windows after update; add Yours services to script if needed) Vlado -- 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: per-version hints proposal
On Dec 9 11:46, Corinna Vinschen wrote:
> I don't think this is feasible. The maintainer should have control
> over the promotion from test to curr. I'm not affected by this since
> I generate new versions as soon as I promote, so this is more maintainers
> like JonY, for whom a rebuild and reupload of the gcc packages just to
> promote test to curr is quite a burden.
>
> First, not well thought out proposal:
>
> - cygport gets a new command, e. g.
>
> cygport foo.cygport {promote|untest|currify}
>
> This command has only one purpose. It uploads a file !untest
> to the maintainers upload area, with a single line containing
> the version number from the foo.cygport file, i. e.
>
> - Fetch $PVR from foo.cygport, e. g. 2.24-1.
> - echo "$PVR" > !untest
> - lftp !untest to cygwin.com:maintainer-area
>
> - While creating the ini file, calm looks for !untest files. If one
> is available, check the version number. If there's a matching PVR.hints
> file, drop the test marker. Continue with creating the ini file.
Even simpler:
- cygport gets a new command, e. g.
cygport foo.cygport {promote|untest|currify}
This command has only one purpose. It creates and uploades new
$PVR.hint files without the test: marker to the maintainers upload
area.
Shouldn't these files be picked up by calm and overwrite the existing
PVR.hint files and the test marker is gone?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
signature.asc
Description: PGP signature
[ANNOUNCEMENT] libnice 0.1.13-1
The following packages have been uploaded to the Cygwin distribution: * libnice10-0.1.13-1 * libnice-devel-0.1.13-1 * libnice-doc-0.1.13-1 * girepository-Nice0.1-0.1.13-1 * gstreamer1.0-plugins-nice-0.1.13-1 Libnice is an implementation of the IETF's draft Interactive Connectivity Establishment standard (ICE). It provides GLib-based library, libnice and GStreamer elements. ICE is useful for applications that want to establish peer-to-peer UDP data streams. It automates the process of traversing NATs and provides security against some attacks. This is an update to the latest upstream release. The GStreamer 0.10 elements have been dropped 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
libnice 0.1.13-1
The following packages have been uploaded to the Cygwin distribution: * libnice10-0.1.13-1 * libnice-devel-0.1.13-1 * libnice-doc-0.1.13-1 * girepository-Nice0.1-0.1.13-1 * gstreamer1.0-plugins-nice-0.1.13-1 Libnice is an implementation of the IETF's draft Interactive Connectivity Establishment standard (ICE). It provides GLib-based library, libnice and GStreamer elements. ICE is useful for applications that want to establish peer-to-peer UDP data streams. It automates the process of traversing NATs and provides security against some attacks. This is an update to the latest upstream release. The GStreamer 0.10 elements have been dropped in this release. -- Yaakov
[ANNOUNCEMENT] Application Indicators
The following packages have been uploaded to the Cygwin distribution: * indicator-applet-12.10.1-1 * indicator-application-12.10.0-1 * indicator-application-gtk2-12.10.0.1-1 * lxpanel-indicator-plugin-0.8.2-2 * mate-indicator-applet-1.14.1-1 * xfce4-indicator-plugin-2.3.3-1 * guake-0.8.8-1 * indicator-keylock-3.1.0-1 * pasystray-0.6.0-3 * pidgin-indicator-1.0-1 * transmission-2.92-3 * libappindicator1-12.10.0-1 * libappindicator-common-12.10.0-1 * libappindicator-devel-12.10.0-1 * libappindicator-doc-12.10.0-1 * libappindicator3_1-12.10.0-1 * libappindicator3-devel-12.10.0-1 * libdbusmenu-common-16.04.0-1 * libdbusmenu-glib4-16.04.0-1 * libdbusmenu-glib-devel-16.04.0-1 * libdbusmenu-glib-doc-16.04.0-1 * libdbusmenu-gtk3_4-16.04.0-1 * libdbusmenu-gtk3-devel-16.04.0-1 * libdbusmenu-gtk4-16.04.0-1 * libdbusmenu-gtk-devel-16.04.0-1 * libdbusmenu-gtk-doc-16.04.0-1 * libdbusmenu-jsonloader4-16.04.0-1 * libdbusmenu-jsonloader-devel-16.04.0-1 * libdbusmenu-tools-16.04.0-1 * libido0.1_0-12.10.0.1-1 * libido0.1-devel-12.10.0.1-1 * libido3_0.1_0-12.10.2-1 * libido3_0.1-devel-12.10.2-1 * libindicator7-12.10.1-1 * libindicator-common-12.10.1-1 * libindicator-devel-12.10.1-1 * libindicator-tools-12.10.1-1 * libindicator3_7-12.10.1-1 * libindicator3-devel-12.10.1-1 * libindicator3-tools-12.10.1-1 * girepository-AppIndicator0.1-12.10.0-1 * girepository-AppIndicator3_0.1-12.10.0-1 * girepository-Dbusmenu0.4-16.04.0-1 * girepository-DbusmenuGtk0.4-16.04.0-1 * girepository-DbusmenuGtk3_0.4-16.04.0-1 * python-appindicator-12.10.0-1 * vala-appindicator-12.10.0-1 * vala-appindicator3-12.10.0-1 * vala-dbusmenu-glib-16.04.0-1 * vala-dbusmenu-gtk-16.04.0-1 * vala-dbusmenu-gtk3-16.04.0-1 Application Indicators is a D-Bus framework for rendering "notification icons" in a uniform way which conforms with the rest of the desktop on which it is displayed, even when the toolkit thereof differs from that of the application. When no Indicator renderer is detected, Application Indicators support a default fallback which will create a GtkStatusIcon with the same icon as the Application Indicator. It supports the menu and responds to all the same state and icon changes. This feature comprises of several parts: * Indicator renderer applets for the GNOME, LXDE, MATE, and Xfce desktop panels (KDE and LXQt include this support natively); * The libappindicator and libappindicator3 libraries, and their bindings, for use by GTK+ applications; * Applications, or addons thereto, (re)built with this support. -- 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
Application Indicators
The following packages have been uploaded to the Cygwin distribution: * indicator-applet-12.10.1-1 * indicator-application-12.10.0-1 * indicator-application-gtk2-12.10.0.1-1 * lxpanel-indicator-plugin-0.8.2-2 * mate-indicator-applet-1.14.1-1 * xfce4-indicator-plugin-2.3.3-1 * guake-0.8.8-1 * indicator-keylock-3.1.0-1 * pasystray-0.6.0-3 * pidgin-indicator-1.0-1 * transmission-2.92-3 * libappindicator1-12.10.0-1 * libappindicator-common-12.10.0-1 * libappindicator-devel-12.10.0-1 * libappindicator-doc-12.10.0-1 * libappindicator3_1-12.10.0-1 * libappindicator3-devel-12.10.0-1 * libdbusmenu-common-16.04.0-1 * libdbusmenu-glib4-16.04.0-1 * libdbusmenu-glib-devel-16.04.0-1 * libdbusmenu-glib-doc-16.04.0-1 * libdbusmenu-gtk3_4-16.04.0-1 * libdbusmenu-gtk3-devel-16.04.0-1 * libdbusmenu-gtk4-16.04.0-1 * libdbusmenu-gtk-devel-16.04.0-1 * libdbusmenu-gtk-doc-16.04.0-1 * libdbusmenu-jsonloader4-16.04.0-1 * libdbusmenu-jsonloader-devel-16.04.0-1 * libdbusmenu-tools-16.04.0-1 * libido0.1_0-12.10.0.1-1 * libido0.1-devel-12.10.0.1-1 * libido3_0.1_0-12.10.2-1 * libido3_0.1-devel-12.10.2-1 * libindicator7-12.10.1-1 * libindicator-common-12.10.1-1 * libindicator-devel-12.10.1-1 * libindicator-tools-12.10.1-1 * libindicator3_7-12.10.1-1 * libindicator3-devel-12.10.1-1 * libindicator3-tools-12.10.1-1 * girepository-AppIndicator0.1-12.10.0-1 * girepository-AppIndicator3_0.1-12.10.0-1 * girepository-Dbusmenu0.4-16.04.0-1 * girepository-DbusmenuGtk0.4-16.04.0-1 * girepository-DbusmenuGtk3_0.4-16.04.0-1 * python-appindicator-12.10.0-1 * vala-appindicator-12.10.0-1 * vala-appindicator3-12.10.0-1 * vala-dbusmenu-glib-16.04.0-1 * vala-dbusmenu-gtk-16.04.0-1 * vala-dbusmenu-gtk3-16.04.0-1 Application Indicators is a D-Bus framework for rendering "notification icons" in a uniform way which conforms with the rest of the desktop on which it is displayed, even when the toolkit thereof differs from that of the application. When no Indicator renderer is detected, Application Indicators support a default fallback which will create a GtkStatusIcon with the same icon as the Application Indicator. It supports the menu and responds to all the same state and icon changes. This feature comprises of several parts: * Indicator renderer applets for the GNOME, LXDE, MATE, and Xfce desktop panels (KDE and LXQt include this support natively); * The libappindicator and libappindicator3 libraries, and their bindings, for use by GTK+ applications; * Applications, or addons thereto, (re)built with this support. -- Yaakov
[ANNOUNCEMENT] mediainfo 0.7.91-1
The following packages have been uploaded to the Cygwin distribution: * mediainfo-0.7.91-1 * mediainfo-gui-0.7.91-1 * mediainfo-qt-0.7.91-1 * libmediainfo0-0.7.91-1 * libmediainfo-devel-0.7.91-1 * libzen0-0.4.34-1 * libzen-devel-0.4.34-1 MediaInfo is a convenient unified display of the most relevant technical and tag data for video and audio files. This is an update to the latest upstream versions. The library packages are built separately in this release, and the Qt interface was added. -- 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
mediainfo 0.7.91-1
The following packages have been uploaded to the Cygwin distribution: * mediainfo-0.7.91-1 * mediainfo-gui-0.7.91-1 * mediainfo-qt-0.7.91-1 * libmediainfo0-0.7.91-1 * libmediainfo-devel-0.7.91-1 * libzen0-0.4.34-1 * libzen-devel-0.4.34-1 MediaInfo is a convenient unified display of the most relevant technical and tag data for video and audio files. This is an update to the latest upstream versions. The library packages are built separately in this release, and the Qt interface was added. -- Yaakov
Re: Problem with chdir and GetCurrentDirectory on Windows 2016
On Fri, Dec 9, 2016 at 8:24 AM, Dipak Gaigole wrote: > Agreed Andrey. But I couldn't find any API(s) which can serve my > requirements. And we can't afford to execute (fork+exec) tools like > cygpath for each getcwd call. > Any suggestions on improving this approach or any alternative approach > are always welcome. https://cygwin.com/cygwin-api/func-cygwin-conv-path.html Note the CCP_PROC_CYGDRIVE option. Csaba -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ The Tao of math: The numbers you can count are not the real numbers. Life is complex, with real and imaginary parts. "Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds "People disagree with me. I just ignore them." -- Linus Torvalds -- 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
