Bug#895718: python-pyqt5: import PyQt5.QtCore fails
On Sun, 24 Jun 2018 13:28:38 +0300 Adrian Bunk wrote: > On Mon, May 14, 2018 at 04:32:26PM -0300, Lisandro Damián Nicanor Pérez Meyer > wrote: > > On 14 May 2018 at 16:24, Mattia Rizzolo wrote: > > > On Mon, May 14, 2018 at 01:55:55PM -0300, Lisandro Damián Nicanor Pérez > > > Meyer wrote: > > >> Quoting from the above: > > >> > > >> The rationale of this system call is to provide resiliance against > > >> file descriptor exhaustion attacks, where the attacker consumes all > > >> available file descriptors, forcing the use of the fallback code where > > >> /dev/[u]random is not available. Since the fallback code is often not > > >> well-tested, it is better to eliminate this potential failure mode > > >> entirely. > > >> > > >> So if we disable it we disable a feature providing a more robust method > > >> to > > >> provide randomness to ours users. > > > > > > Reading this sounds like the presence of the syscall could be tested at > > > runtime, and if present used and if not fall back to dev/urandom? > > > > Patches directly at upstream (due to copyright issues) are welcomed :-) > > As far as I can see, there are 4 sane options available: > > 1. unsupported, and give a clear error > For working upgrades it is important that software in a stable release > works on kernels of the previous and next stable releases. > This also ends up being well-tested in upgrade scenarios. > Running buster on the jessie kernel is not really supported, > and even less tested. I don't think userland package maintainers should be expected to support anything older than the kernel version in the last stable release. If users really want that to work they should be responsible for relaxing the dependency in a way that the maintainer accepts. > libqt5core5a should abort with a clear error message in the preinst > on kernels < 3.17. > > 2. disable QT_CONFIG(getentropy) in Qt in buster This would presumably be the simplest approach; it's theoretically less secure but in practice it's exceedingly unlikely to be a problem. > 3. implement a fallback in Qt glibc now implements getentropy() and getrandom(), with fallbacks on aolder kernel versions. So I think that you could remove Qt's implementation of getentropy() and have it call glibc's instead. (But I haven't looked at the Qt code in question; it might not be quite as simple as that.) > 4. backport getrandom to the jessie kernel > getrandom is only ~ 20 LOC plus some syscall wiring, so if anyone wants > to convince/pay the Debian LTS team to backport that to the jessie > kernel it should be doable. [...] I don't think this meets the stable update criteria. In itself it wouldn't fix any weakness of the RNG. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part
[bts-link] source package qtcreator
# # bts-link upstream status pull for source package qtcreator # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #815676 (http://bugs.debian.org/815676) # Bug title: Bad indent after line with ternary operator in Qtcreator # * https://bugreports.qt.io/browse/QTCREATORBUG-15775 # * remote status changed: (?) -> Reported usertags 815676 + status-Reported # remote status report for #834543 (http://bugs.debian.org/834543) # Bug title: [qtcreator] Compiler path ignored # * https://bugreports.qt.io/browse/QTCREATORBUG-20373 # * remote status changed: (?) -> Closed # * remote resolution changed: (?) -> Out-of-scope # * closed upstream tags 834543 + fixed-upstream usertags 834543 + status-Closed resolution-Out-of-scope thanks
[bts-link] source package src:qtwebsockets-opensource-src
# # bts-link upstream status pull for source package src:qtwebsockets-opensource-src # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #895939 (http://bugs.debian.org/895939) # Bug title: qtwebsockets-opensource-src: FTBFS on hurd-i386: the requested timeout (5000 ms) was too short, 5150 ms would have been sufficient this time # * https://bugreports.qt.io/browse/QTBUG-67779 # * remote status changed: (?) -> Reported usertags 895939 + status-Reported thanks
[bts-link] source package qtbase-opensource-src
# # bts-link upstream status pull for source package qtbase-opensource-src # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #792133 (http://bugs.debian.org/792133) # Bug title: libqt5widgets5: doesn't honor the locales for "Date Modified" in file chooser for en_DK # * https://bugreports.qt.io/browse/QTBUG-67070 # * remote status changed: (?) -> Reported usertags 792133 + status-Reported # remote status report for #808822 (http://bugs.debian.org/808822) # Bug title: insufficient flags in pkgconfig --cflags # * https://bugreports.qt.io/browse/QTBUG-50156 # * remote status changed: (?) -> Open usertags 808822 + status-Open # remote status report for #809367 (http://bugs.debian.org/809367) # Bug title: libqt5gui5: XEMBED interop with gtksocket broken # * https://bugreports.qt.io/browse/QTBUG-50212 # * remote status changed: (?) -> Reported usertags 809367 + status-Reported # remote status report for #867794 (http://bugs.debian.org/867794) # Bug title: python3-pyqt5: App tray icon won't show if show() before systray is available # * https://bugreports.qt.io/browse/QTBUG-61898 # * remote status changed: (?) -> Reported usertags 867794 + status-Reported # remote status report for #867974 (http://bugs.debian.org/867974) # Bug title: libqt5gui5: new-delete-type-mismatch in QOpenGLContext destructor # * https://bugreports.qt.io/browse/QTBUG-57773 # * remote status changed: (?) -> Closed # * remote resolution changed: (?) -> Fixed # * closed upstream tags 867974 + fixed-upstream usertags 867974 + status-Closed resolution-Fixed # remote status report for #884956 (http://bugs.debian.org/884956) # Bug title: Qt 5: HiDPI scaling is broken # * https://bugreports.qt.io/browse/QTBUG-53022 # * remote status changed: (?) -> In-Progress usertags 884956 + status-In-Progress # remote status report for #890291 (http://bugs.debian.org/890291) # Bug title: libqt5core5a: Recent update breaks ALL QT app UIs # * https://bugreports.qt.io/browse/QTBUG-53022 # * remote status changed: (?) -> In-Progress usertags 890291 + status-In-Progress # remote status report for #899108 (http://bugs.debian.org/899108) # Bug title: vlc: after last security update (stretch), whenever vlc is started the gui is 10 times larger than normal. # * https://bugreports.qt.io/browse/QTBUG-53022 # * remote status changed: (?) -> In-Progress usertags 899108 + status-In-Progress thanks
[bts-link] source package qtdeclarative-opensource-src
# # bts-link upstream status pull for source package qtdeclarative-opensource-src # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #894726 (http://bugs.debian.org/894726) # Bug title: libqt5qml5: QQmlEngine segfaults on sparc64 # * https://bugreports.qt.io/browse/QTBUG-56264 # * remote status changed: (?) -> Reported usertags 894726 + status-Reported thanks
[bts-link] source package src:qtwebengine-opensource-src
# # bts-link upstream status pull for source package src:qtwebengine-opensource-src # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #888366 (http://bugs.debian.org/888366) # Bug title: qtwebengine-opensource-src: FTBFS with FFmpeg 4.0 # * https://bugreports.qt.io/browse/QTBUG-65086 # * remote status changed: (?) -> Reported usertags 888366 + status-Reported thanks
[bts-link] source package qtchooser
# # bts-link upstream status pull for source package qtchooser # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #878361 (http://bugs.debian.org/878361) # Bug title: qtchooser misinterprets -qtconf # * https://bugreports.qt.io/browse/QTBUG-63769 # * remote status changed: (?) -> Open usertags 878361 + status-Open thanks
[bts-link] source package src:qtbase-opensource-src
# # bts-link upstream status pull for source package src:qtbase-opensource-src # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #814959 (http://bugs.debian.org/814959) # Bug title: Keyboard mapping broken with Qt5 apps in TightVNC, possibly due to missing XKEYBOARD extension # * https://bugreports.qt.io/browse/QTBUG-44938 # * remote status changed: (?) -> Closed # * remote resolution changed: (?) -> Done # * closed upstream tags 814959 + fixed-upstream usertags 814959 + status-Closed resolution-Done # remote status report for #818232 (http://bugs.debian.org/818232) # Bug title: qgo: Unable to type via VNC, keys not matching # * https://bugreports.qt.io/browse/QTBUG-44938 # * remote status changed: (?) -> Closed # * remote resolution changed: (?) -> Done # * closed upstream tags 818232 + fixed-upstream usertags 818232 + status-Closed resolution-Done # remote status report for #899274 (http://bugs.debian.org/899274) # Bug title: KMail does not always remember the desired message list columns # * https://bugreports.qt.io/browse/QTBUG-65478 # * remote status changed: (?) -> Closed # * remote resolution changed: (?) -> Fixed # * closed upstream tags 899274 + fixed-upstream usertags 899274 + status-Closed resolution-Fixed thanks
[bts-link] source package plasma-workspace
# # bts-link upstream status pull for source package plasma-workspace # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #876907 (http://bugs.debian.org/876907) # Bug title: /usr/bin/plasmashell: System tray popups and application menu break when virtual desktops used # * http://bugs.kde.org/show_bug.cgi?id=377956 # * remote status changed: RESOLVED -> REOPENED # * remote resolution changed: FIXED -> (?) # * reopen upstream forwarded 876907 https://bugs.kde.org/show_bug.cgi?id=377956 tags 876907 - fixed-upstream usertags 876907 - status-RESOLVED resolution-FIXED usertags 876907 + status-REOPENED thanks
Processed: [bts-link] source package qtbase-opensource-src
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package qtbase-opensource-src > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #792133 (http://bugs.debian.org/792133) > # Bug title: libqt5widgets5: doesn't honor the locales for "Date Modified" in > file chooser for en_DK > # * https://bugreports.qt.io/browse/QTBUG-67070 > # * remote status changed: (?) -> Reported > usertags 792133 + status-Reported There were no usertags set. Usertags are now: status-Reported. > # remote status report for #808822 (http://bugs.debian.org/808822) > # Bug title: insufficient flags in pkgconfig --cflags > # * https://bugreports.qt.io/browse/QTBUG-50156 > # * remote status changed: (?) -> Open > usertags 808822 + status-Open There were no usertags set. Usertags are now: status-Open. > # remote status report for #809367 (http://bugs.debian.org/809367) > # Bug title: libqt5gui5: XEMBED interop with gtksocket broken > # * https://bugreports.qt.io/browse/QTBUG-50212 > # * remote status changed: (?) -> Reported > usertags 809367 + status-Reported There were no usertags set. Usertags are now: status-Reported. > # remote status report for #867794 (http://bugs.debian.org/867794) > # Bug title: python3-pyqt5: App tray icon won't show if show() before systray > is available > # * https://bugreports.qt.io/browse/QTBUG-61898 > # * remote status changed: (?) -> Reported > usertags 867794 + status-Reported There were no usertags set. Usertags are now: status-Reported. > # remote status report for #867974 (http://bugs.debian.org/867974) > # Bug title: libqt5gui5: new-delete-type-mismatch in QOpenGLContext destructor > # * https://bugreports.qt.io/browse/QTBUG-57773 > # * remote status changed: (?) -> Closed > # * remote resolution changed: (?) -> Fixed > # * closed upstream > tags 867974 + fixed-upstream Bug #867974 [libqt5gui5] libqt5gui5: new-delete-type-mismatch in QOpenGLContext destructor Added tag(s) fixed-upstream. > usertags 867974 + status-Closed resolution-Fixed There were no usertags set. Usertags are now: resolution-Fixed status-Closed. > # remote status report for #884956 (http://bugs.debian.org/884956) > # Bug title: Qt 5: HiDPI scaling is broken > # * https://bugreports.qt.io/browse/QTBUG-53022 > # * remote status changed: (?) -> In-Progress > usertags 884956 + status-In-Progress There were no usertags set. Usertags are now: status-In-Progress. > # remote status report for #890291 (http://bugs.debian.org/890291) > # Bug title: libqt5core5a: Recent update breaks ALL QT app UIs > # * https://bugreports.qt.io/browse/QTBUG-53022 > # * remote status changed: (?) -> In-Progress > usertags 890291 + status-In-Progress There were no usertags set. Usertags are now: status-In-Progress. > # remote status report for #899108 (http://bugs.debian.org/899108) > # Bug title: vlc: after last security update (stretch), whenever vlc is > started the gui is 10 times larger than normal. > # * https://bugreports.qt.io/browse/QTBUG-53022 > # * remote status changed: (?) -> In-Progress > usertags 899108 + status-In-Progress There were no usertags set. Usertags are now: status-In-Progress. > thanks Stopping processing here. Please contact me if you need assistance. -- 867974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867974 899108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package qtcreator
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package qtcreator > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #815676 (http://bugs.debian.org/815676) > # Bug title: Bad indent after line with ternary operator in Qtcreator > # * https://bugreports.qt.io/browse/QTCREATORBUG-15775 > # * remote status changed: (?) -> Reported > usertags 815676 + status-Reported There were no usertags set. Usertags are now: status-Reported. > # remote status report for #834543 (http://bugs.debian.org/834543) > # Bug title: [qtcreator] Compiler path ignored > # * https://bugreports.qt.io/browse/QTCREATORBUG-20373 > # * remote status changed: (?) -> Closed > # * remote resolution changed: (?) -> Out-of-scope > # * closed upstream > tags 834543 + fixed-upstream Bug #834543 [qtcreator] [qtcreator] Compiler path ignored Added tag(s) fixed-upstream. > usertags 834543 + status-Closed resolution-Out-of-scope There were no usertags set. Usertags are now: status-Closed resolution-Out-of-scope. > thanks Stopping processing here. Please contact me if you need assistance. -- 834543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834543 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package plasma-workspace
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package plasma-workspace > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #876907 (http://bugs.debian.org/876907) > # Bug title: /usr/bin/plasmashell: System tray popups and application menu > break when virtual desktops used > # * http://bugs.kde.org/show_bug.cgi?id=377956 > # * remote status changed: RESOLVED -> REOPENED > # * remote resolution changed: FIXED -> (?) > # * reopen upstream > forwarded 876907 https://bugs.kde.org/show_bug.cgi?id=377956 Bug #876907 [plasma-workspace] /usr/bin/plasmashell: System tray popups and application menu break when virtual desktops used Changed Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=377956' from 'https://bugs.kde.org/show_bug.cgi?id=377956, merged-upstream: http://bugs.kde.org/show_bug.cgi?id=381242'. > tags 876907 - fixed-upstream Bug #876907 [plasma-workspace] /usr/bin/plasmashell: System tray popups and application menu break when virtual desktops used Removed tag(s) fixed-upstream. > usertags 876907 - status-RESOLVED resolution-FIXED Usertags were: status-RESOLVED resolution-FIXED. Usertags are now: . > usertags 876907 + status-REOPENED There were no usertags set. Usertags are now: status-REOPENED. > thanks Stopping processing here. Please contact me if you need assistance. -- 876907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:qtbase-opensource-src
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:qtbase-opensource-src > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #814959 (http://bugs.debian.org/814959) > # Bug title: Keyboard mapping broken with Qt5 apps in TightVNC, possibly due > to missing XKEYBOARD extension > # * https://bugreports.qt.io/browse/QTBUG-44938 > # * remote status changed: (?) -> Closed > # * remote resolution changed: (?) -> Done > # * closed upstream > tags 814959 + fixed-upstream Bug #814959 [src:qtbase-opensource-src] Keyboard mapping broken with Qt5 apps in TightVNC, possibly due to missing XKEYBOARD extension Added tag(s) fixed-upstream. > usertags 814959 + status-Closed resolution-Done There were no usertags set. Usertags are now: resolution-Done status-Closed. > # remote status report for #818232 (http://bugs.debian.org/818232) > # Bug title: qgo: Unable to type via VNC, keys not matching > # * https://bugreports.qt.io/browse/QTBUG-44938 > # * remote status changed: (?) -> Closed > # * remote resolution changed: (?) -> Done > # * closed upstream > tags 818232 + fixed-upstream Bug #818232 [src:qtbase-opensource-src] qgo: Unable to type via VNC, keys not matching Added tag(s) fixed-upstream. > usertags 818232 + status-Closed resolution-Done There were no usertags set. Usertags are now: status-Closed resolution-Done. > # remote status report for #899274 (http://bugs.debian.org/899274) > # Bug title: KMail does not always remember the desired message list columns > # * https://bugreports.qt.io/browse/QTBUG-65478 > # * remote status changed: (?) -> Closed > # * remote resolution changed: (?) -> Fixed > # * closed upstream > tags 899274 + fixed-upstream Bug #899274 [src:qtbase-opensource-src] KMail does not always remember the desired message list columns Added tag(s) fixed-upstream. > usertags 899274 + status-Closed resolution-Fixed There were no usertags set. Usertags are now: status-Closed resolution-Fixed. > thanks Stopping processing here. Please contact me if you need assistance. -- 814959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814959 818232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818232 899274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
[bts-link] source package src:qtwebkit-opensource-src
# # bts-link upstream status pull for source package src:qtwebkit-opensource-src # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #779569 (http://bugs.debian.org/779569) # Bug title: addToJavaScriptWindowObject exports QObject's slots by default # * https://bugreports.qt.io/browse/QTBUG-45049 # * remote status changed: (?) -> Open usertags 779569 + status-Open thanks
[bts-link] source package qttools-opensource-src
# # bts-link upstream status pull for source package qttools-opensource-src # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #823822 (http://bugs.debian.org/823822) # Bug title: qttools5-dev-tools: lupdate is super slow # * https://bugreports.qt.io/browse/QTBUG-27936 # * remote status changed: (?) -> Open usertags 823822 + status-Open # remote status report for #875847 (http://bugs.debian.org/875847) # Bug title: qttools5-dev-tools: .qhc files not reproducible # * https://bugreports.qt.io/browse/QTBUG-62697 # * remote status changed: (?) -> Reported usertags 875847 + status-Reported thanks
[bts-link] source package qtquickcontrols-opensource-src
# # bts-link upstream status pull for source package qtquickcontrols-opensource-src # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #779221 (http://bugs.debian.org/779221) # Bug title: qtquickcontrols5-examples: resizing QT window is jerky, redraw/resize problem # * https://bugreports.qt.io/browse/QTBUG-44733 # * remote status changed: (?) -> Reported usertags 779221 + status-Reported thanks
Bug#894476: rcc: please honour SOURCE_DATE_EPOCH
Thorsten, > > far easier and clearer IMHO to statelessly state that clamping is not > > required when using SOURCE_DATE_EPOCH. :) > > OK, now I do not understand _that_… (It's clearer to say "X is the situation" vs "when you said Y before that was correct/incorrect") Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#894476: rcc: please honour SOURCE_DATE_EPOCH
On Mon, 9 Jul 2018, Chris Lamb wrote: > far easier and clearer IMHO to statelessly state that clamping is not > required when using SOURCE_DATE_EPOCH. :) OK, now I do not understand _that_… Doesn’t matter as long as this bug gets fixed, though ☻☺ Have a nice day, //mirabilos -- >> Why don't you use JavaScript? I also don't like enabling JavaScript in > Because I use lynx as browser. +1 -- Octavio Alvarez, me and ⡍⠁⠗⠊⠕ (Mario Lang) on debian-devel
Bug#894476: rcc: please honour SOURCE_DATE_EPOCH
Hi Thorsten, > > It is not required. > > I’m parsing this as “you were not incorrect”, right? It doesn't really matter whether you were correct or incorrect in the past and seems a little silly to debate that; far easier and clearer IMHO to statelessly state that clamping is not required when using SOURCE_DATE_EPOCH. :) > > I've found that having a shared vocabulary is very useful so just in > > case it helps we tend to use the term "clamping" when referring to > > True… it’s just that I didn’t recall the word, as “clamping” > is not something normally part of my English vocabulary […] I might agree it's esoteric word/usage, but not only is it already "out there", we have more problems with "reproducible" to worry about this one too much alas. > I’ll try to remember next time. Again, no question of blame or apologies here… :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#894476: rcc: please honour SOURCE_DATE_EPOCH
Hi Chris, > It is not required. I’m parsing this as “you were not incorrect”, right? (Sorry, non-English-native speaker here.) > Does the canonical specification not explain? > > https://reproducible-builds.org/specs/source-date-epoch/ > > I pedantically refer you to that /only/ because if it is not clear > enough then there is a need to revise it. :) It is indeed clear enough. I didn’t have it at hand when writing my previous message and only vaguely recalled having read it quite some time before. (Thanks for linking it in this thread.) > > AIUI, S_D_E is used as a *delimiter*, not as a timestamp *all* files > > are to be set to. > > I've found that having a shared vocabulary is very useful so just in > case it helps we tend to use the term "clamping" when referring to True… it’s just that I didn’t recall the word, as “clamping” is not something normally part of my English vocabulary (and, having looked it up in the dictionary, nothing I’d normally associate with this), so it’s probably a “lost in translation” effect. I’ll try to remember next time. Thanks, //mirabilos -- 15:41⎜ Somebody write a testsuite for helloworld :-)
