On 8/1/2019 5:17 PM, Ken Brown wrote:
> On 8/1/2019 12:04 PM, Corinna Vinschen wrote:
>> On Aug 1 10:38, Eric Blake wrote:
>>> On 8/1/19 10:30 AM, Ken Brown wrote:
>>>
>> OK, when xwin-xdg-menu launches an application, it creates two pipes
>> and sets
>> the application's stdout and
On 8/1/2019 12:04 PM, Corinna Vinschen wrote:
> On Aug 1 10:38, Eric Blake wrote:
>> On 8/1/19 10:30 AM, Ken Brown wrote:
>>
> OK, when xwin-xdg-menu launches an application, it creates two pipes
> and sets
> the application's stdout and stderr to the write ends of those pipes.
>>
>>>
Hello i got an error code in on of your Iso Tools (WIT) WIT-Problem -
Pastebin.com
|
|
|
| ||
|
|
|
| |
WIT-Problem - Pastebin.com
| |
|
|
It would be good if you can say me what the problem is and in the patch.bat (i
want to create a custom NSMBW
The openldap package in Cygwin has been updated to the latest upstream
version 2.4.48. This is the first release after taking over from the
previous maintainer, the packaging is unchanged. Like the previous
maintainer, I don't actually use the server components of openldap, so
use them with
The openldap package in Cygwin has been updated to the latest upstream
version 2.4.48. This is the first release after taking over from the
previous maintainer, the packaging is unchanged. Like the previous
maintainer, I don't actually use the server components of openldap, so
use them with
The package released yesterday had no symbols generated for the static
library. This is a rebuild to fix that error, the faulty package has
been removed.
--
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailing list, look
at the
The package released yesterday had no symbols generated for the static
library. This is a rebuild to fix that error, the faulty package has
been removed.
--
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailing list, look
at the
Jon Turney writes:
>> setup-x86_64.exe -q -L -l %cd%\cygwin-repo -R C:\PGM\cygwin64 -P
>>
Add an optional parameter to set_action(), to indicate the action is the
result of user action, and only set user_picked then.
Set that parameter when installing from the command line. All other user
actions come through select_action(), so also set that parameter there.
---
choose.cc | 2
Use the stored action in packagemeta::action_caption(), rather than
working backwards from desired/installed/picked.
---
package_meta.cc | 30 +-
1 file changed, 17 insertions(+), 13 deletions(-)
diff --git a/package_meta.cc b/package_meta.cc
index 8fad50d..b417fb0
Use the stored action in packagemeta::list_actions(), rather than
working backwards from desired/installed/picked.
---
package_meta.cc | 26 ++
1 file changed, 6 insertions(+), 20 deletions(-)
diff --git a/package_meta.cc b/package_meta.cc
index 2564f95..8fad50d 100644
Now we have the flexibilty to record a package as explicitly required to
be installed, rather than merely installed because the desired version
is different to the installed version, we can record packages selected
for installation on the command line as distinct from choosing a
specific version
Use stored action in setting up the solver, rather than working out what
the action was from _picked/installed/desired.
---
libsolv.cc | 47 ++-
1 file changed, 26 insertions(+), 21 deletions(-)
diff --git a/libsolv.cc b/libsolv.cc
index
Use packagemeta::set_action() to update the action for packagemeta
object in more (hopefully all) the places it gets changed.
(Future work: ideally we'd opaque packagemeta internals more by making
installed/curr/desired/etc. object private, rather than letting users
grovel around in those
Store the action requested with set_action() in the packagemeta object,
rather than just encoding it in _picked/installed/desired (see
discussion in commit 4209699d)
Try to avoid meaningless states occuring, i.e. action=Install with
desired=installed is converted to action=Keep.
Future work:
---
PickCategoryLine.cc | 2 +-
PickView.h | 2 +-
choose.cc | 6 +++---
package_meta.cc | 19 +++
package_meta.h | 2 +-
5 files changed, 17 insertions(+), 14 deletions(-)
diff --git a/PickCategoryLine.cc b/PickCategoryLine.cc
index
---
package_meta.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/package_meta.h b/package_meta.h
index 1f0361e..2c40102 100644
--- a/package_meta.h
+++ b/package_meta.h
@@ -140,8 +140,6 @@ public:
bool srcpicked() const; /* true if source for desired version is to be
e.g. setup -q -g -P python3-lxml (which used to do something useful)
currently gets you an (empty) python3-lxml package, which will be replaced
by python36-lxml (which obsoletes it) on the next setup run. After this
change, python36-lxml is installed instead.
See also the dicusssion at
Contains an identical value to packagemeta::name
---
package_meta.cc | 2 +-
package_meta.h | 3 +--
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/package_meta.cc b/package_meta.cc
index 3509f05..a4f6c93 100644
--- a/package_meta.cc
+++ b/package_meta.cc
@@ -70,7 +70,7 @@
The only use this column appears to have now is that unticking it is the
same as selecting 'uninstall'.
Future work: Make 'Src?' column more independent, rather than
interacting with the 'New' (action) column in non-obvious ways. We
should be able to choose to install source irrespective of the
On Aug 1 10:38, Eric Blake wrote:
> On 8/1/19 10:30 AM, Ken Brown wrote:
>
> >>> OK, when xwin-xdg-menu launches an application, it creates two pipes
> >>> and sets
> >>> the application's stdout and stderr to the write ends of those pipes.
>
> > Well, I can't be sure that the pipes are
On 29/07/2019 11:13, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
Dear all,
I am trying to prepare an offline installation of Cygwin with a local
repository and I am facing the problem with the package selection.
The packages specified by the -P command are not selected, so they
end up without being
On 8/1/19 10:30 AM, Ken Brown wrote:
>>> OK, when xwin-xdg-menu launches an application, it creates two pipes
>>> and sets
>>> the application's stdout and stderr to the write ends of those pipes.
> Well, I can't be sure that the pipes are responsible. It's just that
> the existence of the
On 8/1/2019 10:27 AM, Jon Turney wrote:
> On 31/07/2019 19:00, Ken Brown wrote:
>> On 7/31/2019 11:53 AM, Ken Brown wrote:
>>> On 7/29/2019 2:55 PM, Ken Brown wrote:
Here's the error that I can reproduce easily in xterm:
$ ls <(grep bash .bashrc)
/dev/fd/63
grep: write
On Thu, 1 Aug 2019 12:19:55, Ken Brown wrote:
> As I said, the problem only occurs in terminals started from the
> xwin-xdg-menu.
> That isn't what you did. Here are the reproduction instructions again:
Entendu!
> 1. Start the X server using the XWin Server shortcut in the Start Menu (look
On 31/07/2019 19:00, Ken Brown wrote:
On 7/31/2019 11:53 AM, Ken Brown wrote:
On 7/29/2019 2:55 PM, Ken Brown wrote:
Here's the error that I can reproduce easily in xterm:
$ ls <(grep bash .bashrc)
/dev/fd/63
grep: write error: Broken pipe
This happens 98% of the time. Notice that I used
On 8/1/2019 6:03 AM, Houder wrote:
> On Wed, 31 Jul 2019 15:53:27, Ken Brown wrote:
>
>> I've made some progress. It turns out that the problem only occurs in
>> terminals
>> launched from the xwin-xdg-menu tray icon. I can even launch a mintty window
>> from that icon (System Tools -> Cygwin
On Thu, 01 Aug 2019 12:03:34, Houder wrote:
> On Wed, 31 Jul 2019 15:53:27, Ken Brown wrote:
>
> > I've made some progress. It turns out that the problem only occurs in
> > terminals
> > launched from the xwin-xdg-menu tray icon. I can even launch a mintty
> > window
> > from that icon
On Wed, 31 Jul 2019 15:53:27, Ken Brown wrote:
> I've made some progress. It turns out that the problem only occurs in
> terminals
> launched from the xwin-xdg-menu tray icon. I can even launch a mintty window
> from that icon (System Tools -> Cygwin Terminal) and I'll see the problem.
>
On 7/31/19 7:25 PM, Ken Brown wrote:
> On 7/31/2019 12:59 PM, Corinna Vinschen wrote:
>> On Jul 31 12:35, Michael Haubenwallner wrote:
>>> On 7/30/19 6:07 PM, Corinna Vinschen wrote:
On Jul 30 17:22, Michael Haubenwallner wrote:
> Hi,
>
> following up
>
Not even the zip archive can help, because the symlinks are not preserved.
Maybe a tar file, but it would be really better to have installer fixed. Is
there any option to force the installer to install everything found in the
local repository?
Panos
-Original Message-
From:
On Jul 31 18:00, Ken Brown wrote:
> On 7/31/2019 11:53 AM, Ken Brown wrote:
> > On 7/29/2019 2:55 PM, Ken Brown wrote:
> >> Here's the error that I can reproduce easily in xterm:
> >>
> >> $ ls <(grep bash .bashrc)
> >> /dev/fd/63
> >> grep: write error: Broken pipe
> >>[...]
> > [...]
>
> OK,
32 matches
Mail list logo
