On Sat, May 17, 2014 at 01:02:08PM -0700, Manoj Srivastava wrote:
> > Over the years, I've seen endless confusion about the current definition
> > of a critical bug severity:
Totally agree.
> > makes unrelated software on the system (or the whole system) break, or
> > causes serious data l
On Tue, Jun 10, 2014 at 09:32:05PM +0200, Stefano Rossi wrote:
> Hello Dariusz and Andrey,
>
> I'd love to see a Profanity package for Debian. Are you, Dariusz, still
> working on it?
> I also would like to know, why would the OpenSSL requirement make it
> impossible t
Package: wnpp
Severity: wishlist
Owner: Andrey Rahmatullin
* Package name: dwarftherapist
Version : 0.6.10+hgNN
Upstream Author : Trey Stout
* URL : http://code.google.com/p/dwarftherapist/
* License : Expat
Programming Lang: C++
Description : Helper
Package: wnpp
Severity: wishlist
Owner: Andrey Rahmatullin
* Package name: git-hg
Version : 20110408-1
Upstream Author : Barak A. Pearlmutter
* URL : https://github.com/barak/git-hg
* License : Expat
Programming Lang: Bash
Description : Script to
On Sun, Apr 10, 2011 at 07:52:52PM +0200, Mike Hommey wrote:
> The right approach for mercurial tracking is IMHO
> https://github.com/SRabbelier/git/tree/remote-hg
I've asked about the right way to do that at
http://lists.debian.org/debian-mentors/2011/04/msg00171.html yesterday and
didn't receive
On Thu, May 12, 2011 at 11:35:16AM +0200, Lech Karol Pawłaszek wrote:
> You've just encountered:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626450
>
> I've fixed it this way:
> # /lib/ld-linux-x86-64.so.2 /bin/ln -s /lib /lib64
> # /lib/ld-linux-x86-64.so.2 /usr/bin/dpkg --configure -a
Not
On Fri, May 13, 2011 at 08:29:40PM +0100, Roger Leigh wrote:
> > Switching to /run/ triggers a critical bug in ifupdown's init script
> > (#623076, #623523, proposed change in #625204). This completely breaks
> > any kind of network access (including lo), if /etc/network/run is a
> > symlink to /
On Tue, May 17, 2011 at 10:26:13PM +0200, Eshat Cakar wrote:
> At the moment there is no way to get more information about
> suggested/recommended packages, except their names. In particular I am
> talking
> about which functionality is added when also installing them.
Yes, I think there should
On Tue, May 24, 2011 at 05:32:08PM +0800, jida...@jidanni.org wrote:
> JM> How about trying a “grep pae /proc/cpuinfo” instead of looking for
> JM> approximate CPU descriptions?
> And indeed lshw says
> product: Intel(R) Celeron(R) M processor 1.40GHz
> capabilities: fpu fpu_exc
On Tue, May 24, 2011 at 08:58:43AM -0700, Ben Hutchings wrote:
> > > JM> How about trying a “grep pae /proc/cpuinfo” instead of looking for
> > > JM> approximate CPU descriptions?
> > > And indeed lshw says
> > > product: Intel(R) Celeron(R) M processor 1.40GHz
> > > capabilitie
On Wed, Jun 08, 2011 at 08:02:34PM +0900, Charles Plessy wrote:
> shuffle will randomize the order of lines in a file. In other words,
> if you have a sorted file, shuffle will undo the sort.
sort -R
Also, biosquid package contains /usr/bin/shuffle.
> stats is a small utility for computing desc
On Wed, Jul 20, 2011 at 10:42:07AM +0200, Adam Borowski wrote:
> > How does the (unreleased) version compare with Arora (my current
> > candidate for "small but usable web browser") and how soon is it
> > likely to be ready for release?
> Arora is just a yet another interface for webkit; it takes
On Wed, Jul 20, 2011 at 07:40:40PM +0200, Axel Beckert wrote:
> > > On the other hand, Dillo's support for CSS and such is sketchy at best.
> > > There's no javascript or anything of that kind as well.
> > What about links2 -g?
>
> JavaScript support in links2 has been killed by upstream in the 2.
On Mon, Jul 25, 2011 at 11:46:47PM +0100, Lars Wirzenius wrote:
> Anyway, qemu-img can convert a raw disk image
> into many other formats. So you generate one raw image, and then
> convert it to any other formats using qemu-img.
Also, according to
http://en.wikipedia.org/wiki/Virtual_disk_image#Vir
On Mon, Jul 25, 2011 at 05:04:21PM +0200, Wouter Verhelst wrote:
> Having said that, I do agree with you that it could benefit from either
> better documentation, or a command for system admins to use which would
> enable or disable initscripts. RedHat (and similars) have 'chkconfig'
> which does t
On Sun, Jul 24, 2011 at 10:20:45PM +0200, Wouter Verhelst wrote:
> > >That this is not particularly useful is not specific to any init
> > >implementation. I hate 'ENABLED=' configuration options with a passion.
> > >They do not make *any* sense, even init.d has a documented (and what's
> > They do
On Sun, Jul 31, 2011 at 08:27:04PM +, Clint Adams wrote:
> On Sun, Jul 31, 2011 at 05:38:43PM +0600, Andrey Rahmatullin wrote:
> > I would be glad if all services (at least network-enabled or especially
> > insecure for other reasons) didn't start by default.
> Maybe eve
On Mon, Aug 01, 2011 at 12:14:31PM +0200, Marco d'Itri wrote:
> > > > I would be glad if all services (at least network-enabled or especially
> > > > insecure for other reasons) didn't start by default.
> > > Maybe everyone would be happy if there were a central place to set
> > > the administrator
On Sun, Jul 24, 2011 at 10:52:13PM +0100, Simon McVittie wrote:
> > even init.d has a documented (and what's
> > more, actually *working*) implementation of not starting daemons at
> > boot. It's called 'remove the *** symlink'.
> If you remove them, they'll be recreated by the next upgrade; th
On Sun, Jul 31, 2011 at 08:27:04PM +, Clint Adams wrote:
> > I would be glad if all services (at least network-enabled or especially
> > insecure for other reasons) didn't start by default.
> Maybe everyone would be happy if there were a central place to set
> the administrator's preferred poli
On Mon, Aug 01, 2011 at 05:59:45PM +0100, Adam D. Barratt wrote:
> > > > I would be glad if all services (at least network-enabled or especially
> > > > insecure for other reasons) didn't start by default.
> > > Maybe everyone would be happy if there were a central place to set
> > > the administra
On Fri, Aug 05, 2011 at 07:35:49PM +0200, Wouter Verhelst wrote:
> If you do want it started, that means you need to install it first. Then
> it makes very much sense it is started automatically.
Logical fallacy: "run" implies "install", but "install" doesn't always
mean "run".
--
WBR, wRAR
sig
On Fri, Aug 05, 2011 at 07:12:58PM +0100, Lars Wirzenius wrote:
> > > If you do want it started, that means you need to install it first. Then
> > > it makes very much sense it is started automatically.
> > Logical fallacy: "run" implies "install", but "install" doesn't always
> > mean "run".
> Whi
On Mon, Aug 15, 2011 at 11:25:42AM +0200, Luca Capello wrote:
> What about zless & Co.? Are they available for xz as well?
xz-utils contains xzless, xzcat etc.
--
WBR, wRAR
signature.asc
Description: Digital signature
On Mon, Aug 29, 2011 at 04:40:30PM +0100, Wolodja Wentland wrote:
> they decided to remove one of (typically) gnome's dependencies, which
> caused the metapackage to be removed as well.
That also causes an effect of "GNOME gets removed!" even without any
additional autoremoved packages :(
--
WBR
On Wed, Aug 31, 2011 at 09:54:28AM +0200, Stéphane Klein wrote:
> Hi,
>
> I would like to make very simple Debian package to install very
> simple file on my system, only static file, like documentation.
The only difference between a project with static files and a project with
software is usually
On Mon, Sep 05, 2011 at 05:56:25PM +0100, Lars Wirzenius wrote:
> > This is a minor issue,but I would propose to change it to
> > http://svn.debian.org/viewvc/dep/web/deps/dep5.mdwn?revision=REVISION
> > if the Format field should point to a specific svn version of the
> > document. However, as f
within the international astronomical
community, from the radio to gamma-ray regimes, for data interchange and
archive, and also increasingly as an online format.
Setting up an upstream tracker [1] for wcslib ...
[1] http://linuxtesting.org/upstream-tracker/versions/wcslib.html
--
Andrey P
Package: wnpp
Severity: wishlist
Owner: Andrey Rahmatullin
* Package name: ipdb
Version : 0.6
Upstream Author : Godefroid Chapelle
* URL : http://pypi.python.org/pypi/ipdb
* License : GPL
Programming Lang: Python
Description : IPython-based pdb
On Tue, Nov 25, 2014 at 08:03:44PM +, Noel Torres wrote:
> > > Why is it that systemd proponents are the ones using this kind of
> > > signature? Are they trying to insinuate that Debian is theirs?
> >
> > Wow! A dipshit crazy conspiracy theory about systemd and its
> > proponents. Haven't see
On Wed, Dec 03, 2014 at 03:36:37PM +, Sam Hartman wrote:
> Didier> (Snipping others' parts, and moving to -devel)
>
> Didier> Given the (current) small exposure of
> Didier> testing-proposed-updates (aka the repository has very few
> Didier> users, therefore the packages there
On Wed, Dec 03, 2014 at 09:39:48PM +0100, Ondřej Surý wrote:
> > > Hi. You assert that even for leaf packages we should not make changes
> > > in unstable targeted beyond jessie. I can see an argument for that
> > > prior to the important bug deadline. However, past that point, I don't
> > > see
On Sun, Feb 22, 2015 at 08:18:33PM +0100, Bernhard R. Link wrote:
> > Here are two scenarios where building a static library (libfoo) with
> > -fPIC is desirable:
> >
> > * libbar has a stable API, so it should be shipped as a .so,
> >but if it links libfoo.a, and libfoo.a is not -fPIC, then
On Wed, Mar 11, 2015 at 01:27:21PM +, Joerg Desch wrote:
> Switch to 'en'
> New LOCALE: 'C'
> Hello World
> Switch to 'de'
> New LOCALE: 'C'
> Hello World
So these cases are expected to you?
> Switch to 'de.utf8'
> New LOCALE: 'de_DE.UTF8'
> Hallo Welt
>
> And on the embedded PC:
> # ./sample
On Wed, Jun 24, 2015 at 08:11:25AM -0700, pe...@easthope.ca wrote:
> GooString is referenced in pdftohtml.cc. What is its purpose
> or purposes?
Wrong list?
--
WBR, wRAR
signature.asc
Description: Digital signature
On Mon, Jun 29, 2015 at 10:22:30AM +0200, Adrien CLERC wrote:
> Le 29/06/2015 02:51, Filippo Giunchedi a écrit :
> > * Package name: structlog
> Hi,
>
> It seems to be a Python library (in the main site, I can read that it is
> used as an imported module), it should be named python-structlog.
On Sat, Jul 04, 2015 at 04:55:58PM +, lumin wrote:
> I have no trouble on making my personal choises, what I want to know
> is, what would you do to protect your software freedom, when the
> reality requires you to touch non-free blobs?
... such as firmwares in various microcontrollers in your
On Sat, Jul 04, 2015 at 07:48:26PM +0200, Michael Ole Olsen wrote:
> non-free, only the developer wins, and those that have enough money to buy
>
> free software lets poor countries use pcs.
You are making a grave mistake here (and below). Should I point it to you?
--
WBR, wRAR
signature.asc
D
On Sat, Jul 04, 2015 at 07:40:28PM +0200, Jan Gloser wrote:
> So from my perspective - feel free to use non-free software, but remember
> to pay for it, at least if the price is reasonable ;-).
What to do with non-free software that doesn't require payment?
It's the matter the original message was
On Sat, Jul 18, 2015 at 10:52:33AM +0200, Ole Streicher wrote:
> > Distributing them to Debian recipients makes the implicit promise that
> > they are free by the DFSG, or that they should be removed from Debian if
> > that's discovered to be untrue.
>
> Can't we just put non-free logos to non-fre
On Sun, Jul 26, 2015 at 02:10:10PM +0200, Antonio Diaz Diaz wrote:
> >TBH this smells like FUD. For example I've never heard of corruption in
> >.xz files due to non-robustness, I'd expect that corruption to come from
> >external forces, and that integrity would help or not detect it.
>
> Sure it
On Mon, Jul 27, 2015 at 07:11:15PM +0200, Antonio Diaz Diaz wrote:
> I guess we are thinking about different use cases here: verifying a package
> that can be easily downloaded again in case of corruption, vs decompressing
> the only copy of an irreplaceable file.
Indeed.
> BTW, telling a user tha
On Mon, Jul 27, 2015 at 08:26:23PM +0200, Marcin M. wrote:
> 1. There are two repos on GitHub, yhara/down (upstream) and marmistrz/down.
> In marmistrz/down I'll create all the adaptation for Debian packaging. In
> Vcs-Git, should I point to my repo or to the upstream one?
https://www.debian.org/do
On Mon, Jul 27, 2015 at 09:20:33PM +0200, Antonio Diaz Diaz wrote:
> >>I guess we are thinking about different use cases here: verifying a package
> >>that can be easily downloaded again in case of corruption, vs decompressing
> >>the only copy of an irreplaceable file.
> >Indeed.
> So you agree th
On Sat, Aug 22, 2015 at 04:35:15PM +0200, Adam Borowski wrote:
> > I feel that arch:all packages requiring a specific architecture (or not
> > buildable on amd64) are quite marginal.
> On the other hand, there's a crapload of arch:all packages that fail on
> !amd64 despite having no valid excuse.
On Sat, Aug 22, 2015 at 09:26:07PM +0100, Simon McVittie wrote:
> >> -- are arch:all packages not building on other architectures worth filing
> >> FTBFS bugs for?
> >
> > I think this should be reported (it's probably common sense that you
> > should be able to rebuild a package on a given support
On Wed, Aug 26, 2015 at 09:38:04AM +0200, Andreas Barth wrote:
> > > Specific issues:
> > > - for i386, there is still sold new hardware with 32bit-only. Are
> > > there open issues for i386 (apart from the 32bit-generic ones)?
> >
> > FWIW, for x32, the security team would prefer if support in
On Wed, Oct 24, 2018 at 03:40:12PM +, Ivan Shmakov wrote:
> What are the values of the crypt_use_gpgme setting in each case?
> Could it be that mutt and neomutt actually have different defaults
> (one using gpg(1) directly and the other using GPGME) here?
According to codesear
On Fri, Oct 26, 2018 at 02:41:31PM +0200, Juliusz Chroboczek wrote:
> I've been encouraging my students to install Debian on their personal
> machines, and we've found out that a lot of them get the wrong Debian
> installer:
>
> - some of them attempt to install an AMD64 version of Debian in
>
On Wed, Nov 21, 2018 at 08:37:28PM -0700, Sean Whitton wrote:
> >> Before we get there, we should first start autoremoving packages from
> >> unstable, if we consider rc-buggy in unstable to be unacceptable. We
> >> do have quite a bit of things in unstable, that are neither getting
> >> fixed, nor
On Sun, Nov 25, 2018 at 10:25:44AM -0700, Sean Whitton wrote:
> >> If someone does want to come along and fix the package, having it pass
> >> through NEW again is not a good use of ftpteam time.
> > Sounds like NEW is the problem, not other parts?
>
> Not sure what you mean.
I mean it seems tha
On Tue, Nov 27, 2018 at 08:38:56AM +0100, Wouter Verhelst wrote:
> > > The experimental distribution is a good place for work in
> > > progress. Maybe the rules for automatic rejects can be relaxed for
> > > experimental so a package can go into the archive (and have e.g. the BTS
> > > used for tha
On Tue, Nov 27, 2018 at 08:38:46PM +0900, Hideki Yamane wrote:
> Cons)
> - Harder to get users for test with testing-proposed-updates repository
My understanding of the current consensus is that this is the main reason
for using the current workflow. Nobody would test anything except sid and
test
On Wed, Nov 28, 2018 at 07:52:08AM +0500, Alexander E. Patrakov wrote:
> As long as there is one Debian Developer (or any other person who has the
> right to upload binary packages) who has a merged /usr on his system used
> for building packages, there is a risk of reintroducing the bug through hi
On Wed, Nov 28, 2018 at 02:48:32PM -0200, Antonio Terceiro wrote:
> Would you be willing to also implement
>
> Tainted-By: not-built-in-a-chroot
That doesn't mean anything. You can build in a bad chroot and you can
build in a clean minimal sid system which is not a chroot but a VM.
> (ischr
On Wed, Nov 28, 2018 at 06:40:46PM +0100, Guillem Jover wrote:
> On Wed, 2018-11-28 at 22:13:41 +0500, Andrey Rahmatullin wrote:
> > On Wed, Nov 28, 2018 at 02:48:32PM -0200, Antonio Terceiro wrote:
> > > (ischroot(1) is from debianutils which is Essential).
>
> > &quo
On Thu, Dec 13, 2018 at 03:39:40PM +0200, Tommi Höynälänmaa wrote:
> Should the linker option "-Wl,--as-needed" be used for plugins, e.g. guile
> plugins? Debmake suggests using the option for the linker.
Are they actually buildable with that option?
--
WBR, wRAR
signature.asc
Description: PGP
On Tue, Dec 18, 2018 at 01:19:54PM +, Daniel Reichelt wrote:
> why does libnss3/buster depend on libc6 >= 2.28 for i386 but for amd64,
> >= 2.14 suffices?
Symbols, I'm sure.
> Is there a technical rationale for this
You can compare the symbol lists to find the differences, I suppose.
--
WBR
Even firefox was renamed twice.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Thu, Dec 20, 2018 at 01:49:29PM +, Mo Zhou wrote:
> I'm declaring this in advance, so if anyone see something dirty happend
> on the Julia binary packages, please don't report any bug against that
> dirty solution.
I'm afraid it doesn't matter for a broken package if the brokenness is
declar
On Wed, Jan 02, 2019 at 07:10:06PM +0100, Kai Harries wrote:
> [4] https://nixos.org/~eelco/pubs/phd-thesis.pdf
This is an interesting text. It shows that the author has read the FHS but
chose to ignore it. The only ref to FHS is in the following text:
"""
For instance, storing components in an es
On Tue, Feb 05, 2019 at 07:22:21AM +, Jonathan Dowland wrote:
> You need to create a Debian package that contains your symlink (or bash
> script), and then either find someone to sponsor uploads of your package
> into Debian, or become a Debian Maintainer or Developer to do so
> yourself.
>
>
On Sun, Feb 17, 2019 at 07:44:29AM +0100, Tollef Fog Heen wrote:
> I think it boils down to the question of «Are builds outside of a
> minimal + build-essential + build-deps» supported?». If they're not, we
> can just ignore the problem and deprecate the Build-Conflicts field
> (since it has no us
On Fri, Mar 08, 2019 at 07:28:11PM +0100, Adam Borowski wrote:
> There's a problem with extending the syntax: we have not one but five cron
> implementations in the distributions, and all would need to be in sync,
Not necessarily. Being in sync isn't required for init scripts.
--
WBR, wRAR
sign
On Fri, Apr 05, 2019 at 09:07:01PM +0300, Otto Kekäläinen wrote:
> Is there any hardening flag / cmake expert around who could help me
> get the hardening flags perfect in MariaDB 10.3?
Start with https://wiki.debian.org/Hardening#Notes_for_packages_using_CMake
> d/rules:
> https://salsa.debian.or
On Fri, Apr 05, 2019 at 09:55:34PM +0300, Otto Kekäläinen wrote:
> Hello!
>
> > > Is there any hardening flag / cmake expert around who could help me
> > > get the hardening flags perfect in MariaDB 10.3?
> > Start with https://wiki.debian.org/Hardening#Notes_for_packages_using_CMake
>
> I've rea
On Fri, Apr 05, 2019 at 10:17:16PM +0300, Otto Kekäläinen wrote:
> So apparently the 'D_FORTIFY_SOURCE=2' is in CPPFLAGS (not read by
> cmake) but not in CXXFLAGS (read by cmake)[1].
That's what the wiki page says, yes.
> So maybe I should define?
> CXXFLAGS=$(CXXFLAGS) $(CPPFLAGS)
That's the spir
On Fri, Apr 05, 2019 at 09:07:06PM +0200, Sven Hartge wrote:
> CMake is a bit "special" in that regard. To get the right hardening
> flags to work for some parts of Bacula, we had to include the following
> patch to kind-of brute force the flags:
> https://salsa.debian.org/bacula-team/bacula/blob/m
Isn't the Bikesheds initiative just this?
--
WBR, wRAR
signature.asc
Description: PGP signature
On Sun, Apr 07, 2019 at 02:17:00PM +, Mo Zhou wrote:
> However, I got a hint from a fellow developer and learned that
> "Bikeshed" has its own meaning under Debian's context, according
> to some old mailing list fragments[2][3] -- which refers to a
> dak feature (This is the first time I heard
On Mon, Apr 08, 2019 at 09:58:26AM +, Mo Zhou wrote:
> AUR's PKGBUILD, Fedora/CentOS/RedHat's .spec, Gentoo's .ebuild,
> all of them are single-file format. The advantages of single-file
> format includes easy distribution, e.g. copying & pasting from
> webpages (you cannot copy a directory fro
On Sun, Apr 07, 2019 at 01:08:42PM -0400, Peter Silva wrote:
> https://www.cnx-software.com/2018/08/27/rockpro64-rk3399-board-linux-review-ubuntu-18-04/
>
> 71fps or es2gears?
Is es2gears a benchmark, unlike glxgears?
--
WBR, wRAR
signature.asc
Description: PGP signature
On Sun, Apr 07, 2019 at 05:59:38PM +0200, Adam Borowski wrote:
> * nvidia proprietary: doesn't work with new kernels.
It does, even nvidia-legacy-304xx-kernel-dkms says "Building the kernel
modules has been tested up to Linux 4.20.".
--
WBR, wRAR
signature.asc
Description: PGP signature
On Thu, Apr 11, 2019 at 09:54:47AM +, Mo Zhou wrote:
> Any link please? Both apt-file-search and google found nothing.
It's in contrib.
https://tracker.debian.org/pkg/game-data-packager
--
WBR, wRAR
signature.asc
Description: PGP signature
On Sat, Apr 13, 2019 at 12:59:19PM +, Holger Levsen wrote:
> > > I see no point whatsoever in 3.0 (native).
> > The main advantage of 3.0 (native) is that it makes it explicit that
> > the package is deliberately native [...]
>
> ok, sorry, I ment to say: I see no point whatsoever in native pa
On Wed, Apr 17, 2019 at 08:44:20AM +1000, Hugh McMaster wrote:
> > At the time of writing 150 release-critical bugs affect buster. This is the
> > number which needs to reach zero before the release can take place.
>
>
> What’s the easiest way to get a list of these RC bugs?
https://udd.debian.or
On Fri, Apr 26, 2019 at 02:27:58PM +, Holger Levsen wrote:
> > > > > > I see no point whatsoever in 3.0 (native).
> > > > What's the point/advantage of native packages?
> > > No need to make a separate orig tarball.
>
> the irony here is that native packages also require an upstream tarball,
S
On Mon, Apr 29, 2019 at 11:40:39AM +0200, Adam Borowski wrote:
> that's a monstrosity -- my personal preference is raw git, where updating to
> a new upstream is "git merge v3.14.15"
gbp allows this too, of course.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Mon, Apr 29, 2019 at 11:18:48AM +0200, Gard Spreemann wrote:
> For one of my packages, I maintain two public git branches: one is
> upstream/latest, where I've been importing upstream's released tarballs,
> and the other is debian/sid that contains the packaging.
>
> Recently, upstream has fina
On Thu, May 09, 2019 at 12:02:26AM +0200, Adam Borowski wrote:
> > We have various applications that only want to extract single members of
> > the package (changelog, NEWS, copyright, ...); tar is a really bad
> > format for such an operation. Other formats (zip, 7z, ...) are more
> > suited for
On Tue, May 14, 2019 at 11:11:46AM +0300, Adrian Bunk wrote:
> How well are you testing such conversions?
> Based on work I've seen from you I'd guess your NMU would be better than
> average. Unfortunately this is not generally true.
>
> Based on what enters the archive, "debdiff between old and
On Tue, May 14, 2019 at 09:10:04AM +, Holger Levsen wrote:
> On Tue, May 14, 2019 at 02:07:11PM +0500, Andrey Rahmatullin wrote:
> > One can go further and say that people uploading broken packages are the
> > actual problem. After all, we have several classes of bugs cause
On Tue, May 28, 2019 at 11:19:37PM +0200, Jean-Philippe MENGUAL wrote:
> Forwarding mail from @debian.org to my mailbox makes me apply
> complicated filters to stay subscribed to ML I wish.
Why?
--
WBR, wRAR
signature.asc
Description: PGP signature
On Wed, May 29, 2019 at 08:43:55AM +0200, Andreas Tille wrote:
> IMHO this touches another burning topic: Its not that we do not want to
> provide some PPA equivalent - its just that we do not realise it. I do
> not remember how many years ago we talked about bikesheds (and
> obviously we even fo
On Wed, May 29, 2019 at 02:14:09PM +0100, Ben Hutchings wrote:
> [...]
> > My understanding is that this unusual difference between the .orig
> > tarball and what's in git is an attempt to "square the circle" between
> > two colliding design principles: "the .orig tarball should be upstream's
> > o
On Wed, May 29, 2019 at 12:20:23PM -0400, Sam Hartman wrote:
> >> Perhaps we should update policy to say that the .orig tarball may
> >> (or even "should") be generated from an upstream release tag
> >> where applicable.
> Andrey> This
On Tue, Jun 04, 2019 at 01:37:46PM +, Thorsten Glaser wrote:
> I’d also throw in that monocultures are not good, and that people
> in general are happier when they aren’t forced into anything.
Yet people in general are also happier when they don't need to learn all
ways to do something.
> Just
On Tue, Jun 04, 2019 at 04:10:38PM +0200, Jonas Smedegaard wrote:
> > > I’d also throw in that monocultures are not good, and that people in
> > > general are happier when they aren’t forced into anything.
> > Yet people in general are also happier when they don't need to learn
> > all ways to do
On Tue, Jun 04, 2019 at 02:27:03PM +, Thorsten Glaser wrote:
> No. A maintainer normally deals with their own packages, or with
> .dsc and debdiff, for NMU. (This is also an answer to the reply
> from wrar. Oh, jonas also said so, reloading the list index page.)
A maintainer normally deals with
On Tue, Jun 25, 2019 at 08:08:22AM +0200, Ansgar wrote:
> Hi,
>
> what do people think about getting rid of current suite names ("stable",
> "testing", "unstable") for most purposes? We already recommend using
> codenames instead as those don't change their meaning when a new release
> happens.
A
On Tue, Jun 25, 2019 at 09:46:00AM +0200, Bastian Blank wrote:
> > Related to that I would like to be able to write something like
> > deb http://deb.debian.org/debian debian11 main
> > deb http://security.debian.org/debian-security debian11-security main
> > in sources.list as codenames confus
On Tue, Jun 25, 2019 at 12:43:56PM +0200, Paride Legovini wrote:
> My question is: are we trying to solve an actual problem here?
No, and please note that the author is not even a Debian user:
https://lists.debian.org/debian-devel/2019/06/msg00376.html
--
WBR, wRAR
signature.asc
Description: PG
On Tue, Jun 25, 2019 at 06:28:13PM +0200, Alf Gaida wrote:
> > oldoldstable has the value of demonstrating some of what's wrong with
> > the current system
>
> Can you please explain, i don't get it
That name is stupid.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Tue, Jun 25, 2019 at 12:40:01PM -0400, Michael Stone wrote:
> > and so on - i take the older releases only as reference.
>
> I just do something like look at https://packages.debian.org/ssh
> Or, if I'm really curious about versions, then something like
> http://snapshot.debian.org/package/open
On Sat, Jun 29, 2019 at 01:53:35PM +0200, Tomas Pospisek wrote:
> TLDR; year based release identifiers should be prefered since they are
> much more intuitive to reason about than codenames and sequentialy
> numbered release identifiers.
>
> If Debian should improve/change release identifiers, the
On Sat, Jun 29, 2019 at 06:17:12PM +0400, Jerome BENOIT wrote:
> >>> As others here I am starting to get confused by the release code
> >>> names, as are my peers that are not that much into Debian. And
> >>> sequential release numbers are devoid of any semantics except for
> >>> their monotonicall
On Mon, Jul 01, 2019 at 03:04:26PM +0200, Enrico Weigelt, metux IT consult
wrote:
> On 29.05.19 17:41, Andrey Rahmatullin wrote:
>
> >> Perhaps we should update policy to say that the .orig tarball may (or
> >> even "should") be generated from an upstream
On Wed, Jul 03, 2019 at 08:59:26AM -0400, Sam Hartman wrote:
> The rationale is that on systems with full disk encryption the initramfs
> probably isn't encrypted
>
> I personally think sticking your full disk encryption keys onto the
> initramfs doesn't have a lot of value.
These two things are
On Wed, Jul 10, 2019 at 10:54:21AM +0200, olivier sallou wrote:
> So, am I doing something wrong?
You tried to install a package (what package? they don't exist) from a
repo that doesn't exist.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Wed, Jul 10, 2019 at 11:29:01AM +0200, olivier sallou wrote:
> I tried a package that is not in backports, it was just for test (for an
> automation tool I use)
> It should fail with a *package not found* , but should not fail about
> buster-backports being non available.
I don't think the faili
301 - 400 of 1182 matches
Mail list logo
