On Mon, Jan 01, 2018 at 05:26:35PM +, Sean Whitton wrote:
> IMO the point of the field is to ensure that you /don't/ have to upgrade
> to the latest version of Policy right away. It allows you to keep track
> of the version of Policy you are up-to-date with, so you can do it
> later/someone mo
On Tue, Jan 02, 2018 at 08:29:00AM +, Niels Thykier wrote:
> > If S-V is declaring that the package conforms to some older version of the
> > policy then all the tools should check that package against that policy
> > and not against the latest one.
> >
>
> Lintian's architecture does not len
On Tue, Jan 02, 2018 at 04:25:07PM -0800, Steve Langasek wrote:
> > If S-V is declaring that the package conforms to some older version of the
> > policy then all the tools should check that package against that policy
> > and not against the latest one.
>
> No, they should not. S-V is a declarat
On Wed, Jan 03, 2018 at 12:16:57PM +0100, W. Martin Borgert wrote:
> > Same here. IMO warnings about the last two policy versions should only be
> > shown in pedantic mode. If a package is 3 versions behind, then this
> > should be a normal lintian warning.
>
> Maybe warn about new minor number, b
On Wed, Jan 03, 2018 at 09:46:59AM -0500, Roberto C. Sánchez wrote:
> > > Do we really need systemd-less builds? I'm not convinced this is
> > > something relevant to Debian.
> > Not at all.
> > This would be a lot of work for the benefit of a tiny audience: the
> > disturbed people who hate syste
On Wed, Jan 03, 2018 at 03:40:06PM +0100, Attila Kinali wrote:
> And insults like this is why a lot of people stopped discussing
> anything with systemd zealots.
So win-win?
--
WBR, wRAR
signature.asc
Description: PGP signature
On Wed, Jan 03, 2018 at 10:21:59PM +0100, Markus Koschany wrote:
> Somehow other distributions like Fedora, Gentoo or
> even FreeBSD can exist without the S-V field to describe their packages.
They can also exist without d/copyright (which is also closer to the
original thread :) ).
--
WBR, wRAR
On Tue, Jan 09, 2018 at 10:31:53PM +0900, Norbert Preining wrote:
> Hi all,
>
> (please Cc)
>
> it seems that msgfmt has problems when run in a C locale, because what
> is produced is not utf8 parsable.
>
> For calibre I need proper utf8 stuff, but I don't see a way to enforce
> an utf8 locale d
On Tue, Jan 09, 2018 at 11:52:47PM +0900, Norbert Preining wrote:
> > No, C.UTF-8 is guaranteed to be available in Debian.
>
> Thanks, good to know - I couldn't find it/set it up, but this is
> probably my very old chroot.
It's avaiable only since libc-bin 2.13-1 (so since wheezy I think).
--
WB
On Fri, Jan 26, 2018 at 09:42:05AM +0100, Philipp Hahn wrote:
> we (Univention GmbH) rebuild packages (from Debian-Jessie or newer)
> using "-j8".
Is that a dpkg-buildpackage option? It's documented to fail on certain
packages, you need to use -J instead, and maintainers need to certify that
a pack
On Fri, Jan 26, 2018 at 07:02:52AM -0500, Roberto C. Sánchez wrote:
> That is interesting. I build using gbp/cowbuilder and so I set these
> environment variables:
>
> DEB_BUILD_OPTIONS="parallel=`nproc`" DH_VERBOSE=1
>
> I was not previously aware of the distinction between -j and -J for
> dpkg
On Fri, Jan 26, 2018 at 03:07:25PM +0100, Adam Borowski wrote:
> So this is _already_ done; at most individual packages might not use this
> option, either via an explicit opt-out, or by having old crufty packaging.
I wonder what percent of the packages has compat < 10.
--
WBR, wRAR
signature.a
On Wed, Jan 31, 2018 at 07:35:32AM +0100, Philipp Hahn wrote:
> Using parallel build (-jX) fails for us, so it takes ~13h to compile
> that gcc. I was told to use '-J' instead, but that is not supported by
> dpkg-buildpackage in Debian-Stretch :-(
You can always use DEB_BUILD_OPTIONS=parallel=n ins
On Wed, Jan 31, 2018 at 02:41:15PM +0100, Guillem Jover wrote:
> But if -jN breaks, that's because the package is not parallel build
> safe, so using -J will not improve things, as the package has not
> opted in (or has opted out depending on the debhelper used) from
> parallel builds anyway.
The g
On Fri, Feb 09, 2018 at 06:58:49PM +0100, Philipp Kern wrote:
> If Ubuntu uses an epoch without Debian following that decision, they can
> never sync with Debian again, increasing the maintenance burden
> indefinitely.
See e.g. libpulse0 (pulseaudio), sadly (I needed to repack a $job package
and f
On Wed, Feb 14, 2018 at 01:57:16PM +0100, Vincent Bernat wrote:
> It's not only an infrastructure problem. If you Depends on X (>= 1.8),
> this will be true with X 1:1.6 as well.
Or with 1.8+really1.6.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Wed, Feb 14, 2018 at 04:29:20PM +0100, Michael Biebl wrote:
> >> It's not only an infrastructure problem. If you Depends on X (>= 1.8),
> >> this will be true with X 1:1.6 as well.
> > Or with 1.8+really1.6.
>
> But this problem will fix itself (after a release cycle at most).
Hmm, why after a
On Thu, Feb 15, 2018 at 09:00:28AM -0600, Pavlo Solntsev wrote:
> I am very excited to see that Debian has moved to GitLab (
> https://salsa.debian.org). With this change, I am wondering how bug report
> process should look like?
I don't think anything has changed.
> Now, I want to submit patche
Recently on Planet: https://apebox.org/wordpress/linux/1229
--
WBR, wRAR
signature.asc
Description: PGP signature
On Fri, Feb 16, 2018 at 07:26:35PM +0100, Innocent De Marchi wrote:
> I believe that the right way is to
> convince developers of the need to generate applications that respect
> the principles of free code.
Note that we don't want "applications that respect the principles of free
code", we specifi
Hi there!
Good news for all interested in hardware compatibility and reliability.
I've started a new project to estimate reliability of hard drives and SSD in
real-life conditions based on the SMART data reports collected by Linux users
in the Linux-Hardware.org database since 2014. The initial
On Sun, Mar 04, 2018 at 11:16:29PM +0100, Thomas Goirand wrote:
> P.S: Why on earth do we need to have the ftpmaster@d.o as Cc? Don't you
> guys believe they read debian-devel without cc-ing them?
Well, at least some active DDs *don't* read d-d@ and I can understand why.
--
WBR, wRAR
signature.
On Mon, Mar 05, 2018 at 02:43:34PM -0700, Sean Whitton wrote:
> If a package is maintained in git, then re-using a version number means
> force-pushing a git tag
Just don't tag uploads until they are accepted.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Tue, Mar 06, 2018 at 06:15:10PM +, Ian Jackson wrote:
> > A changelog bloated with every replaced attempt is hard to read; gaps in
> > version numbering that come without an explanation also raise an eyebrow
> > (thus such a gap needs a comment in the changelog).
>
> How many replaced attem
On Tue, Mar 06, 2018 at 07:27:40PM +, Ian Campbell wrote:
> > I know for a fact that quite regularly licence checks on binNEW packages
> > causes RC bugs to pop up. I acknowledge it may be a burder for the ftp
> > team, but that reason alone probably deserves to keep binNEW as it is.
>
> That
On Wed, Mar 07, 2018 at 06:02:10AM +, Chris Lamb wrote:
> Andrey Rahmatullin wrote:
>
> > > > I know for a fact that quite regularly licence checks on binNEW packages
> > > > causes RC bugs to pop up. I acknowledge it may be a burder for the ftp
> > >
On Thu, Mar 15, 2018 at 01:55:26PM +0100, Philipp Hahn wrote:
> some library packages like "libtirpc1" (just my example here) contain a
> conffile like "/etc/netconfig". Naturally they must conflict with their
> successor "libtirpc3" as they contain the same file name.
No, they must not. Instead,
On Sun, Mar 18, 2018 at 01:54:20PM +0530, shirish शिरीष wrote:
> Now as I understand it and please share if I'm in the wrong, alioth
> is going away and salsa is taking over repository creation, branching
I don't see how this is related to the uploading stuff.
> and maybe at some point also the B
On Sun, Mar 18, 2018 at 07:08:17PM +0530, shirish शिरीष wrote:
> >> Now if the package maintainer is just a DM, even (s)f he prepares a
> >> package, (s)he still needs the ok of a DD to upload/sponsor the
> >> package so it fit for distribution i.e. new, experimental or unstable
> >> and ftp-mirro
On Tue, Apr 03, 2018 at 11:52:26PM -0700, Metztli Information Technology wrote:
> there is only a small hack to debian-example in git source for
> wireless-regdb, from upstream, thus created attached patch for
>
> git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.
On Wed, Apr 11, 2018 at 07:08:21AM +, Lumin wrote:
> Briefly speaking, if a DD was told that "Thank you for your contribution
> to Debian but please wait for at least 2 months so that your package
> can enter the archive.", will the DD still be motivated working on NEW
> packages??? Please conv
On Wed, Apr 11, 2018 at 11:50:22AM +0200, Xavier wrote:
> > If one excludes the node packages, the current state of NEW looks rather
> > good. It suggests[2] that the average wait for non-node packages is
> > about a fortnight.
> Fortnight is the average of existing package in queue, not average t
On Wed, Apr 11, 2018 at 02:29:25PM +0100, Ian Jackson wrote:
> (ii) You make a very good argument that policy should continue to give
> guidance for this kind of situation. The target should probably be
> put back in policy, but with an explicit note saying it's not normally
> desirable, or someth
On Mon, Apr 16, 2018 at 06:47:04PM +0200, Tobias Frost wrote:
> Collab-maint is
> like a big team (with everyone being member)
Citation needed.
There is no such thing as collab-maint anywhere except the alioth
namespace.
> If you were right, what exactly would be the difference between collab-mai
On Tue, Apr 17, 2018 at 01:04:47PM +, Scott Kitterman wrote:
> >if your package recommends a package which is not available, this is a
> >normal bug, not one with RC severity (and neither an important one).
>
> Policy 2.2.1 pretty clearly says otherwise.
Whlile the release policy says "Package
On Tue, Apr 17, 2018 at 10:34:22PM +0200, Christoph Biedl wrote:
> There are people who don't follow every single action in Debian, plain
> stables users for example. For them it's helpful to tell the releases
> apart easily as they might not have the precise names and their order in
> mind. The fi
On Wed, Apr 18, 2018 at 09:20:11AM +0300, Lars Wirzenius wrote:
> > No, users and, I suspect, a large part of admins and developers cannot
> > easily say which of two codenames is newer, and it doesn't matter what are
> > those two codenames. Numeric versions are usually used to help with this,
> >
On Wed, Apr 18, 2018 at 11:23:23AM +0200, Martin Steigerwald wrote:
> As just someone who mostly maintains one package (fio - flexible I/O
> tester) I can certainly understand how you feel about that Lucas removed
> you as a maintainer.
But that didn't happen, unless you put different meaning in
On Wed, Apr 18, 2018 at 05:13:08PM +0200, Alex Mestiashvili wrote:
> Team maintained packages usually have team's name and mailing list in
> the "Maintainer:" field and possibly multiple "Uploaders:".
Sure. And either they convey some info with that (like Python teams do) or
not.
And somebody might
On Wed, Apr 18, 2018 at 03:19:51PM +0200, Martin Steigerwald wrote:
> > > As just someone who mostly maintains one package (fio - flexible I/O
> > > tester) I can certainly understand how you feel about that Lucas
> > > removed you as a maintainer.
> >
> > But that didn't happen, unless you put di
On Wed, Apr 18, 2018 at 04:00:51PM +0100, Ian Jackson wrote:
> Instead, tools grew to tolerate commas here rather than treat them as
> separators (because they would mishandle the erroneous packages).
Is this the main problem with fixing the Policy? Does someone have a plan
with this?
--
WBR, wRA
Thank you Andreas, this is surprisingly interesting.
On Thu, Apr 19, 2018 at 08:37:07AM +0200, Andreas Tille wrote:
> "Adam C. Powell, IV"
> Adam C. Powell, IV
> Debian GNOME Maintainers ,
> Sebastian Dröge
> John H. Robinson, IV
> "Natural Language Processing, Japanese"
>
> Natural L
On Fri, Apr 20, 2018 at 04:24:59PM -0700, Russ Allbery wrote:
> I'd be more comfortable with this (well, RFC 5322 at this point), since
> this removes a lot of the insanity. However, note that this is
> incompatible with existing Maintainer fields: RFC 5322 requires that . be
> quoted. So any Mai
On Sun, Apr 22, 2018 at 02:56:18PM +0100, Ian Jackson wrote:
> > > RFC 5322 also prohibits non-ASCII characters, which would have to be
> > > encoded in RFC 2047 encoding.
> >
> > Yeah, we don't want this.
>
> Luckily there is an established transformation for encoding non-ascii
> in 5322 headers
On Mon, Apr 23, 2018 at 01:52:22AM +0200, Julien Muchembled wrote:
> A lintian warning is even a reason for REJECT. "I" (my mentor) uploaded
> a new source package "zodbpickle" 5 weeks ago and I wonder if it's stuck
> because of this. I found strange to put an override for this so I
> didn't.
"Stuc
On Tue, May 01, 2018 at 11:10:15AM +0100, Aaron Gray wrote:
> Where do I find the .deb source packaging source code for packlages ?
Source packages don't have a .deb extension nor are they one file per
package, but you can find them in the apt repo, if you add a deb-src line
mirroring your deb line
On Tue, May 01, 2018 at 12:26:30PM +0200, Geert Stappers wrote:
> On Tue, May 01, 2018 at 03:17:27PM +0500, Andrey Rahmatullin wrote:
> > On Tue, May 01, 2018 at 11:10:15AM +0100, Aaron Gray wrote:
> > > Where do I find the .deb source packaging source code for packlages ?
&
There is an interesting question about this: technically speaking,
removing exported symbols requires a soname bump. But one can say that
those symbols were never public and so they are not a part of ABI.
Fixing this upstream and bumping the soname should be easier rthough..
--
WBR, wRAR
signat
On Tue, May 22, 2018 at 11:43:31AM +0200, Heinz Repp wrote:
> Just stumbled over some removals:
>
> GnuCash removed from testing in August 2017
> FreeCad removed from testing in October 2017
>
> no sign of any effort to readd them in sight ...
Maybe you are looking in a wrong place.
Last gnucash
On Fri, Jun 01, 2018 at 03:18:53AM -0400, Ken wrote:
> (1) IRC debian-mentors is NOT for mentees to ask question
No, it's the main purpose of that channel.
> and is invite-only
No.
> Unless I have missed some other documents (debian has plenty), I do think the
> community can use one single docu
On Fri, Jun 01, 2018 at 11:31:02AM -0400, Alexandre Viau wrote:
> On 2018-05-31 12:33 PM, Chris Lamb wrote:
> > [11] https://wiki.debian.org/MemberBenefits
> Oh, this reminds me of something.
>
> Has anyone gotten replies to their requests sent to
> debian-st...@collabora.com for the Steam subscr
On Tue, Jun 05, 2018 at 02:37:16PM +0200, Pierre-Elliott Bécue wrote:
> I wonder then, if a lot of people prefer deploy a service from upstream's
> git repo/cookbooks, what is the purpose of packaging? Who would benefit from
> it and who should use package-distros?
Yes, it's a more and more importa
On Thu, Jun 14, 2018 at 11:13:44AM -0500, Matt Zagrabelny wrote:
> In November of 2014 Raphael Hertzog posted [0] to
> -devel about a proposal (DEP-14) for recommended git branch names.
>
> The links he referenced are:
>
> http://dep.debian.net/deps/dep14
>
> http://anonscm.debian.org/viewvc/de
Hello,
A new open project has been created to collect the list of computer hardware
devices with poor Linux compatibility based on the Linux-Hardware.org data
within 4 years: https://github.com/linuxhw/HWInfo
There are about 29 thousands of depersonalized hwinfo reports
(https://github.com/ope
On Sat, Jul 07, 2018 at 02:44:39PM -0400, Tong Sun wrote:
> I have a question following
> https://honk.sigxcpu.org/piki/development/debian_packages_in_git/ --
> `gbp clone` will create the pristine-tar branch, right?
Only if it exists at the remote repo, of course.
> But having done that, I'm stil
On Thu, Jul 12, 2018 at 02:16:01PM +0100, Ian Campbell wrote:
> > > (3) CUDA Deep Neural Network library (cuDNN)[4] is NVIDIA's
> > > **PROPRIETARY**,
> > > stacked on CUDA, and requires NVIDIA GPU exclusively.
> >
> > so what? Debian runs on non-free CPUs too, how is this any different?
>
On Mon, Jul 16, 2018 at 03:14:20PM +0200, Dashamir Hoxha wrote:
> > ++ mktemp -d /dev/shm/pw.sh.X
> > + WORKDIR=/dev/shm/pw.sh.JHasAYH9zwYz1
> > [...]
> > + decrypt /home/pkern/.pw/pw.tgz
> > + local archive=/home/pkern/.pw/pw.tgz
> > + local 'opts=--quiet --yes --batch '
> > + [[ -z ''
On Mon, Jul 16, 2018 at 03:49:18PM +0200, Dashamir Hoxha wrote:
> > > > ++ mktemp -d /dev/shm/pw.sh.X
> > > > + WORKDIR=/dev/shm/pw.sh.JHasAYH9zwYz1
> > > > [...]
> > > > + decrypt /home/pkern/.pw/pw.tgz
> > > > + local archive=/home/pkern/.pw/pw.tgz
> > > > + local 'opts=--quiet --yes
On Mon, Jul 16, 2018 at 04:45:58PM +0200, Philipp Kern wrote:
> > Can we assume you didn't look at the code trying to follow the logic and
> > you don't have the full picture?
>
> Can we please stop here? It takes grace to take back the request.
Sure, but this email was sent before receiving that
On Sun, Jul 22, 2018 at 12:16:22PM +0200, Rens Houben wrote:
> No one in this entire thread was asking that this software be removed.
>
> Instead, all along the suggestion has been "Rename some of the programs
> because Debian is not run by a bunch of puerile twelve-year-olds who get
> their sense
03.03.2018, 10:14, "Andrey Ponomarenko":
> Hi there!
>
> Good news for all interested in hardware compatibility and reliability.
>
> I've started a new project to estimate reliability of hard drives and SSD in
> real-life conditions based on the SMART data repor
On Fri, Aug 17, 2018 at 08:27:00AM +, Ulrike Uhlig wrote:
> While I understand the simplicity of using $company's cloud storage, I'd
> rather not rely on some external company and in particular not on this
> one. This company does not exactly represent what I would call ethical,
> non-proprieta
On Fri, Aug 17, 2018 at 10:12:00AM +, u wrote:
> >> While I understand the simplicity of using $company's cloud storage, I'd
> >> rather not rely on some external company and in particular not on this
> >> one. This company does not exactly represent what I would call ethical,
> >> non-propriet
On Sun, Aug 19, 2018 at 10:02:57PM +, Jeremy Stanley wrote:
> I've heard that Debian's just a bunch of pedantic wonks who care more
> about licensing technicalities than whether their distribution carries
> working software
This is correct, at least partially and if you remove "just".
--
WBR,
On Mon, Aug 20, 2018 at 10:23:53PM +0200, Geert Stappers wrote:
> There is PEP, https://en.wikipedia.org/wiki/Pretty_Easy_privacy
> project website is https://www.pep.security/
>
> However `apt search pep` doesn't show it?
> Neither is a WNPP bugreport at hand.
Not everything is packaged.
> Is Pr
On Tue, Aug 21, 2018 at 08:13:24PM +0900, Roger Shimizu wrote:
> And emdebian's keyring [3] didn't hit archive, either.
Wrong:
https://tracker.debian.org/pkg/emdebian-archive-keyring
"As of July 2014, updates to the Emdebian distributions ceased." though.
--
WBR, wRAR
signature.asc
Descriptio
On Wed, Aug 22, 2018 at 01:02:30PM +1200, Robert Collins wrote:
> RedisLabs have changed the license of various modules to be
> incompatible with DFSG guideline 6: the 'Common Clause' rider.
>
> https://redislabs.com/community/commons-clause/
"Therefore, the no-sale restriction imposed by Commons
On Tue, Sep 04, 2018 at 09:39:39PM +0200, Ruben Undheim wrote:
> What is the recommendation? Any links to previous discussions / documents
> about
> this subject?
Policy 10.1.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Sat, Sep 08, 2018 at 12:03:18PM -0700, Sean Whitton wrote:
> My understanding is that there are quite deep social reasons for the
> current policy (please note, though, that I was not involved in Debian
> when this piece of policy was created; neither was I involved during the
> nodejs TC decisi
On Sat, Sep 08, 2018 at 06:07:43PM -0300, David Bremner wrote:
> Andrey Rahmatullin writes:
>
> > Last upload of ax25-node was in 2008, in 2009 it was effectively orphaned,
> > the TC bug was filed in 2011 and resolved in 2012, in 2015 ax25-node was
> > removed with
On Sun, Sep 23, 2018 at 10:53:04PM +0200, Aurélien COUDERC wrote:
> FTP masters rejected the upload of the new elisa 0.2.1-1 as the package has a
> lower version than the former Elisa project and they proposed bumping the
> epoch
> and reusing the name.
I don't find this reasonable to be honest.
On Mon, Sep 24, 2018 at 09:21:14AM -0700, Russ Allbery wrote:
> This causes a ton of headaches for the archive software. IIRC, I believe
> dak is rather unhappy about version numbers going backwards
This is unfortunate.
> apt is going to have no idea what to do for a system that already has the
>
On Mon, Sep 24, 2018 at 09:38:24AM -0700, Russ Allbery wrote:
> Ideally, we would never reuse the name of a binary package for some
> unrelated piece of software
Indeed.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Tue, Sep 25, 2018 at 12:36:30AM +, Devarajulu, Mohanasundaram wrote:
> During the upgrade if all the packages are installed then upgrade is
> going through well. If only the dev package with the problem and its
> dependencies are installed, by default apt keeps the packages back as it
> does
On Wed, Sep 26, 2018 at 12:52:41PM +0200, Graham Inggs wrote:
> I thought Lumin had made it clear enough that being able to obtain a
> stacktrace from within Julia is actually a feature [1]. One of Julia's
> tests checks this, and hence autopkgtests fail if debug symbols are missing
> from sys.so,
On Thu, Sep 27, 2018 at 02:28:35AM +, Harish Venkatraman wrote:
> Hi Ben,
>
> I am trying to manually back port to Linux 4.9 since in the link I don’t see
> a patch provided for 4.9 version. The last version that has this patch is
> 4.11, wanted to know if back port of this patch is support
On Thu, Sep 27, 2018 at 03:11:58PM +0300, Tommi Höynälänmaa wrote:
> Hi
>
> I would like to include the following software to Debian testing or stable
> distribution:
You can't add anything to current stable (only to the next stable), but
you can add new packages to unstable and they will then mov
On Sat, Oct 06, 2018 at 11:00:37AM +0300, Tommi Höynälänmaa wrote:
> If I need to update a package uploaded to mentors can I just upload the new
> package with dput?
Yes. You can even reuse the version.
Also, the proper mailing list for such questions is debian-mentors@
--
WBR, wRAR
signature.a
On Mon, Oct 15, 2018 at 02:20:03PM +0100, Jonathan Dowland wrote:
> Is it worth interested parties reaching out to the Devuan project
> regarding person-power for sysvinit maintenance?
It's hard to discuss this with a straight face, but in any case even they
admit they don't have any person-power:
On Wed, Oct 17, 2018 at 04:04:15PM +0200, Kamil Jońca wrote:
> (previously sent to debian-devel by mistake)
You've repeated that mistake.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Sat, Oct 20, 2018 at 06:54:07PM +0200, Arne Babenhauserheide wrote:
> > Should Debian also support "noalsa", "noavahi", "nocups",
> > "nopulseaudio", "nosysvinit", "nodbus", "nopam", "nowayland",
>
> Are alsa, avahi, cups, pulseaudio, sysvinit, dbus, pam and wayland all
> similar in scope to sy
On Sat, Oct 20, 2018 at 06:37:20PM +, Ivan Shmakov wrote:
> Now, unless I be mistaken, “build profiles,” as suggested in
> this subthread, are meant to allow for building packages with
> specific changes to their run-time library dependencies?
> Frankly, I don’t see much
On Sun, Oct 21, 2018 at 12:13:27PM -0400, Marvin Renich wrote:
> The proper fix is to convince upstream to dynamically link at runtime
> and disable some features if libgpgme is not available.
dlopening a dependency is bad: for example, it doesn't allow distro
builders to track the deps properly an
On Sun, Oct 21, 2018 at 01:15:21PM +, Ivan Shmakov wrote:
> Semantically, Depends: declares that the package has to be
> installed to proceed. It doesn’t specify whether the package
> has to actually be used. Which kind of invalidates the point.
"Every package must specify
On Sun, Oct 21, 2018 at 01:46:48PM -0400, Marvin Renich wrote:
> > > The proper fix is to convince upstream to dynamically link at runtime
> > > and disable some features if libgpgme is not available.
> > dlopening a dependency is bad: for example, it doesn't allow distro
> > builders to track the
On Sun, Oct 21, 2018 at 05:33:57PM +, Ivan Shmakov wrote:
> > "Every package must specify the dependency information about other
> > packages that are required for the first to work correctly." Policy 3.5.
>
> The gnupg package is not required for (neo)mutt to work
> correctly,
On Tue, Oct 23, 2018 at 05:01:04PM +0200, Wouter Verhelst wrote:
> > That would be a bad idea -- we don't want gratuitous dependencies all
> > around. Just because I use xfce doesn't mean I want a daemon for some old
> > kinds of iApple iJunk
>
> Why not? What does it cost you, other than a few b
Hello, I'd like to present a new project called "ABI Navigator" for searching binary symbols (functions, methods, global data, etc.) in open-source libraries: https://abi-laboratory.pro/index.php?view=navigator The project allows to find out in which versions of libraries some symbol is defined, ad
Hi Philip,
Try Linux Hardware database: https://linux-hardware.org/
You can upload a "probe" of your computer hardware to the db, open the probe
url and investigate the Linux-compatibility and operability of devices on
board. Look at probes and hardware logs of the same computer model and same
On Mon, Feb 27, 2017 at 03:14:08PM +, Ian Jackson wrote:
> > It's not even about updating: the first version of chromium with this
> > build-time tweak simply disabled all already installed extensions for me
> > so they were not activated when I restarted chromium after that upgrade
> > session
On Mon, Feb 27, 2017 at 04:43:29PM +, Ian Jackson wrote:
> > > Do we know why this is ? Is this an unintended side effect of some
> > > other change ? Has someone done this deliberately and if so have they
> > > explained what they were trying to achieve ?
> > >
> > > I can see that the beha
On Wed, Mar 01, 2017 at 01:17:24AM +, Reinhard Tartler wrote:
> > > I can see that the behaviour you describe would be very annoying.
> > When updating extensions is disabled, it is a "good" thing that you cannot
> > install them and use installed ones.
> It's certainly *not* good. It may be "s
On Mon, Mar 06, 2017 at 11:09:37AM -0500, Christopher Clements wrote:
> I have mutt configured to let me edit the headers along with the
> message, but I thought that stuff like the "To:" field were read by SMTP
> servers to determine where to deliver the message, sort of like post
> office relay b
On Mon, Mar 06, 2017 at 05:58:02PM +0100, Philip Hands wrote:
> I presume this issue arises because people (myself included) dislike the
> fact that in order to install some RFCs and/or GNU documentation one has
> to flick a switch that also opens the door to some thoroughly
> proprietary software.
On Tue, Mar 07, 2017 at 04:53:34PM +, Holger Levsen wrote:
> I think Debian has better things to do than working on fine grained control
> over non-free stuff. Obviously anybody is free to work on this, but I dont
> think we should make our repositories, packages, policies and workflow s
>
On Thu, Mar 09, 2017 at 10:14:13AM -0800, Russ Allbery wrote:
> If you don't want possibly unused software installed, we have a supported
> mechanism for that: disable automatic installation of Recommends.
Which explodes from time to time, like when ntpdate and ntpd only
recommended lockfile-progs
On Thu, Mar 09, 2017 at 12:22:17PM -0800, Russ Allbery wrote:
> >> If you don't want possibly unused software installed, we have a
> >> supported mechanism for that: disable automatic installation of
> >> Recommends.
>
> > Which explodes from time to time, like when ntpdate and ntpd only
> > recom
On Wed, Mar 22, 2017 at 08:16:14PM +0200, Jonathan Carter (highvoltage) wrote:
> so what's going to be the best way to make these
> available to Debian stable users?
https://wiki.debian.org/Chromium#Extensions
--
WBR, wRAR
signature.asc
Description: PGP signature
On Wed, Mar 22, 2017 at 09:51:12PM +0100, Jeroen Dekkers wrote:
> If we already know this is going to be major issue, why aren't we
> doing the sensible thing and enable extensions by default
The story of extensions in Debian Chromium is a strange and sad one.
See also https://bugs.debian.org/cgi-b
On Fri, Mar 24, 2017 at 01:46:31PM +0100, Adam Borowski wrote:
> Thought I'd share a trick I'm using: as debhelper's dependencies chain became
> really fat, you can gain a drastic speed-up (especially for small packages)
> by preinstalling debhelper into your base sbuild/pbuilder/etc image.
What if
801 - 900 of 1182 matches
Mail list logo
