With that I'm closing this LP bug by updating it to Won't Fix.
(This does not mean that fixes will never be possible or done at all,
'Won't Fix' in this case indicates that the workaround / alternative fix was
not desired, hence was not chosen; and it was taken in lieu of a better status.)
**
I've removed this from the queue as requested. Thank you for all your
work on this!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056485
Title:
Behaviour of socat in Ubuntu 20.04 unexpected
To
Hello @Jamie, thanks for your answer and feedback. Your decision is
understood.
@Robie Based on this, there is no need to follow the alternative
approach anymore, and I think this SRU request can be recalled and I
would like to ask you to reject socat from the focal unapproved queue.
--
You
> would like this avenue to be investigated
To be clear, I mean the general avenue of workarounds in mkvterm, not
necessarily my specific idea.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056485
I consulted with other SRU team members today.
We agree that the bug is valid and that the current behaviour is wrong.
However, if we were to change behaviour, the concern is that existing
users might be regressed in a way that will be difficult for them to
track down. The trade-off we must make
Well, to me it looks like socat is like a Swiss army knife, where some
features are popular and are used often, but others are very rarely
used.
Also please consider potential reactions of users that run into this (or
similar cases):
1) (trivial) Users notice this problem (or not) and don't do
Interleaving Frank's and jldolan's comments here:
> I just assumed socat was not a very popular package.
My experience is the opposite! I understand it to be used in all kinds
of corners - particularly in user scripts that don't appear in the
archive.
> I've learned (and I generally agree with
** Changed in: socat (Ubuntu Focal)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056485
Title:
Behaviour of socat in Ubuntu 20.04 unexpected
To manage
Thanks for having a look at this SRU.
The general compile of the socat code works after just having commit
5ebf36038f39 "Under certain circumstances, options of the first address
were applied to the second address" applied.
However, the build also triggers a huge amount of tests, and one, test
SRU review
Please could you explain why "minor-corrections-in-makefile-and-test-
sh.patch" is required - in particular the change to Makefile.in, but
also the test change? If only parts are required, can the patch be made
more minimal?
> [ Where problems could occur ]
I accept that this is a
** Changed in: socat (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056485
Title:
Behaviour of socat in Ubuntu 20.04 unexpected
To manage
** Also affects: socat (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: socat (Ubuntu Focal)
Status: New => In Progress
** Changed in: socat (Ubuntu)
Status: In Progress => Invalid
** Changed in: socat (Ubuntu Focal)
Importance: Undecided => High
**
New build (with changes squashed into one) are successfully build here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp2056485-2
Especially test #384 was successful:
"
test 384 SOCAT_OPT_HINT: check if merging single character options is
rejected... OK
"
The overall test results are like
Debdiff for socat/focal (from 1.7.3.3-2 to 1.7.3.3-2ubuntu0.1).
** Patch added: "debdiff_socat_focal_1.7.3.3-2_to_1.7.3.3-2ubuntu0.1.diff"
https://bugs.launchpad.net/ubuntu/+source/socat/+bug/2056485/+attachment/5754053/+files/debdiff_socat_focal_1.7.3.3-2_to_1.7.3.3-2ubuntu0.1.diff
**
The second build with the additional patch succeeded:
https://launchpad.net/~fheimes/+archive/ubuntu/lp2056485
"
test 385 TERMIOS_PH_ALL: are termios options applied to the correct address...
OK
"
(actually all test were not successfully completed)
I'm now merging both into one package change
I kicked-off some initial test builds in PPA, but one test fails now:
"
test 385 TERMIOS_PH_ALL: are termios options applied to the correct address...
FAILED
./socat -t 0.1 -T 1 STDIO,echo=0 EXEC:cat
"
and I see that is related, and got added to test.sh by the requested patch:
"
+# test for a
** Summary changed:
- Multiple issues found on Ubuntu 20.04 against socat
+ Behaviour of socat in Ubuntu 20.04 unexpected
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056485
Title:
Behaviour of
17 matches
Mail list logo
