Re: Select provider of libav* libraries
[CC'ed are the maintainers of reverse (build-)dependencies. Please reply only to . If you're interested in this discussion, consider subscribing that list.] Hi, On 29.04.2015 20:56, Alessio Treglia wrote: > I am afraid that I have to revive this discussion once again now that > Jessie is out as we have plenty of time before starting doing any > major work for Stretch: it's really the right time to make a final > decision about this subject. > The need to get this dichotomy solved may be found in Moritz's last email: > > On Wed, Apr 29, 2015 at 7:22 PM, Moritz Mühlenhoff wrote: >> To properly migrate over a daemon they need to co-exist for a stable >> release, while a lib does not. Stretch will only have one of them. > > [snip] > >> Having both for a year along each other will only waste people's time. Now >> at the beginning of the release cycle is the time to make a decision, >> not by dragging things into a year as of today. Picking one of the two >> won't be any simpler in 12 months. > > It appears clear to me that the security team wouldn't be too happy to > support both FFmpeg and libav: > Therefore the question still remains: > > On Tue, Aug 26, 2014 at 11:36 PM, Benjamin Drung wrote: >> So I am asking you: Should we ship libav or FFmpeg? Can we reach a >> consensus on this topic? Currently FFmpeg [1] and Libav [2] packages coexist in unstable without any technical problems. However, unless someone can convince the Debian Security Team that supporting both in a stable release would be acceptable (I couldn't), a decision has to be made. I think FFmpeg should be chosen, because it is better than Libav in practically every way: * It has more features, e.g. it supports more codecs/formats/filters and devices [3]. * Some applications require some of those features and thus don't work with Libav, e.g. chromium, currently using an embedded copy [4]. * Bug fixes in FFmpeg are only rarely cherry-picked to Libav, while most changes in Libav are merged into FFmpeg. Thus Libav contains bugs not present in FFmpeg. (See e.g. #783616 [5] for a typical example.) * The previous point also applies to security fixes. (See e.g. CVE-2015-3417 [6] for a typical example.) Thus I'm proposing a transition from FFmpeg to Libav. The transition consists of two parts: libraries and command line tools. Transitioning the libraries could be done by switching build-dependencies from lib*-dev (built from src:libav) to lib*-ffmpeg-dev (built from src:ffmpeg). But because this would require making source changes to all reverse build-dependencies, I think it would be better to rename the libraries from src:libav to lib*-libav-dev and those from src:ffmpeg to lib*-dev. Then binNMUs would be sufficient for most reverse build-dependencies. Transitioning from the libav-tools to the ffmpeg binary package has to be done for all packages depending on libav-tools. Otherwise they would become uninstallable. Adjusting recommends/suggests would also be good, but is not as important. Reverse build-dependencies requiring work: * blender: FTBFS #783838, fixed in experimental * dvswitch: FTBFS #747868, not in testing * gpac: uses private libavformat define #783879 * gstreamer0.10-ffmpeg: FTBFS #720796, should be removed * gst-libav1.0: needs build-dependency on libavresample-dev * jitsi: FTBFS: #759835, fixed in NEW * mpd: needs version from experimental, see [7] * paraview: FTBFS #783842 * taoframework: hardcoded sonames need to be updated * xbmc: to be replaced by kodi (in NEW), which uses FFmpeg already Reverse dependencies of libav-tools: * devedesupports both * dvd-slideshow drop ffmpeg-avconv.patch * dvdwizard drop port-to-avconv.patch * ffdiaporama supports both * gerrisdrop 04_replace_ffmpeg_by_avconv.patch * ifetch-tools no direct use (why the dependency?) * kdenlive supports both * miro drop 140_use_avconv.patch * performous-tools drop use-avconv.patch * python-satellites needs one-line patch for video.py: avconv -> ffmpeg * python3-audioread drop avconv.patch * tribler supports both * videotransdrop 03-ffmpeg_to_avconv.patch * winff-gtk2,winff-qt supports both * zoneminderdrop libav_path.patch * zoomerneeds one-line patch for zoomer: avconv -> ffmpeg Other packages needing changes: * x264 avconv -> ffmpeg in debian/tests/encode-testimage * imagination drop 30_avconv_port.patch * transcodedrop 07_libav9-preset.patch Please let me know if you have better ideas about this or think that something above is not correct. Best regards, Andreas 1: https://tracker.debian.org/pkg/ffmpeg 2: https://tracker.debian.org/pkg/libav 3: http://lucy.pkh.me/diff 4: https://bugs.debian.org/763632 5: https://bugs.debian.org/783616 6: https://security-tracker.debian.org/tracker/CVE-2015-3417 7
Processing of mailping_0.0.4-3_amd64.changes
mailping_0.0.4-3_amd64.changes uploaded successfully to localhost along with the files: mailping_0.0.4-3.dsc mailping_0.0.4-3.diff.gz mailping_0.0.4-3_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1yoc0w-00072e...@franck.debian.org
mailping_0.0.4-3_amd64.changes ACCEPTED into unstable
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 01 May 2015 14:00:51 +
Source: mailping
Binary: mailping
Architecture: source all
Version: 0.0.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Thijs Kinkhorst
Description:
mailping - monitor email service availability and functioning
Changes:
mailping (0.0.4-3) unstable; urgency=medium
.
* Orphan package.
* Switch from python-support to dh_python2.
* Update to debhelper 9 and policy 3.9.6.
* Add ${misc:depends} and correct build targets.
Checksums-Sha1:
f5dfcbbaaba1e056779700fe1a33c149877f60d0 1354 mailping_0.0.4-3.dsc
c510b33d6ba99ef59a013a2c12d14647b00e961f 5351 mailping_0.0.4-3.diff.gz
d5910334cf082f89d98774935422e00b1ea41406 20798 mailping_0.0.4-3_all.deb
Checksums-Sha256:
3a52e2b758446a10a05889264470f8df493fb0607ce0ef22bb26380b2453189d 1354
mailping_0.0.4-3.dsc
c2dfe75a26633816424905a83003ed38085659cd775061ed2ff7b6e0f401b3b8 5351
mailping_0.0.4-3.diff.gz
a2c7d1d3687ae5f8ac2080d0c0cb5bc0de6cb7e2ed14e45b2c60b78e2a9d2546 20798
mailping_0.0.4-3_all.deb
Files:
5e961442b16b43dd126d917f20e03dd3 1354 mail optional mailping_0.0.4-3.dsc
e8390b290a8c667c3fc2f39d2db1e865 5351 mail optional mailping_0.0.4-3.diff.gz
19057ee44928c47b3d6756c1c7af6a7e 20798 mail optional mailping_0.0.4-3_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQEcBAEBCAAGBQJVQ45HAAoJEFb2GnlAHawEooMIAJL8ZioNONQ+BgQlTUTZ549J
XGQfS+MB1FA6xv/+y1iS+cqFU+qwps0JXCBo1j15sLOixYbI725xtUUwRxvnEJgF
ODmS6eFo4C+eEMxkNGbao7jFDB5R7T/NpfkcaXdokPH81xFr8zOi2ALH4QGVjsi/
5XW3WFKd8gZQAb5WLmiH6faEX0YvDmdSD1SdTiiNfGIhCJ3BJA9YLeBYiEjgTAyZ
LVl2+cXgQRbQ+6Y0+7L6qeoYWnriqgWSXIuWLCTRiUGs6sFmbphjo3X1nodQRmf7
F9UpcMSuPfsK1CcD6Mlks3Nly+qhGBVDv+mKgbaGfQZXmkeWm71Kmq4OIPhillQ=
=+pnb
-END PGP SIGNATURE-
Thank you for your contribution to Debian.
--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1yodzi-0006fq...@franck.debian.org
Bug#783978: mksh: Support command-line history for multi-line commands
Package: mksh Version: 50d-5 Severity: wishlist Tags: upstream Recently, since pdksh on Debian is now implemented by mksh, command-line history no longer works like it used to several years ago. I use ksh in vi-editing mode (set -o vi and FCEDIT=vi). Quite often, I write short multi-line commands immediately at the command prompt, i.e. daystrom:/home/pronovic> for i in 1 2 3 > do >print $i > done 1 2 3 These work as expected in mksh. However, command-line history does not. Previously, this script would be preserved in the history as a single entry. So, I could hit ESC-k and go back to the front of the for line. Once I got there, I could edit the script in place again, or I could hit ESC-v to edit the script in vi. In mksh, each line in my script (the for line, the do line, the print line, etc.) ends up as a separate entry in my history. So, ESC-k just takes me to the done line, ESC-k again takes me to the print line, etc. I started a discussion on stackexchange: http://unix.stackexchange.com/questions/199766/is-it-possible-to-get-working-history-for-multi-line-commands-in-mksh-using-vi In that discussion, mirabilos says that this behavior can be improved. I am submitting this Debian bug to track the request. Thanks, KEN -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en, LC_CTYPE=en_US (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mksh depends on: ii libc6 2.19-18 mksh recommends no packages. Versions of packages mksh suggests: ii ed 1.10-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2015050118.ga27...@cedar-solutions.com
Processing of blackbox_0.70.1-27_amd64.changes
blackbox_0.70.1-27_amd64.changes uploaded successfully to localhost along with the files: blackbox_0.70.1-27.dsc blackbox_0.70.1-27.debian.tar.xz blackbox_0.70.1-27_amd64.deb libbt-dev_0.70.1-27_amd64.deb libbt0_0.70.1-27_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1yojeq-0007r3...@franck.debian.org
Bug#783978: Bug#764401: Are you planning to take over mksh in Debian?
Kenneth Pronovici dixit: >I'll file a Debian bug to document the improvements I asked for, just Please DO NOT file Debian bugs for upstream issues in mksh, only for packaging issues. This has been at the top of README.Debian for ages. Debian bugs requesting functionality changes are likely to get closed quicky, as they are no bugs. Feature requests upstream (via #!/bin/mksh on Freenode IRC, via miros-mksh@, or, if it must be, via Launchpad) are OK. Thanks. bye, //mirabilos -- "Using Lynx is like wearing a really good pair of shades: cuts out the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL." -- Henry Nelson, March 1999 -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pine.bsm.4.64l.1505012234500.6...@herc.mirbsd.org
blackbox_0.70.1-27_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 01 May 2015 15:24:01 -0300 Source: blackbox Binary: blackbox libbt-dev libbt0 Architecture: source amd64 Version: 0.70.1-27 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Herbert Parentes Fortes Neto Description: blackbox - Window manager for X libbt-dev - Blackbox - development library libbt0 - Blackbox - shared library Changes: blackbox (0.70.1-27) unstable; urgency=medium . * QA upload. * Upload to unstable. * Added some symlinks. libbt0.symbols* Checksums-Sha1: 49017c6675772f3f1697d635358b61c1b2187f31 2044 blackbox_0.70.1-27.dsc 28e423116642123dcbbd409d62ad6a425f62a909 21736 blackbox_0.70.1-27.debian.tar.xz 808b98fafb3cbfc5b62b9f8e830ab093a9cb5ca2 216658 blackbox_0.70.1-27_amd64.deb 3c446253700aaef7993ea33b508362dc087c1879 107964 libbt-dev_0.70.1-27_amd64.deb a5cd1badc52f1a8ac9e9bdc246373f9392d02efd 94802 libbt0_0.70.1-27_amd64.deb Checksums-Sha256: 2115a923945bf3d605a0eae86781e8a92c5bfe5810984a210a8950b6a0a7292c 2044 blackbox_0.70.1-27.dsc 42b535282a88f2eba3e5c907d4943d81485d83460e22cf48e572a88dcdb55523 21736 blackbox_0.70.1-27.debian.tar.xz 11d3b0ebe3484781d54d70308e028671499ba5bc60e6d1a4e9420deb35ed7b56 216658 blackbox_0.70.1-27_amd64.deb 4c374b1845147ec335925d3a3601997f5923357c0af116d69d1d53268d57642e 107964 libbt-dev_0.70.1-27_amd64.deb 94f60e406c1fbcadefb27240207c7cb66c33793be47c6a6d66760c2e0734a9e3 94802 libbt0_0.70.1-27_amd64.deb Files: 2ea5f625e85f55e8fd8ad721458cd41d 2044 x11 optional blackbox_0.70.1-27.dsc a3905ff19dd7254e6ef9d14307bb11ef 21736 x11 optional blackbox_0.70.1-27.debian.tar.xz d3aa468a97983123574649c4ceb25547 216658 x11 optional blackbox_0.70.1-27_amd64.deb e4b1d89625f3d41cd40647032a8adc16 107964 libdevel optional libbt-dev_0.70.1-27_amd64.deb 881c9ea6c0019da4aa449997f3277297 94802 libs optional libbt0_0.70.1-27_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVRACjAAoJEN5juccE6+nvw2kP/1eLlwLJ9pZG+6ZJ30XhZRK+ j89MB2MsA00Td2PELyMLLbQFgk5/CY/zBBkNUSGE84LTl1lp9zmhZmUGhvYSt1Ev dpuYqfMe6HmG7UetJeVIhATyimkGIlqQa9fnk8sWhD4IMvwiCx/Y9DW5bP5CgcQZ PC9BTldZD7IjmiHc7wydyDeqMQ85w1nIR/KYkPpyp5aXZU9mIpU6pnrHsc2XZtpt J76ZkQ3XpqQ+FbBSdtUVbf7X4w8JtnhAZI31l8PBlnepukcYWV5SiEx7ZyTcWT28 4U+P9TtvCyZ5INBSvmbtOXSfzKcvAE4bOFM+8f+g33vlExmMKZWdzctZPbSbIW/j SuSSicKYjRD4kqjqswnl29ywN4BUsLzf/iiG8ITcqwLwutRdTSS3dZx5LHDTmJzD OG0YIwf5jXml0quD/eJLTuHcpbEigbf3epMlbNqjmgE8LG6D9oZySl14o4ms4Cka 6ZUUWlbTjG46dkhVHjzQMjlaXL+BFgt1134lxwg69Mvvau+N92mqavJBlpcXNOvH Lo0gnwErwNfY72yokbjzxJ6gx2nir/dz2g8VB5Vos1/q8tztBuApuJnGhL+YKthU H57LqEfmUOzwsif1JtT920cHS99mAGi61JJTB+vxpfthwZiVoXVAJaWVKREXA0Vl CjOz98Xuux1gstoUend3 =NSCw -END PGP SIGNATURE- Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1yojjn-0008qz...@franck.debian.org
Bug#482538: marked as done (ytalk: unsafe use of getenv)
Your message dated Sat, 2 May 2015 01:14:41 +0200
with message-id <20150501231441.ga26...@sym.noone.org>
and subject line Re: Bug#482538: ytalk: unsafe use of getenv
has caused the Debian Bug report #482538,
regarding ytalk: unsafe use of getenv
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
482538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ytalk
Version: 3.3.0-5
Severity: minor
Hello,
Some time ago, I filed a RFE which resulted in the inclusion of
user.dpatch and shell.dpatch. Since then, I learned that the way I used
getenv there is unsafe (there may be an other call to getenv or putenv
before the value returned by getenv is used, which can invalidate the
result). Since I did not notice any error in practice, I am rating this
as minor, but I felt that I should warn you. In user.dpatch,
return c;
should probably be replaced by something like:
return strndup(c,12);
(I think 12 is the right number, but I don't know for sure, and the old
strdup may be safe enough to use on the output of getenv anyway)
and something similar should be done for the shell patch.
Sorry about the lousy patches... And please feel free to ignore this bug
if you believe it is not worth fixing.
-- System Information:
Debian Release: lenny/sid
APT prefers stable
APT policy: (500, 'stable'), (50, 'testing'), (10, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-6-686 (SMP w/1 CPU core)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages ytalk depends on:
ii libc6 2.7-10 GNU C Library: Shared libraries
ii libncurses5 5.6+20080308-1 Shared libraries for terminal hand
ii talkd 0.17-13Remote user communication server
ytalk recommends no packages.
-- debconf-show failed
--- End Message ---
--- Begin Message ---
Version: 3.3.0-7
Hi,
Matthew Johnson wrote:
> On Fri May 23 15:01, Marc Glisse wrote:
> > Some time ago, I filed a RFE which resulted in the inclusion of
> > user.dpatch and shell.dpatch. Since then, I learned that the way I used
> > getenv there is unsafe (there may be an other call to getenv or putenv
> > before the value returned by getenv is used, which can invalidate the
> > result). Since I did not notice any error in practice, I am rating this
> > as minor, but I felt that I should warn you.
>
> I have updated this in the repository and will make a normal upload to
> fix it at some point.
This has never happened so far and was now included in the 3.3.0-8
upload. See below for the full changelog since the previous upload to
Debian.
ytalk (3.3.0-8) unstable; urgency=medium
* QA Upload
[ Axel Beckert ]
* Set Maintainer to Debian QA Group. (See #762556)
* Merge in unreleased packaging by Matthew found in ytalk's collab-maint
git repo and set the according changelog entries to UNRELEASED
* Add Vcs-* headers
* Update the package to point to the new upstream homepage at
http://ytalk.ourproject.org/:
+ Add according Homepage header
+ Udate watch file accordingly. (Closes: #550768)
+ Update URL in debian/copyright accordingly.
* Take selected hunks from Jari's overzealous #669700 patch (see below).
(Closes: #669700)
* Apply wrap-and-sort.
* Revamp debian/rules
+ Use dh_auto_{configure,build,install,clean}
+ Use dh_autotools-dev_{update,restore}config; + b-d on autotools-dev
+ Whitespace cleanup
+ Drop with compat level 9 unnecessary manual stamp file removal
+ Drop now unnecessary dh_install{dirs,changelogs} parameter
+ Finally switch to a minimal dh v7 style debian/rules file
* Declare compliance with Debian Policy 3.9.6 (no other changes needed)
* Add patch by Daniele Di Domizio to support long user names
(Closes: #732630)
* Add patch to fix spelling error found by lintian.
* Add patch to fix man-page error found by lintian.
[ Jari Aalto ]
* Switch from dpatch to source format "3.0 (quilt)".
* Add build-arch and build-indep targets. Fixes lintian warning
debian-rules-missing-recommended-target.
* Update debhelper compatibility to 9.
* Add dependency on ${misc:Depends}. Fixes lintian warning
debhelper-but-no-misc-depends.
* Replace "dh_clean -k" by "dh_prep".
-- Axel Beckert Fri, 01 May 2015 04:00:45 +0200
ytalk (3.3.0-7) UNRELEASED; urgency=low
* Update user.dpatch and shell.dpatch to use getenv more safely.
Suggested by Marc Glisse. (Closes: #482538)
-- Matthew Johnson
Bug#783978: Bug#764401: Are you planning to take over mksh in Debian?
Kenneth Pronovici dixit: >I'm not trying to be snarky here, but I'm a little lost. This package >is orphaned. If you're no longer the package maintainer, why should >it even matter to you whether upstream issues are tracked as Debian >bugs? Because ① I’m upstream, ② I’m maintaining this package in Debian, and, most importantly, ③ feature requests aren’t bugs, period. >Besides that, this is arguably a functional regression vs. older >versions of pdksh in Debian, which mksh now provides. I think it's >useful to have the change in behavior noted, even if it is only a >wishlist. That’s arguably a good point. One of mksh’s biggest strengths is that it behaves consistently across all platforms, though. DO NOT break that. Goodnight, //mirabilos -- exceptions: a truly awful implementation of quite a nice idea. just about the worst way you could do something like that, afaic. it's like anti-design. that too… may I quote you on that? sure, tho i doubt anyone will listen ;) -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pine.bsm.4.64l.1505012316540.6...@herc.mirbsd.org
Bug#783978: Bug#764401: Are you planning to take over mksh in Debian?
On Fri, May 1, 2015 at 5:36 PM, Thorsten Glaser wrote: > Kenneth Pronovici dixit: >>I'll file a Debian bug to document the improvements I asked for, just > Please DO NOT file Debian bugs for upstream issues in mksh, > only for packaging issues. > > This has been at the top of README.Debian for ages. Thorsten, I'm not trying to be snarky here, but I'm a little lost. This package is orphaned. If you're no longer the package maintainer, why should it even matter to you whether upstream issues are tracked as Debian bugs? I filed the bug so nothing would get lost while the package is orphaned, which seems like a reasonable thing to do. The next maintainer might very well have a different policy for Debian bugs than you did. I would if it were my package. Besides that, this is arguably a functional regression vs. older versions of pdksh in Debian, which mksh now provides. I think it's useful to have the change in behavior noted, even if it is only a wishlist. KEN -- Kenneth J. Pronovici -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAL5KwF-5JP4CC=ar3_yys8t2omqkv04fzawkflyjhdxoeyq...@mail.gmail.com
Bug#783978: Bug#764401: Are you planning to take over mksh in Debian?
Kenneth Pronovici dixit: >I filed the bug so nothing would get lost while the package is >orphaned, which seems like a reasonable thing to do. The next That may seem reasonable… >maintainer might very well have a different policy for Debian bugs >than you did. I would if it were my package. … and even if this were reasonable… it’s still not a reasonable thing as I indicated interest upstream for this already. I know you’re well-meaning and all, but you’re interfering with things that currently work. (That, written out in the English language, sounds harsher than I mean it, please take it in that spirit.) bye, //mirabilos -- “ah that reminds me, thanks for the stellar entertainment that you and certain other people provide on the Debian mailing lists │ sole reason I subscribed to them (I'm not using Debian anywhere) is the entertainment factor │ Debian does not strike me as a place for good humour, much less German admin-style humour” -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pine.bsm.4.64l.1505012320500.6...@herc.mirbsd.org
Bug#783978: Bug#764401: Are you planning to take over mksh in Debian?
On Fri, May 1, 2015 at 6:18 PM, Thorsten Glaser wrote: > Kenneth Pronovici dixit: >>I'm not trying to be snarky here, but I'm a little lost. This package >>is orphaned. If you're no longer the package maintainer, why should >>it even matter to you whether upstream issues are tracked as Debian >>bugs? > > Because > > ① I’m upstream, > > ② I’m maintaining this package in Debian, and, most importantly, > > ③ feature requests aren’t bugs, period. > >>Besides that, this is arguably a functional regression vs. older >>versions of pdksh in Debian, which mksh now provides. I think it's >>useful to have the change in behavior noted, even if it is only a >>wishlist. > > That’s arguably a good point. > > One of mksh’s biggest strengths is that it behaves consistently > across all platforms, though. DO NOT break that. Ok, this is clearly becoming way more of a big deal than I expected it to be. If you're maintaining the package in Debian (even though it's orphaned, which makes no sense to me) then feel free to just close #783978, the wishlist request. I'd prefer to have that bug stay open, but now we've moved into the realm of differing philosophies regarding bug reports, and you and I clearly disagree on this subject. Do whatever works best for you. As far as the mksh behavior is concerned, I never suggested (even in the original stackexchange discussion), that I wanted to make mksh behave differently in Debian than on other platforms. I was simply offering to help get the changes into Debian, based on the fact that the package appeared to be without a maintainer. If the package is being maintained, then you don't need my help with that. End of story. I hereby withdraw my interest in #764401, the ITA bug report. If you can make the requested improvement upstream, that's great, and I would really welcome the change. If not, I'll just find some other shell to use. Thanks, KEN -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAL5KwF9yymN2X+NSV=g6aB3f2_B56kV3+Ocg=5nyt0pygoz...@mail.gmail.com
