Mike Hommey glandium.org> writes:
> I'm saying you can't derive any knowledge from that debian-legal post
> about screenshot of games.
Mhm. AIUI the messages, the base for the reasoning is that the
imagery is the product of the game code, which is not the fact
here.
//mirabilos
--
To UNSUBSC
Julien Cristau debian.org> writes:
> It should just be forced despite the bd-uninstallable. sysvinit-utils
> and util-linux are essential, so they're already in the build chroot, so
> whether a newer version is available and uninstallable doesn't matter.
Not if the B-D is versioned, unfortunate
Ian Jackson chiark.greenend.org.uk> writes:
> I would like to think some more about the workflows of the existing
> tools people are using to work with Debian and git, so that I can
I tend to have the entire tree “as seen from Debian” in version control,
so I can just throw the .orig.tar.* to ..
On Fri, 17 Jul 2015, Adrien CLERC wrote:
> Maybe you should try the "I am an advanced user" of uBlock (or uBlock
> Origin, it's up to you). It replaces AdblockPlus and RequestPolicy in a
> much more efficient UI for me. More complex also…
Hm, but, tbh, I’m not. I absolutely hate Firef*x but there
Adam Borowski angband.pl> writes:
> Note that while requestpolicycontinued is capable to do everything original
> requestpolicy did, in its default mode it's just a poor ad blocker,
The new xul-ext-requestpolicy is a severe regression from the old one:
• it defaults to all permitted
• it fails
Ian Jackson chiark.greenend.org.uk> writes:
> The problem is simply that the icons are non-DFSG-free.
You could make a screenshot from where the original icons are shown,
then re-encode those tiny 16x16px thingies into new *.ico files with
GIMP. This is sorta like taking a photograph (if in doub
Ian Jackson chiark.greenend.org.uk> writes:
>For example, in this case, it would be technically possible for
>(say) Google (or someone masquerading as Google) to change the icon
>offered to Debian's Iceweasel to one which looks very like
>Wikipedia's icon.
FWIW, there are DuckDuc
On Tue, 16 Jun 2015, Wookey wrote:
> This is a worthy goal, but I've had long conversations about this,
> trying to think up some 'neutral' names which aren't confusing and
> have failed. After much hand-wringing I concluded that one might as
> well just use the GNU names as we use GNU conventions
Guillem Jover debian.org> writes:
> On Mon, 2015-05-11 at 01:34:08 +0200, Matthias Klose wrote:
> > On 05/10/2015 03:32 AM, Guillem Jover wrote:
> > > CC_FOR_BUILD = gcc
Plus, what Wookey said.
> > the above mentioned wiki pages still talk about HOSTCC and BUILDCC. Please
> > clarify when to us
Jonas Smedegaard jones.dk> writes:
> Standard approach in The Perl team seems to be to skip the license
> granting statement (i.e. verbatim-from-license-issuer text) and include
> only license boilerplates (i.e. verbatim-from-license-author texts),
That is rather… interesting… as the licence
Dimitri John Ledkov debian.org> writes:
> somebody else did a bad rebase, and then people started to query why I
You should just not accept rebase, *ever*.
[receive]
denyNonFastforwards = true
denyDeletes = true
This is the standard config of all Evolvis (FusionForge inhouse va
Jonas Smedegaard jones.dk> writes:
> What I do is add a custom build target that rewrites debian/control
> based on rmadison query resolving current archs for a given package.
Please don’t forget the debian-ports architectures for this. (I think
this is a point where not-even-on-dpo new archite
Ansgar Burchardt debian.org> writes:
> Please be aware that --force-yes makes apt ignore invalid signatures for
Ouch.
What is the equivalent of --force-yes with*out* --allow-unauthenticated,
then? This scenario (scheduled non-interactive upgrades) is common…
Thanks,
//mirabilos
[ with my m68k buildd maintainer and (ex-?) porter hat ]
Aurelien Jarno dixit:
>- debian-ports uses mini-dak instead of dak. It uses less resources and
> brings some features that are useful for new architectures like
> accepting binary uploads when it "improves" the version even if it is
> no
On Fri, 6 Feb 2015, Dmitry Bogatov wrote:
> know, it is THE console downloading solution.
I thought that was youtube-dl?
Which is also written in Python… I smell the chance to share…
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 5
On Thu, 29 Jan 2015, Clint Byrum wrote:
> Fair enough?
In some cases, the patch to fix the behaviour for some
architectures may-or-may-not-(but-this-has-to-be-proven)
hurt performance or something on other architectures
while retaining correctness. In these cases, always if
the language does not
On Mon, 19 Jan 2015, Wookey wrote:
> Ah yes, and that list has no option for 'maintainer and submitter' or
> 'everybody who replied to this bug' which both seem like things one
That does not help either. By default, people just “reply to list”,
“reply to all” or just “reply”. Too much stuff ends
On Mon, 19 Jan 2015, Thijs Kinkhorst wrote:
> The only seems to suggest this is a minority. I would however argue that
> the majority of other bug tracking systems do subscribe you to bugs you
> interact with.
Such as FusionForge, which runs Debian’s very own Alioth.
I’ve been bitten by this in
On Thu, 15 Jan 2015, Vincent Lefevre wrote:
> I don't even see how it can work. Perhaps you need to explain.
*sigh*…
• Take output of 「apt-cache show texlive-latex-extra」
• Replace all newlines with \x01
• Replace all “\x01\x20” with just a space (0x20)
• Replace all remaining \x01 back to newli
On Wed, 14 Jan 2015, Vincent Lefevre wrote:
> > > which doesn't work at all, neither with zsh nor with bash.
> >
> > It works with mksh, GNU bash, AT&T ksh93, zsh (Debian sid).
> > I don’t see why it shouldn’t work on older versions either.
>
> It didn't work on Debian sid.
WFM. I suggest you t
On Mon, 12 Jan 2015, Vincent Lefevre wrote:
> which doesn't work at all, neither with zsh nor with bash.
It works with mksh, GNU bash, AT&T ksh93, zsh (Debian sid).
I don’t see why it shouldn’t work on older versions either.
> I still want to be able to see the full "Depends:" and so on.
grep-a
On Fri, 9 Jan 2015, Vincent Lefevre wrote:
> > You can pipe the output to "head" or "tail" to sort of achieve what you
> > want to.
>
> Obviously not. It may be possible with something like sed or perl,
> but this may not be future-proof, and breakage due to changes in
Nonsense, the format is tri
On Thu, 4 Dec 2014, Ian Jackson wrote:
> Each time you generate an EE key which you intend to use this way,
[…]
This assumes you can control the server key/cert you want to trust.
> Daniel Kahn Gillmor writes ("Re: curl and certificate verification in
> jessie"):
> > So, the idea is that when y
On Tue, 2 Dec 2014, Brian May wrote:
> > Is it *that* simple? I'm surprised by the "interest" thing just being
Yes.
> There might be times when compress is run twice. e.g. when
It does, yes. I wonder about that too. Can a package trigger itself?
> (e.g. you could explicitly raise the trigger
On Mon, 1 Dec 2014, Cyril Brulebois wrote:
> > Could you please add support for the Tanglu[1] Debian derivative?
> Without having looked at it yet: thanks.
> Yes, please. One bug report per feature is the best way.
I thought d-i was frozen and debootstrap was to absolutely
not be touched any mo
On Mon, 1 Dec 2014, Jérémy Lal wrote:
> Instead of triggers, i'd rather make sure the web application package is
> rebuilt whenever one of its Build-Depends package is updated.
No, that’s too fragile and ties up way too many resources.
It’s fully OK to compose the final version on the users’
syst
On Sat, 29 Nov 2014, Axel Wagner wrote:
[…]
> Axel Wagner
*plonk*
Congrats, you’re the second person, after Josselin.
(No, this eMail was not the only one, just the one to trigger overflow.)
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Tro
On Sat, 29 Nov 2014, Svante Signell wrote:
> The best for kFreeBSD and Hurd would be to abandoning the Debian ship.
No.
> It is sinking
It has sunk, but not gone underwater yet completely.
> (just let the devuan people get things in order first)
And can you *please* *stop* the devuan trolling
On Fri, 28 Nov 2014, Philipp Kern wrote:
> On Fri, Nov 28, 2014 at 04:40:50PM +0100, Thorsten Glaser wrote:
> > Hey, there are *still* bugs found because of s390 (not s390x).
>
> Uhm. s390x is 64bit BE; ppc64 and sparc64 never made it into the archive.
Sure, but I was thinking
On Sat, 29 Nov 2014, Thomas Goirand wrote:
> 2/ in debian/openstack-dashboard.postinst, implement something like:
>
> if [ "$1" = "triggered" ] ; then
> /usr/share/openstack-dashboard/manage.py compress --force
> fi
>
> Is it *that* simple?
No, triggers unfortunately are not that simple:
On Fri, 28 Nov 2014, Svante Signell wrote:
> > Github? Ugh! http://mako.cc/copyrighteous/free-software-needs-free-tools
> This has just started, give them some time, please.
No. If they even consider things like this, there is something
seriously wrong right in the beginning.
> Maybe it would b
On Fri, 28 Nov 2014, Stephan Seitz wrote:
> On Fri, Nov 28, 2014 at 04:00:42PM +0100, Thorsten Glaser wrote:
> > On Fri, 28 Nov 2014, Stephan Seitz wrote:
> > > Of course not. syslog-ng was not replaced by rsyslog when Debian changed
> > > the default syslog.
> >
On Fri, 28 Nov 2014, Stephan Seitz wrote:
> Of course not. syslog-ng was not replaced by rsyslog when Debian changed the
> default syslog.
Note that syslog-ng was not the default, but sysklogd (which was)
wasn’t replaced either. Thankfully.
> The grub1 bootloader was not replaced when Debian cha
On Fri, 28 Nov 2014, Ansgar Burchardt wrote:
> No, the ctte did not say that. We had a flamewar about that
> interpretation before.
That was almost word by word from
https://lists.debian.org/debian-devel-announce/2014/11/msg0.html
bye,
//mirabilos
--
>> Why don't you use JavaScript? I also
On Fri, 28 Nov 2014, Marco d'Itri wrote:
> On Nov 28, Svante Signell wrote:
>
> > a) Upgrades should _not_ change init: whatever is installed should be
> > kept.
> I disagree: upgrades should get the default init system unless the
> system administrator chooses otherwise.
I disagree with you,
On Fri, 28 Nov 2014, Svante Signell wrote:
> It will be interesting to see how many Debian Maintainers and Developers
> will jump the ship and join them (in addition to the users). Future will
I’ll tell you in the present.
Github? Ugh! http://mako.cc/copyrighteous/free-software-needs-free-tools
On Fri, 28 Nov 2014, Thomas Goirand wrote:
> It's been a long time I've been thinking about it, and I believe that
> the only way to do this, would be to use triggers. Though I have never
Look at libjs-protoaculous which combines prototype and
scriptaculous into one (possibly minified) js file. I
On Fri, 28 Nov 2014, Svante Signell wrote:
> the order of pre-depends for int init package should change from
> Pre-Depends: systemd-sysv | sysvinit-core | upstart
> to
> Pre-Depends: sysvinit-core | systemd-sysv | upstart
That would probably require changes in d-i to ensure that
systemd is, inde
On Thu, 27 Nov 2014, Edmund Grimley Evans wrote:
> of which could be expressed more concisely. (Are all Debian
> architectures ILP32 or LP64? Any rare exceptions could be described in
I think so. Probably even all Linux architectures?
> 4. I'd like to see some information about va_list added as
On Tue, 25 Nov 2014, Svante Signell wrote:
> (another partial? solution is to change order of the (pre-)depends of
> the init package, as proposed in
No, that breaks due to the bug in debootstrap’s dependency “resolver”
(see #557322, #668001, #768062) and the unwillingness of KiBi to fix
that. Th
Matthias Urlichs urlichs.de> writes:
> Care to tell us why? Other than "ugh, it's written by Lennart"??
The “why” does not matter. Users do not have to justify why they
need to use something. I worked in for company that had a strict
“no PHP” policy once. I have encountered other more or less we
On Fri, 21 Nov 2014, Simon McVittie wrote:
> failing to start up on armel due to unaligned memory accesses. lzo2 has
> a cpp macro, LZO_CFG_NO_UNALIGNED which can be defined to stop it doing
> "clever" things with casting pointers. If the maintainer doesn't object
Please define this macro uncondi
On Wed, 19 Nov 2014, Michal Suchanek wrote:
> >> Release: testing
> I had Ubuntu base system on this particular PC some years ago and I
Hah! I’m not the only one then ☺
bye,
//mirabilos
--
[16:04:33] bkix: "veni vidi violini"
[16:04:45] bkix: "ich kam, sah und vergeigte"...
--
To UNSUBS
On Tue, 18 Nov 2014, Helmut Grohne wrote:
> From this little exercise, it seems that it is not well understood in
> what way services should be signalled after log rotation. In particular,
> it seems to me that service and invoke-rc.d should not be both valid. So
I’ve experimented a bit with this
On Tue, 18 Nov 2014, Daniel Pocock wrote:
> That is not a Git-specific issue, it is a general issue with source-only
> uploads. If source-only uploads become the norm then signed tags should
> be the same as source packages shouldn't they?
Absolutely not! (Hint: .orig.tar.gz, often several. And
On Fri, 14 Nov 2014, Ralf Jung wrote:
> I was specifically talking about interfaces (as in, dbus signatures),
Meh… I don’t even have dbus installed at home. (It is, on the work
system, due to… virt-manager and iceweasel(?).)
> > So, no need for anything systemd-ish.
>
> Well, even better for yo
On Fri, 14 Nov 2014, Ian Jackson wrote:
> expect to find version numbers matching ^\d+\~, then anything matching
These are common enough for me to have not only seen,
but also used (in native packages, of course) them.
(But: Yes, epochs should belong into filenames, except
for filesystem naming
On Fri, 14 Nov 2014, Ralf Jung wrote:
> Really, if all the energy that people put into complaining about systemd
> and looking for proves to back their complaints (many of which are
> certainly valid!) would be put into providing alternative
> implementations of these interfaces that many desktop
On Thu, 13 Nov 2014, Ralf Jung wrote:
> How does having yet another NTP client shut off existing NTP clients?
https://github.com/systemd/systemd/commit/7b8b9686e050a2b19ed2a3686af187dffaab5c08
This is like MSDNAA: give away stuff for free (support xntpd¹)
to get people used to the drug (systemd)
On Fri, 7 Nov 2014, Ralf Treinen wrote:
> architecture-specific. The issue of architecture=all packages that
> are not installable on some architecture can IMHO not be solved with
> our current setup which makes architectures=all available on every
> architecture.
This is a bug, I’ve seen this a
On Sat, 8 Nov 2014, Stuart Prescott wrote:
> UDD can help with this.
>
> A list of source packages that have M-A: same binary packages in jessie that
> have different versions in any two release architectures is at:
Can we do this for the triplet (i386, amd64, x32) too, please?
Yes, it’s not a
On Fri, 7 Nov 2014, Adam Borowski wrote:
> You can chroot to the system from the host machine, and upgrade to sysvinit.
> If your host can't run arm code, install qemu-user-static and copy
> /usr/bin/qemu-arm-static to the target system.
This is no fix. There are systems Qemu does not emulate.
de
On Mon, 3 Nov 2014, Bernhard R. Link wrote:
> different as with other NMUs? Where is the difference to
Thanks, you described this better than I could.
bye,
//mirabilos
--
15:41⎜ Somebody write a testsuite for helloworld :-)
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
wit
On Sun, 2 Nov 2014, Steve Langasek wrote:
> it in /usr/lib instead of /usr/lib/$arch. But this also seems like a
> low-priority FHS issue to me. Is there a practical reason that we should
Low-priority sounds about right, but there’s still the supposed
case of /usr/share sharing across architect
Ian Jackson dixit:
[ NMU ]
>A dgit user should be able to do this without reading the debdiff:
This is a dangerous habit to get into – I’d prefer users of even
dgit, no matter how good it may be, to not rely on that. This is
a social issue, not a technical one.
bye,
//mirabilos
--
„Cool, /usr/s
On Wed, 29 Oct 2014, Ian Jackson wrote:
> maintainers of other tools. It does seem to me to imply that using
> git-buildpackage to do an NMU is risky, because:
Yes, it is – anything other than the standard Debian tool
(dpkg-buildpackage) is.
> If some user of git-buildpackage (without dgit) tri
On Sun, 26 Oct 2014, Pau Garcia i Quiles wrote:
> "Do you want to enable an external repository which will provide you with
> the latest version of Wt?
How are you going to provide, say, S/390 binaries? ☺
What about distribution integration and bugtracking?
> Is this acceptable? Has anyone ever
(Bcc bugreport, as some new information has come up, I think.)
Hi everyone,
some gir-* packages install their typelib files into multiarch paths
since recently, which requires gobject-introspection of a version
newer than what’s in stable.
There’s a bugreport related to this (#766644) in which t
Gregory Smith dixit:
>They say you're a hard nose, skeptical, untrusting, old unix admin and
>programmer from the old days and you do not take one ounce of
My old days were on DOS¹. I am a relative newcomer to the Unix world,
starting about 1999. But I grew up with the “old values”, including
the
On Wed, 22 Oct 2014, Henrique de Moraes Holschuh wrote:
> The problem is that Debian is the operating system distributing the system
> libraries, and that all packages Debian distributes are *also* part of that
> same operating system.
Wrong: “*as long as*
your GPL binary is not shipped together
Jelmer Vernooij dixit:
>Samba is unlikely to add such an exception.
So just make OpenSSL a system library finally.
bye,
//mirabilos
--
(gnutls can also be used, but if you are compiling lynx for your own use,
there is no reason to consider using that package)
-- Thomas E. Dickey on the
On Tue, 21 Oct 2014, Axel Wagner wrote:
> systemd in debian is: That the systemd-opponents want to take the
> freedom from other people (amongst other the gnome upstream and debian
^^^
> maintainers) to use the software they like in the way they like, by
> preventing them from depending on s
Ondřej, could you please stop your aggressive behaviour against other
people on this list? Sadly, you are not very helpful with these remarks.
Repeatedly.
Thanks,
//mirabilos
--
15:41⎜ Somebody write a testsuite for helloworld :-)
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.or
Konstantin Khomoutov dixit:
>Sometimes we have to run software which is neither Open Source nor Free
>on our systems which are (luckily) Open Source and Free.
Things like f-prot are shipped statically linked, when in their
binary form for OpenBSD. And binary compatibility only goes so
far either
On Tue, 21 Oct 2014, Thomas Goirand wrote:
> So, dear fellow DDs, I'm asking you: each time you see that an upstream
> author is breaking an ABI on a package you maintain, write an email to
> him/her, and explain how much this is bad and shouldn't happen. If the
> Unix community starts to realize
On Tue, 21 Oct 2014, Michael Ole Olsen wrote:
> suddenly I couldnt just place a script in rc2.d folder anymore, needed to
> symlink
> needed to add an lsb header too it seems
Indeed.
It took me quite some effort to learn about LSB headers, exit codes,
SYSV init scripts, and all that, in order t
On Mon, 20 Oct 2014, Matthias Urlichs wrote:
> Christoph Biedl:
> > - upstream shows little respect for people who object systemd
>
> Why should they?
Because not doing that is asocial.
> "If you don't want to use my software on general principles, go away and
> write your own. Do not bother m
On Mon, 20 Oct 2014, Osamu Aoki wrote:
> I see. By the way, I have never seen package using Build-Using in
> debian/control which is documented in policy. Is there any automatic
> way to set the used-source:Version of package used? Something like ...
>
> Built-Using: marisa (== ${used-source:Ver
On Mon, 20 Oct 2014, Gerrit Pape wrote:
> time for this is quite limited.
You and me both, unfortunately.
bye,
//mirabilos
--
[16:04:33] bkix: "veni vidi violini"
[16:04:45] bkix: "ich kam, sah und vergeigte"...
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject
On Mon, 20 Oct 2014, Gerrit Pape wrote:
> See #766048, I rate the results as ciritical issues ;), and so won't
I’ve glanced at the list referenced.
Some things that immediately come to mind:
autoconf2.64 2.64-3 Failed [CONFIGURE_ERROR] configure: error: no acceptable m4
could be found in $PATH
On Sun, 19 Oct 2014, Sune Vuorela wrote:
> Eigen.
Yes, that was it. Thanks.
OK, we have some examples, I hope this helps the OP ;-)
bye,
//mirabilos
--
Sometimes they [people] care too much: pretty printers [and syntax highligh-
ting, d.A.] mechanically produce pretty output that accentuates i
On Sun, 19 Oct 2014, Osamu Aoki wrote:
> This is about packaging around a header only C++ library package.
IIRC, we already have one in the archive. I vaguely recall it
from m68k porter work, but can’t remember the name. Something
mathematical, I think?
bye,
//mirabilos
--
15:41⎜ Somebody write
On Fri, 17 Oct 2014, Jonas Smedegaard wrote:
> If package is suitable for unstable but not for testing, please upload
> to unstable and file severe bugreport to keep it from entering testing.
I thought so too, but learned that this is a bad idea.
Sometimes, you have to update the package in test
On Thu, 16 Oct 2014, Ian Jackson wrote:
> | If one of the members of the tech ctte considers that we should
> | either overwrite the udev-maintainer or move printf to /bin, we
The coreutils maintainer may still decide to do just that.
That’s what would help the most.
bye,
//mirabilos
--
Yes,
On Thu, 16 Oct 2014, Jonathan Dowland wrote:
> > > But it’s now resolved, thanks Philipp!
> >
> > Wrong again, I dist-upgraded the chroots and gave back the package.
> > But as before, facts are difficult.
>
> Likewise, you could have pointed this out without being quite so condecending.
Uhm ye
On Wed, 15 Oct 2014, Christoph Anton Mitterer wrote:
> I see it a bit differently:
> RC4 is broken. Full stop.
> Therefore new versions clients and servers should per default not
> use/enable/accept it.
Sorry, but I *have* to nitpick here.
RC4 as used by SSL is mostly broken. (A server could res
On Wed, 15 Oct 2014, Ian Jackson wrote:
> Actually, the problem is indeed in policy. In its resolution of
> #539158 the TC decided unanimously (but unfortunately slightly
> implicitly) that printf ought to be provided by our /bin/sh.
Somewhat.
> As the maintainer of a minority shell, Thorsten h
On Wed, 15 Oct 2014, Andreas Barth wrote:
> Buildd administration — @buildd.debian.org
> lists a couple of people. And also a working mail address. Contacting
> people via a role account is always prefered.
Yeah, that’s whom I contacted first, on Friday. It was just not
getting any sort of respo
Signed-off-by: Thorsten Glaser
---
library.php | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/library.php b/library.php
index a5a0d8e..43e2c45 100644
--- a/library.php
+++ b/library.php
@@ -1432,7 +1432,7 @@ function html_footer_text($raw=false) {
echo "
Page gene
On Wed, 15 Oct 2014, Cyril Brulebois wrote:
> Thorsten Glaser (2014-10-15):
> > Who are powerpc buildd admins, again?
>
> Still listed at the same location since last time you asked:
Yeah, I tend to forget it.
> https://www.debian.org/intro/organization
Ah wonderful, a s
On Wed, 15 Oct 2014, Stephane Chazelas wrote:
> $ mksh -c 'IFS=; x=abc; printf "<%s>\n" ${x#$*}' x a b | sed -n l
> <\a\300a>$
> $
Interesting… but all shells diverge on this one.
tglase@tglase:~ $ bash -c 'IFS=; x=abc; printf "<%s>\n" ${x#$*}' x a b | sed -n
l
$
tglase@tglase:~ $ dash -c 'IFS=
On Mon, 13 Oct 2014, Joey Hess wrote:
> Only thing I don't understand is why so few votes for systemd-shim out
> of the group who has it installed.
Maybe noatime? That’s probably popular on desktops. “vote” does
not really say much, anyway.
bye,
//mirabilos
--
Sometimes they [people] care too m
On Mon, 13 Oct 2014, Wookey wrote:
> I _think_ we don't do this because the upgrading uses a lot of time on
> buildds, especially slow ones. I did do this (build in snapshot,
Right.
> the same packages over and over until the snapshot was updated (which
> was manual and done approx weekly). This
On Mon, 13 Oct 2014, Stephane Chazelas wrote:
> $*, $@, "$*" were not special in any way. They just underwent
> the same rules as other variables. Only "$@" was.
This changed in POSIX sh though. I remember having
to change some things in mksh to adhere to 2008 and
post-2008.
bye,
//mirabilos
--
Stephane Chazelas dixit:
[ a lot, with which I vehemently disagree ]
>If you need arrays, use "$@" or use "perl/python/ruby...", but
>please don't break yet another shell with the Korn arrays or
>arithmetics.
The good part about mksh i̲s̲ that it’s a programming language,
a nice one to use, much
On Mon, 13 Oct 2014, Neil Williams wrote:
> > (I did not have the chance to Second the GR proposal
> > because I was not even aware that there *was* one.)
>
> https://lists.debian.org/debian-vote/
>
> Same procedure as previous calls for GR: debian-vote mailing list. If
Yeah, surprise, I don’t
On Mon, 13 Oct 2014, Miles Fidelman wrote:
> Those who are most impacted are sys admins of servers, and upstream developers
I’m both, and I joined Debian to try to make an impact…
> - the two communities most impacted, but that seem to have no say in the
> matter.
… but even then, am drowned by
On Mon, 13 Oct 2014, Dominik George wrote:
> foo='x[$(rm -rf /)]'
> echo $(( foo ))
>
> Guess when the array index is evaluated? Now mind that it could be
This is fully and completely a user error. (User being the script.)
> user-provided.
Never put “tainted” input into ksh arithmetics, period
On Sat, 11 Oct 2014, Theodore Ts'o wrote:
> I assume that posh meets the strict definition of 10.4. And so
> without actually changing policy, someone _could_ try setting /bin/sh
> to be /bin/posh, and then start filing RC bugs against packages that
> have scripts that break. Yes?
Yes, modulo
On Mon, 13 Oct 2014, Matthias Urlichs wrote:
> Yes. Human beings are perfectly able to communicate dislike for another
> human's actions in a way that does not imply disrespect for that person.
But Debian beings are not able to distinguish between disrespect
for actions made by some person (while
Hi all,
it still happens, occasionally, that buildd chroots are not
updated, which leads to mksh builds refer old versions of
gcc or some libc (used when linking the mksh-static binary)
in its Built-Using field. The buildd admin gets a REJECT
from dak, because the version is neither in testing (ye
On Tue, 7 Oct 2014, Adam Borowski wrote:
> change your /bin/sh), 2. being (then) a violation of a "must" clause of
> the policy.
To be fair: my bug wasn’t about -a and -o, but about the printf builtin
which Policy is silent about. Some shells do have a builtin printf,
most don’t. printf(1) lives
Forwarding a bit of my answer on this. I don’t know what to
think about how this criticism immediately raises responses
like the two I already got, yet the other person in question
is allowed to disrespect his fellow DDs and just ignore the
fixes for real-world, although minority, problems.
I deli
On Sat, 4 Oct 2014, Russ Allbery wrote:
> >> If we were to decide that #309415 should be fixed in policy (and hence
> >> posh), then it should be done by requiring support for the obsolescent
The problems with posh and dash are also the sheer number of bugs
in corner cases, which the more activel
On Wed, 1 Oct 2014, Russell Stuart wrote:
> The only reason I ported things to dash is /bin/sh is now linked to it,
> which in view makes it the standard shell. Every script starting with
> #!/bin/sh must work with. If I can't get it working because of a
This is wrong. Every script starting wit
On Sun, 28 Sep 2014, Russell Stuart wrote:
> - pipefail,
mksh has “set -o pipefail” and the PIPESTATUS array.
> - local variables,
mksh has them, of course. ksh93 only has them in
functions declared with the “function” keyword,
and lacks a default “alias local=typeset” to make
it useful.
On Fri, 26 Sep 2014, Matthias Urlichs wrote:
> In any case, adding "-p" to any #!/bin/bash shebang line looks like a very
> good idea. Shall we add a Lintian check for this?
***ABSOLUTELY NOT***
The -p option is for the shell to *not* drop privileges when
called setuid.
bye,
//mirabilos
--
Som
On Fri, 26 Sep 2014, Klaus Ethgen wrote:
> > bug in grep, xz-utils or gzip.
> Only against that 3 tools that most likely are also used from network
For what it’s worth, OpenBSD/MirBSD have BSD-licenced
implementations of tools like zgrep, zless, etc. that
can be used (with s/gzip/xz/g) for xz as
On Thu, 25 Sep 2014, shawn wilson wrote:
> In that case, I'd think busybox's sh is *much* more minimalist. Why dash
> over busybox?
There is something called bugs. The busybox implementation
is artificially limited. Also, it uses the busybox common
code, which makes its codebase rather large.
Th
On Wed, 24 Sep 2014, Jakub Wilk wrote:
> > You can easily do this by downloading an email from the bug thread and
> > replying to that.
>
> Luckily, if you do that, there's a great chance that you'll get both a helpful
> Subject and References. :-)
Except if it’s the first mail in the thread, th
101 - 200 of 562 matches
Mail list logo
