On Wed 11 Jul 2018 at 11:53:29 (+), Curt wrote:
> On 2018-07-10, David Wright wrote:
Yes, I wrote a post on 2018-07-10 but you haven't quoted any of it here.
> You following up to Woole[d]ge:
>
> Hmm, I struggle to see the connection between what I asked for and
> what you wrote. From
On 2018-07-10, David Wright wrote:
You following up to Woolege:
Hmm, I struggle to see the connection between what I asked for and
what you wrote. From your later post, I guess the answer is that
editing /etc/debian_version risks provoking expletives from other
users of the system.
That
On Fri 06 Jul 2018 at 08:41:58 (+), Curt wrote:
> On 2018-07-06, David Wright wrote:
>
> > Hmm, I struggle to see the connection between what I asked for and
> > what you wrote. From your later post, I guess the answer is that
> > editing /etc/debian_version risks provoking expletives from
On 2018-07-09, Greg Wooledge wrote:
> On Sat, Jul 07, 2018 at 07:55:26AM +, Curt wrote:
>> On 2018-07-07, davidson wrote:
>> > Speculation: I suspect that the listserv software escapes "From" after
>> > a newline, and that its chosen escape is synonymous with the embedded
>> > quote
On Sat, Jul 07, 2018 at 07:55:26AM +, Curt wrote:
> On 2018-07-07, davidson wrote:
> > Speculation: I suspect that the listserv software escapes "From" after
> > a newline, and that its chosen escape is synonymous with the embedded
> > quote character.[1]
> The culprit is therefore Wooledge
On 2018-07-07, davidson wrote:
> On Fri, 6 Jul 2018, Curt wrote:
>
>> On 2018-07-06, Greg Wooledge wrote:
>>>
From this, I conclude that Joey Hess is a skilled manipulator.
>>>
>>
>> (I didn't say this.)
>
> Observation: That line begins with "From".
>
> Speculation: I suspect that the
On Fri, 6 Jul 2018, Curt wrote:
On 2018-07-06, Greg Wooledge wrote:
From this, I conclude that Joey Hess is a skilled manipulator.
(I didn't say this.)
Observation: That line begins with "From".
Speculation: I suspect that the listserv software escapes "From" after
a newline, and
On 2018-07-06, The Wanderer wrote:
>
> On 2018-07-05 at 17:29, Nicholas Geovanis wrote:
>
>> But what I'm trying to point out here is that there seems to be no
>> such canonical (sic) Debian tool which CAN tell me what release and
>> version I'm running.
>
> That's not true. /etc/debian_version,
On 2018-07-05 at 17:29, Nicholas Geovanis wrote:
> But what I'm trying to point out here is that there seems to be no
> such canonical (sic) Debian tool which CAN tell me what release and
> version I'm running.
That's not true. /etc/debian_version, if not modified by the sysadmin,
should
On 2018-07-06, Greg Wooledge wrote:
>
>>From this, I conclude that Joey Hess is a skilled manipulator.
>
(I didn't say this.)
On Fri, Jul 06, 2018 at 08:41:58AM +, Curt wrote:
> So, Joey Hess is a crazy idiot, for instance?
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=81249
That was written in 2001. One hopes that he has learned something in
the 17 years since then. I certainly have.
Reading along to
On 2018-07-06, David Wright wrote:
> Hmm, I struggle to see the connection between what I asked for and
> what you wrote. From your later post, I guess the answer is that
> editing /etc/debian_version risks provoking expletives from other
> users of the system.
>
> That said, I do agree with
On Thu 05 Jul 2018 at 14:08:21 (-0400), Greg Wooledge wrote:
> On Thu, Jul 05, 2018 at 12:57:34PM -0500, David Wright wrote:
> > On Thu 05 Jul 2018 at 12:42:36 (-0400), Greg Wooledge wrote:
> > > On Thu, Jul 05, 2018 at 11:06:22AM -0500, David Wright wrote:
> > > > But if you're a sysadmin who has
On Thu 05 Jul 2018 at 16:29:30 (-0500), Nicholas Geovanis wrote:
> On Thu, Jul 5, 2018 at 3:46 PM Greg Wooledge wrote:
> >
> > On Thu, Jul 05, 2018 at 03:27:44PM -0500, Nicholas Geovanis wrote:
> > > (1) You foolishly relied on the value in /etc/debian_version when
> >
> > It is not a fucking
On Thu, Jul 5, 2018 at 3:46 PM Greg Wooledge wrote:
>
> On Thu, Jul 05, 2018 at 03:27:44PM -0500, Nicholas Geovanis wrote:
> > (1) You foolishly relied on the value in /etc/debian_version when
>
> It is not a fucking configuration file that you edit.
> It is supposed to be read only.
> Only a
On Thu, Jul 05, 2018 at 03:27:44PM -0500, Nicholas Geovanis wrote:
> (1) You foolishly relied on the value in /etc/debian_version when
It is not a fucking configuration file that you edit.
It is supposed to be read only.
Only a crazy idiot would manually edit the file that tells you what
On Thu, 5 Jul 2018 14:57:03 -0500
Nicholas Geovanis wrote:
> I am rightly accused of relying too heavily on /etc/debian_version to
> detect my running release. But it seems clear
> to me that the "right", canonical way to detect this is to query the
> installed package base to extract a
On Thu, Jul 5, 2018 at 3:16 PM Greg Wooledge wrote:
>
> On Thu, Jul 05, 2018 at 02:57:03PM -0500, Nicholas Geovanis wrote:
> > So surely there is an
> > "approved" tool for doing that. Hopefully OTHER THAN
> > apt, aptitude, synaptic or apt-get; ideally simpler and easier to
> > script than that.
On Thu, Jul 05, 2018 at 02:57:03PM -0500, Nicholas Geovanis wrote:
> I am rightly accused of relying too heavily on /etc/debian_version to
> detect my running release. But it seems clear
> to me that the "right", canonical way to detect this is to query the
> installed package base to extract a
I am rightly accused of relying too heavily on /etc/debian_version to
detect my running release. But it seems clear
to me that the "right", canonical way to detect this is to query the
installed package base to extract a version/release
number from a package name and/or version. So surely there is
On Thu, Jul 05, 2018 at 12:57:34PM -0500, David Wright wrote:
> On Thu 05 Jul 2018 at 12:42:36 (-0400), Greg Wooledge wrote:
> > On Thu, Jul 05, 2018 at 11:06:22AM -0500, David Wright wrote:
> > > But if you're a sysadmin who has a script that wants/needs a version
> > > *number* for any reason,
On Thu 05 Jul 2018 at 12:42:36 (-0400), Greg Wooledge wrote:
> On Thu, Jul 05, 2018 at 11:06:22AM -0500, David Wright wrote:
> > But if you're a sysadmin who has a script that wants/needs a version
> > *number* for any reason, then /etc/debian_version is the safest file
> > to modify.
>
> I
On Thu, Jul 05, 2018 at 11:06:22AM -0500, David Wright wrote:
> But if you're a sysadmin who has a script that wants/needs a version
> *number* for any reason, then /etc/debian_version is the safest file
> to modify.
I strongly disagree. The safest file to modify would be the broken
shell script
On Thu 05 Jul 2018 at 11:53:45 (+0100), Joe wrote:
> On Thu, 5 Jul 2018 10:09:36 + (UTC)
> Curt wrote:
>
>
> >
> > The problem I'm looking at is that the Debian testing/unstable
> > releases do not have a version number and are not going to be
> > receiving one any time soon (the tradition
On Thu 05 Jul 2018 at 12:58:21 (+1200), Richard Hector wrote:
> On 05/07/18 03:53, David Wright wrote:
> > On Wed 04 Jul 2018 at 13:18:14 (+1200), Richard Hector wrote:
> >> On 02/07/18 05:31, David Wright wrote:
> >>> On Sun 01 Jul 2018 at 22:44:17 (+1200), Richard Hector wrote:
> On
On Wed, Jul 04, 2018 at 10:09:29AM -0500, David Wright wrote:
> On Wed 04 Jul 2018 at 09:55:54 (+0900), John Crawley wrote:
> > Sorry, but I thought a "configuration file" was supposed to
> > influence the behaviour of _software_ in some way. Are files which
> > only provide info for humans also
On 2018-07-05, Joe wrote:
> On Thu, 5 Jul 2018 10:09:36 + (UTC)
> Curt wrote:
>
>
>>
>> The problem I'm looking at is that the Debian testing/unstable
>> releases do not have a version number and are not going to be
>> receiving one any time soon (the tradition of not according a number
>>
On Thu, 5 Jul 2018 10:09:36 + (UTC)
Curt wrote:
>
> The problem I'm looking at is that the Debian testing/unstable
> releases do not have a version number and are not going to be
> receiving one any time soon (the tradition of not according a number
> to these two releases being of the
On 2018-07-05, Richard Hector wrote:
>
> Equally, if I want to know what the time is, I can ask you.
> If you don't know, I can tell you.
> Then I can ask you, and now you'll know, and I'll find out.
>
> Right?
>
> We must be looking at different problems.
>
> I'm assuming that if you're trying
On 2018-07-05 09:58, Richard Hector wrote:
On 05/07/18 03:53, David Wright wrote:
On Wed 04 Jul 2018 at 13:18:14 (+1200), Richard Hector wrote:
On 02/07/18 05:31, David Wright wrote:
On Sun 01 Jul 2018 at 22:44:17 (+1200), Richard Hector wrote:
On 28/06/18 16:40, David Wright wrote:
On Wed
On 05/07/18 03:53, David Wright wrote:
> On Wed 04 Jul 2018 at 13:18:14 (+1200), Richard Hector wrote:
>> On 02/07/18 05:31, David Wright wrote:
>>> On Sun 01 Jul 2018 at 22:44:17 (+1200), Richard Hector wrote:
On 28/06/18 16:40, David Wright wrote:
> On Wed 27 Jun 2018 at 19:49:13
On Wed 04 Jul 2018 at 13:18:14 (+1200), Richard Hector wrote:
> On 02/07/18 05:31, David Wright wrote:
> > On Sun 01 Jul 2018 at 22:44:17 (+1200), Richard Hector wrote:
> >> On 28/06/18 16:40, David Wright wrote:
> >>> On Wed 27 Jun 2018 at 19:49:13 (+0200), Martin Krämer wrote:
> I am
On Wed 04 Jul 2018 at 09:55:54 (+0900), John Crawley wrote:
> On 2018-07-02 02:31, David Wright wrote:
> >What seems to be lost on people who feel a pressing need for
> >/etc/debian_version to contain a number to satisfy some script that
> >they have written (which seems to be the usual reason) is
On 02/07/18 05:31, David Wright wrote:
> On Sun 01 Jul 2018 at 22:44:17 (+1200), Richard Hector wrote:
>> On 28/06/18 16:40, David Wright wrote:
>>> On Wed 27 Jun 2018 at 19:49:13 (+0200), Martin Krämer wrote:
I am wondering if it is possible to get the debian release number
for debian
On 2018-07-02 02:31, David Wright wrote:
What seems to be lost on people who feel a pressing need for
/etc/debian_version to contain a number to satisfy some script that
they have written (which seems to be the usual reason) is that
/etc/debian_version is a configuration file.
I don't know
On Sun 01 Jul 2018 at 22:44:17 (+1200), Richard Hector wrote:
> On 28/06/18 16:40, David Wright wrote:
> > On Wed 27 Jun 2018 at 19:49:13 (+0200), Martin Krämer wrote:
> >> I am wondering if it is possible to get the debian release number
> >> for debian testing (and maybe sid) from command line?
On 28/06/18 16:40, David Wright wrote:
> On Wed 27 Jun 2018 at 19:49:13 (+0200), Martin Krämer wrote:
>> I am wondering if it is possible to get the debian release number
>> for debian testing (and maybe sid) from command line?
>
> Yes.
>
> # cat > /etc/debian_version
> Write whatever you want
On Wed 27 Jun 2018 at 19:49:13 (+0200), Martin Krämer wrote:
> I am wondering if it is possible to get the debian release number
> for debian testing (and maybe sid) from command line?
Yes.
# cat > /etc/debian_version
Write whatever you want here
^D
Job done. (That's a control-D.)
Whether it's
On Wed, Jun 27, 2018 at 03:03:45PM -0500, Nicholas Geovanis wrote:
> On Wed, Jun 27, 2018 at 12:49 PM Martin Krämer wrote:
> >
> > I am wondering if it is possible to get the debian release number for
> > debian testing (and maybe sid) from command line?
> > I know that current testing is
On Wed, Jun 27, 2018 at 12:49 PM Martin Krämer wrote:
>
> I am wondering if it is possible to get the debian release number for debian
> testing (and maybe sid) from command line?
> I know that current testing is codename buster, while its release number is
> 10.
> I can get the codename from
On Wed, 27 Jun 2018 19:49:13 +0200
Martin Krämer wrote:
Hello Martin,
>I know that current testing is codename buster, while its release
>number is 10.
My (possibly mistaken) understanding is that it will get the official
release number 10 when buster becomes the stable branch of Debian.
See
Hi everyone,
I am wondering if it is possible to get the debian release number for
debian testing (and maybe sid) from command line?
I know that current testing is codename buster, while its release number is
10.
I can get the codename from command line, but not that the corresponding
release
42 matches
Mail list logo
