Package: release-notes
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org, gib...@debian.org
TL;DR -- It is expected that trixie will be the last release of
Debian to include LXD, and users are encouraged to migrate to Incus
after upgrading.
(CC'ing debian-devel for br
Hi,
Stéphane Blondon wrote (Sun, 28 May 2023 13:16:24
+0200):
> > > Richard Lewis wrote (Fri, 19 May
> > 2023 00:58:26 +0100):
> >
> > > - are the red hyphens in eg the 'deb...' line near the top of
> > > >
> > https://people.debian.org/~holgerw/release-notes_sphinx/en/html/issues.html
> > > >
> > Richard Lewis wrote (Fri, 19 May
> 2023 00:58:26 +0100):
>
> > - are the red hyphens in eg the 'deb...' line near the top of
> > >
> https://people.debian.org/~holgerw/release-notes_sphinx/en/html/issues.html
> > > meant to be red? (maybe it is a syntax error?)
> >
Sphinx uses Pygments to h
r simpler, or even
> use a canned one like (this was simply my first web search result):
>
> https://pypi.org/project/Sphinx-Substitution-Extensions/
>
> The examples in its readme look to be along the lines of the Debian
> Release Notes use case anyway. There's also basic substitu
substitution you could get away with something far simpler, or even
use a canned one like (this was simply my first web search result):
https://pypi.org/project/Sphinx-Substitution-Extensions/
The examples in its readme look to be along the lines of the Debian
Release Notes use case any
is still lacking some
> > > functionality,
> > > which is heavily used in the release-notes.
> > > That is the use of substitutions within URLs.
> > > In docbook speach these were entities, and you could use them in URLs
> > > like this:
> >
tities (or now called substitutions) in
quoted lines like
deb https://deb.debian.org/debian RELEASENAME main contrib
or
# script -t 2>~/upgrade-RELEASENAMEstep.time -a
~/upgrade-RELEASENAMEstep.script
These also do not work.
That's the biggest blocker in the upgrading c
Hi,
RL wrote (Sat, 20 May 2023 12:52:25
+0100):
> Holger Wansing writes:
>
> > However, I may have some objections against the migration at all:
> > as far as I know, sphinx/reStructuredText is still lacking some
> > functionality,
> > which is heavily used in
Holger Wansing writes:
> However, I may have some objections against the migration at all:
> as far as I know, sphinx/reStructuredText is still lacking some functionality,
> which is heavily used in the release-notes.
> That is the use of substitutions within URLs.
> In docbook sp
Am 19.05.23 um 17:35 schrieb Ansgar:
I suggest to already document this in the release notes for bookworm,
possibly in Section 2.1 (Supported architectures) or a subsection in
Section 5 (Issues to be aware of for bookworm).
Maybe something along these lines:
+---
| Debian 12 is expected to be
Package: release-notes
X-Debbugs-Cc: Steve McIntyre , debian-devel@lists.debian.org
On Fri, 2023-05-19 at 15:03 +0100, Steve McIntyre wrote:
> I had been thinking about doing similar for installer images too, but
> with other work going on too I think it got too late in the cycle to
>
://salsa.debian.org/holgerw/release-notes
However, I may have some objections against the migration at all:
as far as I know, sphinx/reStructuredText is still lacking some functionality,
which is heavily used in the release-notes.
That is the use of substitutions within URLs.
In docbook speach
Control: tags -1 moreinfo
On Lu, 29 iun 20, 10:31:02, Holger Levsen wrote:
> package: release-notes
> x-debbugs-cc: Timo Weingärtner , Jan Luca
> Naumann , 963...@bugs.debian.org,
> debian-devel@lists.debian.org
>
> in #963191 on Mon, Jun 29, 2020 at 10:06:33AM +0200, B
package: release-notes
x-debbugs-cc: Timo Weingärtner , Jan Luca Naumann
, 963...@bugs.debian.org, debian-devel@lists.debian.org
in #963191 on Mon, Jun 29, 2020 at 10:06:33AM +0200, Bastian Blank wrote:
> On Mon, Jun 29, 2020 at 09:32:09AM +0200, Timo Weingärtner wrote:
> > 20.06
* David Bremner:
> Julian Andres Klode writes:
>
>>
>> apt install _toremove +toinstall
>>
>
> A common convention is to do something like
>
> apt install -- -toremove +toinstall
>
> I would prefer that to rolling our own syntax, unless there's some good
> reason (other than the small amount of e
Julian Andres Klode writes:
>
> apt install _toremove +toinstall
>
A common convention is to do something like
apt install -- -toremove +toinstall
I would prefer that to rolling our own syntax, unless there's some good
reason (other than the small amount of extra typing)
d
On Tue, Mar 10, 2020 at 08:36:25AM -0400, The Wanderer wrote:
> On 2020-03-10 at 06:58, Julian Andres Klode wrote:
>
> > On Sat, Mar 07, 2020 at 09:41:44PM +0100, Julian Andres Klode wrote:
> >
> >> ### Incompatibilities
> >>
> >> * The apt(8) command no longer accepts regular expressions or wild
On 2020-03-10 at 06:58, Julian Andres Klode wrote:
> On Sat, Mar 07, 2020 at 09:41:44PM +0100, Julian Andres Klode wrote:
>
>> ### Incompatibilities
>>
>> * The apt(8) command no longer accepts regular expressions or wildcards as
>> package arguments, use patterns (see New Features).
>
> Corre
On Sat, Mar 07, 2020 at 09:41:44PM +0100, Julian Andres Klode wrote:
> ### Incompatibilities
>
> * The apt(8) command no longer accepts regular expressions or wildcards as
> package arguments, use patterns (see New Features).
Correction - regular expressions starting in ^ or ending in $ (that i
On 08.03.20 19:10, Jonas Smedegaard wrote:
> Quoting Matthias Klose (2020-03-08 18:40:34)
>> On 3/7/20 9:41 PM, Julian Andres Klode wrote:
>>> # APT 2.0
>>>
>>> After brewing in experimental for a while, and getting a first outing in
>>> the Ubuntu 19.10 release; both as 1.9, APT 2.0 is now landing
On Sun, Mar 08, 2020 at 02:40:56PM -0400, Boyuan Yang wrote:
> Hi,
>
> 在 2020-03-07六的 21:41 +0100，Julian Andres Klode写道：
> > # APT 2.0
> > ### Incompatibilities
> >
> > * The apt(8) command no longer accepts regular expressions or wildcards as
> > package arguments, use patterns (see New Featur
Hi,
在 2020-03-07六的 21:41 +0100，Julian Andres Klode写道：
> # APT 2.0
> ### Incompatibilities
>
> * The apt(8) command no longer accepts regular expressions or wildcards as
> package arguments, use patterns (see New Features).
A little comment on this: I am okay with apt(8) no longer accepting reg
On Sun, Mar 08, 2020 at 07:10:49PM +0100, Jonas Smedegaard wrote:
> Quoting Matthias Klose (2020-03-08 18:40:34)
> > On 3/7/20 9:41 PM, Julian Andres Klode wrote:
> > > # APT 2.0
> > >
> > > After brewing in experimental for a while, and getting a first outing in
> > > the Ubuntu 19.10 release; bo
On Sun, Mar 08, 2020 at 07:10:49PM +0100, Jonas Smedegaard wrote:
> Quoting Matthias Klose (2020-03-08 18:40:34)
> > $ apt show >/dev/null | cat
> >
> > WARNING: apt does not have a stable CLI interface. Use with caution in
> > scripts.
> >
> > Is there a roadmap when the CLI interface will bec
Quoting Matthias Klose (2020-03-08 18:40:34)
> On 3/7/20 9:41 PM, Julian Andres Klode wrote:
> > # APT 2.0
> >
> > After brewing in experimental for a while, and getting a first outing in
> > the Ubuntu 19.10 release; both as 1.9, APT 2.0 is now landing in unstable.
> > 1.10 would be a boring, wei
On 3/7/20 9:41 PM, Julian Andres Klode wrote:
> # APT 2.0
>
> After brewing in experimental for a while, and getting a first outing in
> the Ubuntu 19.10 release; both as 1.9, APT 2.0 is now landing in unstable.
> 1.10 would be a boring, weird number, eh?
>
> Compared to the 1.8 series, the APT 2
# APT 2.0
After brewing in experimental for a while, and getting a first outing in
the Ubuntu 19.10 release; both as 1.9, APT 2.0 is now landing in unstable.
1.10 would be a boring, weird number, eh?
Compared to the 1.8 series, the APT 2.0 series features several new features,
as well as improvem
package: release-notes
severity: wishlist
x-debbugs-cc: debian-devel@lists.debian.org
On Tue, Apr 24, 2018 at 05:37:00AM +, Niels Thykier wrote:
> Reminder: The release-notes does have a section for "deprecations" (Note
> as I recall, it was empty for stretch, so it is prob
NOtes manager
Reno is a release notes manager for storing release notes in a git
repository and then building documentation from them.
This is a new OpenStack dependency (currently needed by os-client-config).
On Thu, May 15, 2014 at 06:33:41PM +0200, Luca Capello wrote:
> ...despite the above, MANY THANKS to all people writing the Release
> Notes (and any other official documentation), which is highly
> important at least for me, as well as a pleasure to read.
Hear hear, strongly and fully ac
't think
>> > we should force this on upgrades. There should be a prompt and an
>> > opportunity to not change init systems.
>>
>> Instead of or in addition to such prompting, I expect this switch will
>> be documented in the Release Notes so that people w
The umask used to be (and should be again now) settable
centrally. (/etc/login.defs or /etc/default/login LSB?)
Setting the umask in /etc/profile and multiple other rc
files (instead centrally in login.defs) was only necessary while
pam_umask was not available, and to be depreciated.
All the tim
Processing commands for cont...@bugs.debian.org:
> reassign 547220 release-notes
Bug #547220 [general] general: Lenny Upgrade Documentation Typos
Bug reassigned from package 'general' to 'release-notes'.
>
End of message, stopping processing here.
Please contact
--
# Nicolay DIMITROV .
# CRIS - Bât A 2ème étage
# Direction des Systèmes d'Information de l'Université Stendhal
# Domaine Universitaire 1180 avenue Centrale B.P.25 38040 Grenoble cedex 9
# Tel: 0476827797 Fax: 0476827754
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with
Quoting Thomas Mueller (thomas_mueller_...@online.de):
>
> Is someone working on the de-translations?
> Need help?
>
> This is the only langauge I can offer support.
> Just let me know!
The place to look for this is
debian-l10n-ger...@lists.debian.orgcc'ing the list.
--
signature.asc
Is someone working on the de-translations?
Need help?
This is the only langauge I can offer support.
Just let me know!
take care
Tom
Am Samstag, 24. Januar 2009 schrieb W. Martin Borgert:
> Hello world,
>
> sorry for repeating myself: It's high time to translate the
> r
Quoting Klebson Porfirio (klebs...@gmail.com):
> How can I get information about pt_BR translations status? I am with
> free time to help in what will be necessary.
That would be debian-l10n-portugu...@lists.debian.org.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a s
tors, do the translations now!
>
> See this mail from last october for technical details:
> http://lists.debian.org/debian-doc/2008/10/msg00134.html
>
> The SVN location of the release notes have changed since:
> svn://svn.debian.org/svn/ddp/manuals/trunk/release-notes
>
>
Le dimanche 14 décembre 2008 à 23:06 +0100, Luk Claes a écrit :
> The firmware GR
> ===
>
> With these hopefully solid plans in place for the release, we feel the
> need to acknowledge that there is an ongoing vote whose outcome could
> potentially disrupt them. In the release team we
On Mi,12.nov.08, 10:37:33, W. Martin Borgert wrote:
> there are some bugs open against the release notes to which
> nobody wrote a patch so far. This is your opportunity to help
> Debian and become famous!
...
> #491000 release-notes: Romanian translation is mixed with English
I fil
Hi,
there are some bugs open against the release notes to which
nobody wrote a patch so far. This is your opportunity to help
Debian and become famous!
Please: If you think, you have a good understanding of one or
more of the following issues and can write some sentences in
English about the
Raphael Hertzog wrote:
> On Thu, 03 Jul 2008, Bryan Donlan wrote:
>> On Thu, Jul 3, 2008 at 6:25 AM, Raphael Hertzog <[EMAIL PROTECTED]> wrote:
>>> Package: release-notes
>>> Severity: important
>>>
>>> To work-around a problem that can happen i
On Thu, 03 Jul 2008, Bryan Donlan wrote:
> On Thu, Jul 3, 2008 at 6:25 AM, Raphael Hertzog <[EMAIL PROTECTED]> wrote:
> > Package: release-notes
> > Severity: important
> >
> > To work-around a problem that can happen in the perl 5.10 upgrade (see
> > #4797
Hi,
On Thursday 03 July 2008 12:25, Raphael Hertzog wrote:
> Given that the new dpkg also supports triggers, we should probably also
> recommend to upgrade apt/aptitude at the same time otherwise those tools
> might be confused by the new package status...
#464559 (in apt) is also a problem for e
Package: release-notes
Severity: important
To work-around a problem that can happen in the perl 5.10 upgrade (see
#479711), the perl scripts contained in dpkg (update-alternatives,
dpkg-divert) have been modified... but for the work-around to be used, the
new dpkg must obviously be installed
Holger Levsen <[EMAIL PROTECTED]> writes:
> Hi,
>
> On Friday 23 March 2007 13:54, Goswin von Brederlow wrote:
>> We still have no usable linux-source deb. The prepatched source
>> currently shipped will not build vserver, xen and several archs and
>> the debian patch is not compatible to make-kpk
Hi,
On Friday 23 March 2007 13:54, Goswin von Brederlow wrote:
> We still have no usable linux-source deb. The prepatched source
> currently shipped will not build vserver, xen and several archs and
> the debian patch is not compatible to make-kpkg and it is undocumented
> how to apply it manualy
Luk Claes <[EMAIL PROTECTED]> writes:
> Hi,
>
> You might not remember who the release team is, but we still want to
> inform you about the final leg of the etch release cycle. Our original
> schedule did not work out due to problems with the kernel and the
> slower than expected reduction of rel
Le jeudi 28 septembre 2006 08:54, Andreas Barth a écrit :
> * sorting out docs-in-main vs. the DFSG
>
> Most packages with non-free docs have been split now and only a few
> packages are left. Sadly, the remaining packages include glibc,
> automake and emacs21. Please try to help out for those.
* Andreas Barth ([EMAIL PROTECTED]) [060928 08:56]:
> we hope to address with a General Resolution; or will be fixed with the
> removal of mozilla or the addition of X.org 7.1. This means that we are
"removal of mozilla" means of course the old all-in-one-suite that is
no longer supported by upst
Your message dated Tue, 7 Jun 2005 18:20:34 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#312282: release-notes: --guess?
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Package: general
Version: debian-doc@lists.debian.org
Hello,
the german release notes talk about the "--guess" option to deborphan,
however this is only a prefix for multiple options, I guess this should mean
"--guess-dummy" or maybe "one of the --guess* options".
get by with just upgrading aptitude
> > - desktops with kde, gnome (from unofficial backports or not) that will
> > have to look at the results of 'aptitude install aptitude' and decide if
> > anything else is needed; perl probably is a prime candidate
>
> >
kde, gnome (from unofficial backports or not) that will
> have to look at the results of 'aptitude install aptitude' and decide if
> anything else is needed; perl probably is a prime candidate
> I going to try to rewrite/reorganize chapter 4 of the release notes
> somew
candidate
I going to try to rewrite/reorganize chapter 4 of the release notes
somewhat on Saturday to see if I can make the upgrade instructions a bit
more organic.
pgpLCBeArcofP.pgp
Description: PGP signature
* Bernd Eckenfels ([EMAIL PROTECTED]) [050517 03:35]:
> In article <[EMAIL PROTECTED]> you wrote:
> >2. change the /etc/apt/sources.list to point to "stable"
> I wish all documentation is using the distribution names not the symbolic
> names. If you put "stable" in a file this will cause major
Hi Frans,
On Wed, May 18, 2005 at 12:31:29AM +0200, Frans Pop wrote:
> On Monday 16 May 2005 17:58, Frans Pop wrote:
> > Should users first upgrade dpkg and aptitude before upgrading the rest
> > of the system or can the upgrade safely be done using Woody's version
> > of the package tools?
> Fro
In article <[EMAIL PROTECTED]> you wrote:
> 1. Check that /etc/apt/sources.list points to "woody"
> 2. apt-get update
> 3. apt-get install aptitude
perhaps use "--reinstall" or "aptitude/woody" to force downgrade?
> 4. change the /etc/apt/sources.list to point to "sarge"
> 5. apt-get update
> 6
On Monday 16 May 2005 17:58, Frans Pop wrote:
> Should users first upgrade dpkg and aptitude before upgrading the rest
> of the system or can the upgrade safely be done using Woody's version
> of the package tools?
From the reactions to this thread and a thread on #309340 [1], the
consensus seems
If there is any architecture specific news that you'd like to have
included in the Release Notes (like new subarchs supported or dropped),
please send a proposed text to the d-doc mailing list (CC the list for
the architecture) before the end of this week.
Cheers,
Frans Pop
pgpJSfW0bTfF
retitle 309357 woody aptitude update can fail
quit
On Tue, May 17, 2005 at 01:45:14PM +0200, Gaudenz Steinlin wrote:
> On Mon, May 16, 2005 at 05:58:24PM +0200, Frans Pop wrote:
> > Long version:
> > The current version of the release notes tells users to (simplified):
> &g
> > The current version of the release notes tells users to (simplified):
> > > 1. apt-get install aptitude
> > > 2. change the /etc/apt/sources.list to point to "stable"
> > > 3. aptitude update
> > In my test a few days ago I had to use apt-get up
On Mon, May 16, 2005 at 05:58:24PM +0200, Frans Pop wrote:
> Long version:
> The current version of the release notes tells users to (simplified):
> 1. apt-get install aptitude
> 2. change the /etc/apt/sources.list to point to "stable"
> 3. aptitude update
In my test a
In article <[EMAIL PROTECTED]> you wrote:
>2. change the /etc/apt/sources.list to point to "stable"
I wish all documentation is using the distribution names not the symbolic
names. If you put "stable" in a file this will cause major trouble a few
years later. Beside it is unclear to the reader
On Mon, May 16, 2005 at 08:12:04PM +0200, Adrian Bunk wrote:
> On Mon, May 16, 2005 at 07:44:37PM +0200, Adeodato Simó wrote:
>...
> > Note that in (4), the command is aptitude, not apt-get.
>
> Does this make any difference?
>...
It does.
My fault, I confused (4) with (3).
cu
Adrian
--
On Mon, May 16, 2005 at 07:44:37PM +0200, Adeodato Simó wrote:
>
> 1. apt-get install aptitude
> 2. change the /etc/apt/sources.list to point to "stable"
> 3. aptitude update
> 4. aptitude install aptitude dpkg
> 5. aptitude -f --with-recommends dist-upgrade
0. change the /etc
On Mon, May 16, 2005 at 07:44:37PM +0200, Adeodato Simó wrote:
> * Adrian Bunk [Mon, 16 May 2005 18:14:20 +0200]:
> > On Mon, May 16, 2005 at 05:58:24PM +0200, Frans Pop wrote:
>
> > > The current version of the release notes tells users to (simplified):
> > > 1. ap
* Adrian Bunk [Mon, 16 May 2005 18:14:20 +0200]:
> On Mon, May 16, 2005 at 05:58:24PM +0200, Frans Pop wrote:
> > The current version of the release notes tells users to (simplified):
> > 1. apt-get install aptitude
> > 2. change the /etc/apt/sources.list to point to &qu
The current version of the release notes tells users to (simplified):
> 1. apt-get install aptitude
> 2. change the /etc/apt/sources.list to point to "stable"
> 3. aptitude update
> 4. aptitude -f --with-recommends dist-upgrade
>
> Step 1. is meant to install the Woody ve
Short version:
Should users first upgrade dpkg and aptitude before upgrading the rest of
the system or can the upgrade safely be done using Woody's version of the
package tools?
Long version:
The current version of the release notes tells users to (simplified):
1. apt-get install aptit
[ Rob Bradford, you're in CC: since I don't know if you read d-d and just
in case you miss this :-) ]
I've been reviewing for the Release Notes the packages in sid that are
provided for upgrade purposes only (since we did in the past for woody's
[1]). The goal is to p
On Sun, Apr 07, 2002 at 01:48:51PM +0200, Michael Banck wrote:
> On Sun, Apr 07, 2002 at 01:38:59PM +0200, Josip Rodin wrote:
> > On Sun, Apr 07, 2002 at 12:13:38PM +0100, Philip Hands wrote:
> > > after the dust settles after the CD stampede
> >
> > Speaking of which, what's the tactic to get thi
On Mon, 2002-04-08 at 10:15, Wilmer van der Gaast wrote:
> Michael [EMAIL PROTECTED]@Sun, 7 Apr 2002 13:48:51 +0200:
> > Don't worry, ./ will be faster. There's nothing we can do about it... ;)
> >
> You can always ask them not to post it before the mirrors are ready,
> not?
>
Hah, it is their
Michael [EMAIL PROTECTED]@Sun, 7 Apr 2002 13:48:51 +0200:
> Don't worry, ./ will be faster. There's nothing we can do about it... ;)
>
You can always ask them not to post it before the mirrors are ready,
not?
--
*=-+-__
|[EMAIL PROTECTED]: _ Ugh! Nio2f says something
> I don't see any harm in making up jigdo files for DVDs --- I don't see
Ooh, yes, please - I'd love to be able to make bootable dvds to pass
around here [MIT area.]
> Of course, if loads of people with DVD writers mail me, I'm likely to be
metoo :)
--
To UNSUBSCRIBE, email to [EMAIL PROTECT
On Sun, Apr 07, 2002 at 01:38:59PM +0200, Josip Rodin wrote:
> On Sun, Apr 07, 2002 at 12:13:38PM +0100, Philip Hands wrote:
> > after the dust settles after the CD stampede
>
> Speaking of which, what's the tactic to get this done efficiently? I suppose
> we could coordinate with several mirror m
On Sun, Apr 07, 2002 at 12:13:38PM +0100, Philip Hands wrote:
> after the dust settles after the CD stampede
Speaking of which, what's the tactic to get this done efficiently? I suppose
we could coordinate with several mirror maintainers to have them rsync copies
of the final images before the use
On Sun, Apr 07, 2002 at 12:13:38PM +0100, Philip Hands wrote:
>On Sun, 2002-04-07 at 11:51, Raphael Hertzog wrote:
>> You also speak of a DVD distribution, while it may be possible, I've
>> never heard of someone doing it officially ... better leave it out until
>> we actually provide some DVD imag
On Sun, 2002-04-07 at 11:51, Raphael Hertzog wrote:
> You also speak of a DVD distribution, while it may be possible, I've
> never heard of someone doing it officially ... better leave it out until
> we actually provide some DVD images ?
John Winters of linuxemporium.co.uk was asking me about this
Le Sat, Apr 06, 2002 at 04:58:18PM +0100, Rob Bradford écrivait:
> With the release nearly upon us this is an *URGENT* request for
> information regarding the woody release notes. The following issues need
> addressing.
>
> Draft release notes are available at
> http://www.d
On 6 Apr 2002, Rob Bradford wrote:
> * Split/Renamed packages *since* Potato - Have any of you packages been
> renamed or split. Note this includes merges as the net result is a
> rename.
The python-imaging documentation has been split, as not all of the
documentation is in the upstream archive.
n, 17 May 1999, Tim (Pass the Prozac) Sailer wrote:
> Date: Mon, 17 May 1999 09:24:07 -0400
> From: "Tim (Pass the Prozac) Sailer" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: debian-devel@lists.debian.org, [EMAIL PROTECTED]
> Subject: Re: Solaris NFS problems
On Mon, May 17, 1999 at 03:29:45PM +0300, Rainer Dorsch wrote:
>
> I forget to say, that I am running
>
> # uname -a
> Linux rai16 2.2.7 #1 Mon May 10 15:53:20 CEST 1999 i686 unknown
>
> Where do I get these NFS 3 patches from?
ftp.varesearch.com
I forwarded you the announcement just now.
> On Mon, May 17, 1999 at 10:30:52AM +0300, Rainer Dorsch wrote:
> >
> > It is nearly impossible to compile a large software package on a NFS
> > mounted
> > partion on potato, when it is exported by Solaris 2.6 (UltraSPARC). A
> > search
> > in Deja News (Solaris NFS patch in comp.os.linux.*)
On Mon, May 17, 1999 at 10:30:52AM +0300, Rainer Dorsch wrote:
>
> It is nearly impossible to compile a large software package on a NFS mounted
> partion on potato, when it is exported by Solaris 2.6 (UltraSPARC). A search
> in Deja News (Solaris NFS patch in comp.os.linux.*) found a couple of
aris partitions? Which patches
did you apply? Did you try to compile large programs? Hello world programs
work!
Bob,
I think, this issue should go into the release notes, because it may break
systems running slink for months without any problems, until the patch was
applies on the Solaris
hi
Ship's Log, Lt. [EMAIL PROTECTED], Stardate 250199.2228:
> How about adding that the xvidtune program is in the xf86setup package? Some
> users may be confident enough about their X configuration not to bother
> installing xf86setup, and then miss xvidtune.
If they are confident about there c
On Mon, Jan 25, 1999 at 10:28:56PM +, [EMAIL PROTECTED] wrote:
> How about adding that the xvidtune program is in the xf86setup package? Some
> users may be confident enough about their X configuration not to bother
> installing xf86setup, and then miss xvidtune.
As of version -9, xvidtune is
On Thu, Jan 14, 1999 at 04:20:51PM +, Robert Woodcock wrote:
> Many of you are painfully aware that there are some issues in slink that are
> impractical to correct before release.
>
>
> xbase -> xbase
>twm
>xterm
>xbase-clients
>xdm
>xf86setup
How abo
Rob Browning <[EMAIL PROTECTED]> wrote:
> I mostly agree, but the argument that anything to the right of the
> dash should only reflect *Debian* related revisions does hold some
> water.
The question is: is it being used to bail out a maintainer who didn't
take other steps to deal with the version
lopers
> Subject: RE: libc6_2.0.7 release notes...
>
>
> I think a reasonable policy statement for this would be something like:
>
> All pre-release versions will have debian revision of -0.x
>
> Maintainer release revisions will start at -1 and increment in
> whole number
I think a reasonable policy statement for this would be something like:
All pre-release versions will have debian revision of -0.x
Maintainer release revisions will start at -1 and increment in
whole numbers
Non maintainer releases will add a point version to the left of the
maintainer release
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> Well, my contention is that pre-release are *not* upstream
> releases. They can arguably be termed a special release (not an
> upstream release) that the debian maintainer has chosen to make. This
> is a bit of a stretch, but acceptable, in m
Hi,
>>"Rob" == Rob Browning <[EMAIL PROTECTED]> writes:
Rob> Manoj Srivastava <[EMAIL PROTECTED]> writes:
>> I actually like this. I still think that the aversion people
>> have for epochs is rather more than is warranted from the technical
>> objections (the mandatory longevity _is_ a technic
Hi,
>>"Jules" == Jules Bean <[EMAIL PROTECTED]> writes:
Jules> Someone suggested this earlier in the discussion, and someone
Jules> else pointed out that this is clearly against policy, since
Jules> anything after the '-' should reflect debian-specific
Jules> packaging changes, not upstream ch
> On Thu, 25 Jun 1998, Philip Hands wrote:
>
> >
> > until 2.1.0 comes out, so that we wouldn't need to use a ``dirty,
> > evil epoch''.
>
> No one has said anything about dirt or evil with respect to epochs.
Sorry, I was being facetious, and I forgot the ;-)
> Policy says not to use them for
Dale Scheetz <[EMAIL PROTECTED]> writes:
> If we simplify it to 2.0.8-0.1 then it should conform to your idea of
> policy better, but it doesn't convey as much information as the other form
> and it would make them look like non-maintainer releases.
Go with the more informative option, and make a
On Thu, 25 Jun 1998, Jules Bean wrote:
> Someone suggested this earlier in the discussion, and someone else pointed
> out that this is clearly against policy, since anything after the '-' should
> reflect debian-specific packaging changes, not upstream changes.
>
Then I would argue that the polic
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> I actually like this. I still think that the aversion people
> have for epochs is rather more than is warranted from the technical
> objections (the mandatory longevity _is_ a technical objection), but
> the -0 approach is elegant.
I mostly
Hi,
>>"Dale" == Dale Scheetz <[EMAIL PROTECTED]> writes:
Dale> Brandon Mitchell has come up with a better scheme than my "numbering"
Dale> alternative. Consider the following:
Dale> 2.0.8pre12.0.8-0pre1
Dale> 2.0.8pre22.0.8-0pre2
Dale> 2.0.8 2.0.8-1
Dale> This has
1 - 100 of 189 matches
Mail list logo
