On 2025-03-22 16:15 -0700, Otto Kekäläinen wrote:
Thanks for the explanation Wookey on why you prefer to not use VCS for
Debian packaging, and why others using VCS, and thus in Debian Salsa,
creates extra work for you.
Just out of curiosity, what email client and plugins do you use to
. I appreciate their
effort. That does _not_ mean I must intrinsically want said packages
converted to an entirely different workflow. Sorry Otto :-)
Wookey
--
Principal hats: Debian, Wookware
http://wookware.org/
signature.asc
Description: PGP signature
On 2025-03-17 00:03 +0100, Salvo Tomaselli wrote:
Hello,
I am a user of telegram-desktop.
Is anyone else interested in fixing this and able to help?
I'm a weekly user and would very much like it working. I'm a bit short of
tuits, but I'll try and take a look and see if I ca
ould_ just do less of it, that would be
good.
Wookey
--
Principal hats: Debian, Wookware
http://wookware.org/
signature.asc
Description: PGP signature
, as
we do have some notice mechanisms already. But they are old, and
expectations change so it's not crazy to ask if they are still sufficient.
But equally, starting with 'it's your fault' seems unhelpful and
possibly unfair. I look forward to some answers in response to Helmut,
a
nd format=flowed,
This is probably the most useful email in the thread. Cheers.
I have added
set text_flowed
to my mutt
but I think I need to know the equivalent to
au FileType mail setlocal formatoptions+=w
for
emacs particularly, but also zile, jed and mcedit (all of which get used from
tim
On 2025-01-23 18:09 -0800, Otto Kekäläinen wrote:
> Hi,
>
> On Thu, 23 Jan 2025 at 17:52, Wookey wrote:
> ..
> > Right. I look at bug reports for my packages (eventually). I have
> > never looked at a Salsa merge request in my life. That's just
> > /dev/null
package that the maintainer is not
> interested in spending time/effort on accepting contributions,
No - it just indicates that they want people to use the BTS or just
email. Contributions are always very welcome.
Wookey
--
Principal hats: Debian, Wookware
http://wookware.org/
At least if you
> file a bug then there's a good chance somebody will actually be told
> about it.
Right. I look at bug reports for my packages (eventually). I have
never looked at a Salsa merge request in my life. That's just
/dev/null for my packages. That could change one day,
thought --as-needed on its own is sufficicent to avoid dpkg-shlibdeps warnings
about unnecessary linking (because it only links the things that are needed), so
I don't understand the need for the psuh/pop sequence (I must admit that I never
knew that existed until your message recently).
cheer
chive had
> migrated away from `fakeroot`).
>
> 2) A quick fix to `debhelper` to remove the reliance on
> `fakeroot` when assembling `-dbgsym` packages.
A detail, I know, but we take detail-correction seriously round here. :-)
Wookey
--
Principal hats: Debian, Wookwar
t; solution I could and should upload it.
That is indeed a totally reasonable approach.
Wookey
--
Principal hats: Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
onsistent as possible across architectures, and don't just
reach for the 'disable' button. For someone on a particular arch that
is the same as the 'remove from archive' button in effect.
Wookey
--
Principal hats: Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
7;neat' epochless versions forevermore for all those
future users when everyone has forgotten about this cock-up.
Ultimately you are the maintainer so it's up to you.
From what you have said, I think I'd epoch in this case, unless I
thought the current set of users could be considered
erything - even the
packages that were just uploaded as tarballs. And explicitly _doesn't_
remove the archive VCS interface. And it supports all the git-based
workflows. (someone should probably tell IWJ this conversation is
occuring as he's taken a bit intererest in it, but no longer
? Like I say, dgit is so close, but exactly the opposite of
what I need.
> > But let's not try to "fix" a problem by introducing a rule that is, at
> > best, affecting something only very weakly related to the problem that
> > we are trying to solve.
>
> I would be happy to talk about rules that might help solving problems
> (as well as droping rules that are creating barriers).
Me too. Please let us improve the culture around NMUs, collaboration and fixes
without making people (OK, duffers like me) change all their tooling.
I am all for more Matrix over IRC though - that's a genuine
improvement (and they are easy to bridge).
Wookey
--
Principal hats: Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
failed to make any progress despite reading wiki pages and
man pages and blogs. I just realised that I didn't understand how it
worked or what the tradeoffs were, so couldn't really make sensible
decisions about what I should do. I suspect I'm not the only one who
is quite vague
depend of curl are not building on armel/armhf.
We are well aware that this is broken and blocking lots of
things. Co-ordinate efforts on the #debian-arm channel.
There are plenty of other loops to unbung too.
Wookey
--
Principal hats: Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
oups/distros/softwares
are following fuse development more closely and thus have already got
'wrong' binaries.
A soname bump is probably your best bet, but if no-one even noticed
this for a year then maybe it's not that bad and just reverting will
suffice? (And send everyon
stable ABI/dynamic linking problem.
I guess it might be time for another go to see if we can get some traction.
Wookey
--
Principal hats: Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
on't support anything like as many
architectures.
If it only done for security issues, rather than routinely, then that
shouldn't be that much extra load (does anyone have any idea how much
extra building we are talking about? Is it trivial, or huge?)
Wookey
--
Principal hats: Debia
On 2023-11-24 18:58 +, Thorsten Glaser wrote:
> Unfortunately, eller is down
Eller had to move hosting provider at short notice. It is now racked
again but needs network configuration for new location. It will
hopefully re-appear by end-Monday.
Wookey
--
Principal hats: Debian, Wookw
are just told to 'use the right one' will do so,
and I thought it worth pointing out that that's not correct). Info for
your average maintainer needs to go one step back and say "use stringA
in this circumstance and stringB in this circumstance. . The reason why it matter
it
(and it's kind of annoying because it interrupts the install/upgrade
process). And this only works for well-maintained packages that
actually update Debian.NEWS, not barely-maintained/unmaintained
packages. I guess you might get the info from the replacing, as
opposed to replaced package,
correct binary builds (although I do think it should clean enough to
make correct sources too in general).
Wookey
--
Principal hats: Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
#x27;t really exist.
It does exist. It's broken far too often and it affects actual
developers using debian tools. It's supposed to work.
Wookey
--
Principal hats: Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
workflows) everything 'just
works'. So it's easy to justify in terms of maintenance effort IMHO.
The only maintenance load comes if/when upstream move things around.
I have never tried Helmut's suggestion of removing this stuff in the
clean target. It does seem to me that removing it from the tarball
makes a lot more sense than cleaning it later.
Wookey
--
Principal hats: Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
lt reliably from git/VCS - the old debian stuff is
bust'. Better would be a new git-only dpkg format of some sort with a
new set of expectations. But that's quite a big piece of work.
Just to be clear I don't want any of that. I want the existing tooling
and packaging to work the way p
bringing up because whilst the existing
'i386' arch has to choose one ABI or another, nothing stops us from
having both variants in the archive if we want them enough.
Wookey
--
Principal hats: Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
of issues and options. It is much appreciated.
I agree with the two consensus proposals Helmut put in the email at
the top of this thread (that DEP17 is a good representation of the
issues and that putting the files in the canonical locations is the
long-term endpoint of this transition).
Wook
; > mind before applying it?
>
> Note that I'm not the one driving this change (I'll start a separate
> thread for -fstack-clash-protection in the next days), but the original
> request was from Wookey.
> Personally I think now at the beginning of the new development
pendent of the 'should the i386 ABI
switch along with other 32-bit ABIs'.
Switching or not (so long as the fairly small subset of the distro we
use keeps working) would not affect our usage of the device, for example.
So if we could try and consider these questions separately, that would
le/fix it for
everything though. A rebuild check of affected libraries to see how
much work this adds would be a good idea.
I'll add this info the the wiki and do some tests.
Wookey
--
Principal hats: Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
open router hardware that can actually run the fancy
scriptage/setup needed then everything can be in one box, but not this
year).
Removing the installer to stop supporting _new_ installs is probably
fair enough but I don't think we can yet say there are no reasonable
use cases for old i386 h
be great if you could add relevant info to the wiki page:
https://wiki.debian.org/ReleaseGoals/64bit-time#Known_Issues
Similarly, if anyone else knows of actual or potential issues, that
page would be a great place to document them, or add tests we can run
to check things are still working as expected.
27; (a workaround) is to make any packages which appear as the
arch-all intermediaries in dep-chains to be made arch-any so that
chain is not broken. We can either do that for all packages in an
ecosystem, or just for ones that actually exhibit this problem. Doing
it for all is safer.
HTH
Wookey
--
Principal hats: Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
oaded our buildds. Such a thing
may be more tractable these days in terms of available build resources
on most arches, but it's still a very big deal, and this change
certainly doesn't warrant it.
Wookey
--
Principal hats: Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
On 2022-10-25 16:10 +0100, Simon McVittie wrote:
> On Tue, 25 Oct 2022 at 15:34:26 +0100, Wookey wrote:
> > These are hardware features (new instructions) that 'tag' pointers and
> > branch targets to make it much harder for malicious code to implement
> > ROP (retur
t it is changing the defaults.
Like all dpkg-buildflags it can easily be disabled for a particular
package and there is a kernel option to turn it off on a particular
machine if issues are encountered (and no doubt we will find a couple).
I hope that all makes sense.
Wookey
--
Principal hat
> a per-architecture symlinks in arch-specific packages.
I would like to understand how the cross stuff works with this
personalities thing, but it may be a while before I get round to
it. Again I shall assume that you know what you are doing :-)
If Helmut is happy then I'm sure it'
rework IMHO to get rid
of this very unhelpful (and not at all necessary) characteristic. I
did consider doing the work needed to fix this but didn't have the
bandwidth/enthusiasm at the time. Maybe someone has fixed this in the
nearly a decade since I looked in to it and the point is moot? B
a bit (away from AI, towards core arch activities and my
personal packages). I'm not sure how much of my current test hardware
I'll get to keep...
I am a DD (since 2000)
Wookey
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
great. Having the
store and-forward done by someone else (unless you want to still do it
yourself) is nice.
Wookey
--
Principal hats: Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
ial packages, but not not very useful for trivial ones.
Wookey
--
Principal hats: Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
er path in debian
has been /var/www/html/ for decades so I'd use that, but you might
have reasons to make it /var/www/shiny-server instead if you want
shiny-server to be co-installable with other web-servers, and serve different
stuff?
Wookey
--
Principal hats: Debian, Wookware, ARM
http:
Package: wnpp
Severity: wishlist
Owner: Wookey
Package name: libbacktrace
Version : 1.0
Upstream Author : Ian Lance Taylor
URL : https://github.com/ianlancetaylor/libbacktrace
License : BSD
Programming Lang: C
Description : Backtrace library
Package: wnpp
Severity: wishlist
Owner: Wookey
* Package name: rang
Version : 3.2
Upstream Author : Abhinav Gauniyal
* URL : https://github.com/agauniyal/rang
* License : The Unlicense
Programming Lang: C++
Description : c++ terminal colour library
ve debian package'?
I thought the whole point of debian native packages was that there was
no 'upstream' and it was only for debian so you _are_ in control of
the source, the versioning and the releases? As soon as that stops
being true then should one not shift to making it a
Linux-drops-Windows-Red-Hat-into-airlock
Or at least was in 2013/4.
Wookey
--
Principal hats: Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
singly anachronistic as the rest of the software ecosystem seems
to accelerate around us (not entirely a good thing, of course). Who
needs quality when you can have updates, eh?
The combination of binary uploads for NEW and source-only uploads for
the archive proper also seems a tad clunky.
Woo
Package: wnpp
Severity: wishlist
Owner: Wookey
* Package name: ebusd
Version : 21.3
Upstream Author : John Baier
* URL : https://ebusd.eu/
* License : GPL3 or later
Programming Lang: C++
Description : Daemon for handling communication with eBUS
though as people have pointed out
complete rewrites are not really NMU material and we should follow the
salvage process.
Well done for getting those boring old packages into better shape (again).
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
e (or even
properly know what they are) to my collection of responsibilities, but
I can spend work time on helping get this going so I don't mind
mucking in on some packaging work.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
t stands,
if you don't already know, it tells you nothing more than 'this
program does analysis of data', which is a little too general.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
not) and
> let it stay there until wxWidgets 3.2 is out?
Yes. This is what I'd do for the time being. That way you are not
committed to this path where you might end up maintaining (or not
maintaining, just hoping for the best on!) an unstable wxwidgets
version for several years.
Wookey
On 2021-09-20 04:48 +, Clint Adams wrote:
> On Sun, Sep 19, 2021 at 05:32:04PM +0100, Wookey wrote:
> > I must admit that I have no idea why replacing such a longstanding
> > utility is deemed necessary.
>
> Maybe this riddle will help.
>
> Imagine that you
recommended.
Have a plain which back is much easier than fixing the build mess.
I must admit that I have no idea why replacing such a longstanding
utility is deemed necessary.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
mention the 'B' dependency), let that build, then upload B and (once
built OK) upload a full A.
Sometimes people use 'foo-bootstrap' package names so that the
minimal and full versions of a package can be distinguished.
HTH
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
On 2021-08-11 14:08 +0200, Hans wrote:
> And best: It is all GPL licensed,
It's all free software, but many licences are used, not just the GPL.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
ng is to update xfce-notes-plugin to use it?
Assuming that's not too difficult I don't mind doing some work to get
it back in a ship-able state.
Or it there something else that is still around that does the same job
as the notes plugin? It's quite unusual in the way it wo
lease version is a
significant feature for a platform like theirs, and it wouldn't be
hard to keep the old URLs working for a couple of years to allow a
smooth switch to a specified long-term interface.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
D
On 2021-02-18 16:00 -0300, Henrique de Moraes Holschuh wrote:
> Wookey,
>
> > Description : Enhanced Qfuture (Qt) interface
> >
> > AsyncFuture is designed to enhance the QFuture function, removing..
>
> Maybe this should be prefixed with qt- since i
Package: wnpp
Severity: wishlist
Owner: Wookey
* Package name: asyncfuture
Version : 0~0.1
Upstream Author : Ben Lau, Philip Schuchardt
* URL : https://github.com/vpicaver/asyncfuture
* License : Apache2
Programming Lang: C++
Description : Enhanced
Package: wnpp
Severity: wishlist
Owner: Wookey
* Package name: qt-qml-models
Version : 0~0.1
Upstream Author : Philip Schuchardt
* URL : https://github.com/Cavewhere/qt-qml-models
* License : Custom WTFPL-style
Programming Lang: C++
Description
emergency x86 box has been stuffed in until I work out what's wrong
with it/replace it.
> * Are you testing/patching d-i for the port(s)?
Yes. Added multiple console support for last release.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
case can
someone reply so they are in the bug report. Cheers.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
roof level, unless an impressive
level of enthusiasm is collected and applied.
I have just set up a small server yesterday in order to experiment with this
stuff (setting up matrix-synapse initially, but jangouts and BBB are also of
interest, although neither are packaged).
So yes, kno
investigation and work is needed to progress
that. One outcome of the meeting was to reject all the pending
packages as new uploads will be needed whatever path is eventually
chosen.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
On 2020-08-19 07:47 +0200, Geert Stappers wrote:
>
>
> Please, pretty please, make `debcheckout ` possible
'dgit checkout ' is possible.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
uploaded within say 4 weeks. If NEW takes longer than that,
then upload the new-version-with-bundle at that point.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
On 2020-05-20 13:42 +0200, Gard Spreemann wrote:
>
> Wookey writes:
> Is there any community consensus on putting the bundling in place
> temporarily while the separate package is held up in NEW? Being the
> maintainer of both, I would be able to quickly react to the separate
&
#x27;d
just package it. A headers-only library is relatively quick and easy to do.
> I
> would track the bundling as a bug and act on it when/if a separate
> package enters Debian.
Would you necessarily notice when another package using this
dependency enters the archive?
Wookey
--
Principa
logins these days.
Debian is one place that has a reasonably competent userbase - I
remain unconvinced that we need to change things.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
should go to
debian, not upstream, although of course not many people read docs so
that won't work as well as one might like.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
7;m not (yet)
convinced by the argument that we shouldn't try at all in this case.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
I'd like it even more if we always had zile.
Just a thought (I'm _really_ not trying to start a vi/emacs argument,
but perhaps it is inevitable). If you've never heard of it, I suggest
you give it a try. v. handy.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
es of course take more time and work then
just stuffing yet another embedded 3rd party library into the source.
Ideally upstreams would be doing this work, but many leave it to
distros to tidy up their mess (and incorporate their laziness into
build systems which just adds more bodging to undo).
W
Package: wnpp
Severity: wishlist
Owner: Wookey
* Package name: armnn
Version : 19.11
Upstream Author : ARM Ltd
* URL : https://github.com/ARM-software/armnn
* License : MIT
Programming Lang: C++
Description : Arm NN is an inference engine for CPUs
Package: wnpp
Severity: wishlist
Owner: Wookey
* Package name: tvm
Version : 0.6.0
Upstream Author : Apache tvm incubator project
* URL : https://tvm.apache.org/
* License : Apache 2.0
Programming Lang: C++, (with go, java, python, rust parts)
Description
the
results, particularly from the POV of someone who has primarily
'patches, quilt and tarballs' workflows, but can use git if
necessary.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
which is apparently the new thing. Nor firewalld - perhaps it
would do what I want?
For those too young to know, ipmasq basically does(did - removed in
2009!) what the script on this page does for you:
https://debian-administration.org/article/23/Setting_up_a_simple_Debian_gateway
Woo
nsible
for modern screens.
Most of the rest of what said sounded fairly sensible to me too,
although I'm not familiar with all the details (and have never noticed a
need for a dark theme). Nicer defaults for screenspace and fonts
definitely sounds like a good idea. You probably need to pe
Package: wnpp
Severity: wishlist
Owner: Wookey
Package name: energy2d
Version : 3.0.2
Upstream Author : Charlie Xie
URL : https://github.com/charxie/energy2d
License : LGPL 3.0
Programming Lang: Java
Description : Interactive 2D heat transfer
Package: wnpp
Severity: wishlist
Owner: Wookey
* Package name: samskivert
Version : 1.9
Upstream Author : Michael Bayne
* URL : https://github.com/samskivert/samskivert
* License : LGPL 2.1 or later
Programming Lang: Java
Description : Utility library
oning scheme (increasingly common in my
experience), it's smart to use 0~$date so you can look smug and switch
to (newer) versions if/when they adopt them without needed an epoch.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
ed) and making the
deb nearly twice as big (540K vs 300K). This does seem pretty
ridiculous.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
Package: wnpp
Severity: wishlist
Owner: Wookey
* Package name: plotsauce
Version : 0.1
Upstream Author : Philip Schuchardt
* URL : https://github.com/vpicaver/plotsauce
* License : GPL2 or later
Programming Lang: C++
Description : Survex 3d file to
pstream and the DFSG is normally defined by
'Files-Excluded' in the copyright file and compression/name
transformations in the watch file. It is for my packages, anyway.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
Package: wnpp
Severity: wishlist
Owner: Wookey
* Package name: qmath3d
Version : 1.0
Upstream Author : Digia/Philip Schuchardt
* URL : https://github.com/vpicaver/QMath3d
* License : GPL or LGPL
Programming Lang: C++
Description : Useful 3dmaths
available.
I think it's worth investing some effort in determining how practical
these routes are, and the above is something I think is within my
capabilities. I'm not overflowing with tuits, but I do think this is
important so I'm prepared to spend some cycles on it.
Wookey
--
On 2018-11-23 23:10 -0300, Lisandro Damián Nicanor Pérez Meyer wrote:
> El viernes, 23 de noviembre de 2018 12:26:49 -03 Wookey escribió:
> >
> > My main desktop is now an arm64 machine with an nvidia PCI graphics
> > card. These are fairly new (and currently expensive), but
Package: wnpp
Severity: wishlist
Owner: Wookey
* Package name: djangorestframework-filters
Version : 0.10.2.post0
Upstream Author : Philip Neustrom
* URL : https://github.com/philipn/django-rest-framework-filters
* License : Expat
Programming Lang: Python
to switch between GL and
GLES). Possibly that work never actually got done, just talked out.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
s, if there are some, like adding updated copyright information. This
> way you also have a place to discuss the issue.
This seems sensible to me.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
years?
Yes a yearly ping is not a big deal, but multiplied by the number of
organisations one is a member of, such annual makework is quite
tiresome, and years go surprisingly quickly once you are over about
35. A bit less often than that will be better IMHO.
Wookey
--
Principal hats: Linaro, Deb
moment.
So yeah, some clarification in order I think, and an explanation of use-cases.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
On 2018-07-22 13:14 -0400, Geoffrey Thomas wrote:
> On Sun, 22 Jul 2018, Wookey wrote:
>
> > I think they're funny, which I think is what was intended by
> > upstream. I enjoy a gratuitous boob-or-handjob mention as much as the
> > next 14 year old.
>
> As
on much beyond the benefits of free software, and
providing useful software in Debian is a good thing for all our
downstreams to choose from.
So yes, I'd leave it in, whilst encouraging upstream to reduce the
laddishness, because that is offputting for quite a lot of people, and
is just no l
it is a real issue for people setting up
their own CI infra. One day I may have the tuits to improve things in
this area (I plan to start retiring soon, which might help, or may
simply introduce different distractions :-)
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
On 2018-04-17 12:27 -0700, Steve Langasek wrote:
> On Tue, Apr 17, 2018 at 12:49:36PM +0100, Wookey wrote:
> > On 2018-04-17 13:15 +0800, Rolf Leggewie wrote:
>
> > > the ticket now does
> > > serve a purpose in documenting publicly why there was no upload to
>
1 - 100 of 407 matches
Mail list logo
