t
release. |
Fake announcement or not, I'd like to say that Trixie and Forky are
excellent names to represent 13 and 14.
I understand it's hard to find that good a match for 15.
But... Buttercup barely beyond Buster, Bullseye, Bookworm begins being
boring...
Franklin, Funky or Dolp
On Wed, Jul 05, 2023 at 11:05:05PM +0200, Joaquín Rufo Gutierrez wrote:
> No, Debian 13 will be released on 2024 occasionally.
Who are you, sorry?
The person who sent this "announcement" doesn't seem to be part of the
Debian Project, they're also not listed as a member of the release
team at https://www.debian.org/intro/organization
Someone from the release team might confirm my assumption, but for now
please assume
Il 05/07/2023 22:50, Joaquín Rufo Gutierrez ha scritto:
|Hello Debian users, We are happy to announce that Debian 13,
codenamed "Trixie", is expected to be released sometime in 2024,
following the usual 2-year release cycle.|
|
|
|Hi, sorry but if it were |||2-year release cycle | shouldn't i
No, Debian 13 will be released on 2024 occasionally.
El mié, 5 jul 2023 a las 23:04, Mike Hommey () escribió:
> On Wed, Jul 05, 2023 at 10:50:34PM +0200, Joaquín Rufo Gutierrez wrote:
> > Hello Debian users,
> >
> > We are happy to announce that Debian 13, codenamed "Trixie", is
> > expected to b
On Wed, Jul 05, 2023 at 10:50:34PM +0200, Joaquín Rufo Gutierrez wrote:
> Hello Debian users,
>
> We are happy to announce that Debian 13, codenamed "Trixie", is
> expected to be released sometime in 2024, following the usual 2-year
> release cycle.
Bookworm was released in 2023. The usual 2-year
Hello Debian users,
We are happy to announce that Debian 13, codenamed "Trixie", is
expected to be released sometime in 2024, following the usual 2-year
release cycle. The exact release date will depend on the progress of
testing and bug fixing, but we will keep you updated on the
development stat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Vincent,
Am Sonntag, dem 04.09.2022 um 01:24 +0200 schrieb Vincent Lefevre:
> As this is now in unstable, shouldn't bugs be reported to packages
> that recommend gsfonts or gsfonts-x11 so that they change them to
> fonts-urw-base35? Otherwise one
Hi,
On 2022-08-28 16:55:04 +0200, Fabian Greffrath wrote:
[...]
> A preliminary package fonts-urw-base35_20200910-3 to enable the
> transition can be found in experimental, So, in case anyone want to
> check how the transition works out, any help will be appreciated [5].
[...]
> PS: Please keep me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear fellow DDs,
I'd like to announce a transition that I am going to kick off in about
one week from today: I'd like to replace the gsfonts package with
fonts-urw-base35 and, while at it, integrate the contents of gsfonts-
x11 into the new package.
Hallo -devel,
Note that libpng1.6 is now in sid, so the libpng 1.6 transition has
finally started.
To keep the transition short, please keep an eye on packages; of course
we will also do NMUs when neeeded.
The transistion tracker is here:
https://release.debian.org/transitions/html/libpng1.6.ht
> On Mon, Jan 04, 2016 at 12:02:00PM +0100, Tobias Frost wrote:
>> we are currently planning to start the transition of libpng.
>
> Is there a repository with packages rebuilt against libpng16? Some
> dependency chains are massive, such as the gtk/gdk/... which makes
> testing fixes not possible w
On Mon, Jan 04, 2016 at 12:02:00PM +0100, Tobias Frost wrote:
> we are currently planning to start the transition of libpng.
Is there a repository with packages rebuilt against libpng16? Some
dependency chains are massive, such as the gtk/gdk/... which makes
testing fixes not possible without lar
Dear Debian-devel,
The preparation for the transition are going pretty much good.
In the meantime the bugs have been filed and there are already many
fixes uploaded. MANY THANKS for all of you.
I'm also rebuilding newly uploaded packages to keep libpng.sviech.de
somehow up to date.
Of course,
Hi,
(adding debian-boot@, debian-release@ to Cc)
Tobias Frost (2016-01-04):
> Dear debian-devel,
>
> we are currently planning to start the transition of libpng.
> The transition bug can be found here:
> https://bugs.debian.org/650601.
>
> Out of the 463 rebuilt packages 117 FTBFS with the new
In gmane.linux.debian.devel.general Tobias Frost wrote:
[...]
> (IMHO I'd love to have a real libpng-dev package which depends on the
> real thing; this would enable to version B-Ds on libpng-dev..)
The other option would be versioned provides.
cu Andreas
--
`What a good friend you are to him,
Am Mittwoch, den 06.01.2016, 01:27 +0100 schrieb Samuel Thibault:
> Rene Engelhard, on Tue 05 Jan 2016 22:15:31 +0100, wrote:
> > On Tue, Jan 05, 2016 at 09:58:03PM +0100, Rene Engelhard wrote:
> > > On Tue, Jan 05, 2016 at 09:50:58PM +0100, Samuel Thibault wrote:
> > > > Rene Engelhard, on Tue 05
Rene Engelhard, on Tue 05 Jan 2016 22:15:31 +0100, wrote:
> On Tue, Jan 05, 2016 at 09:58:03PM +0100, Rene Engelhard wrote:
> > On Tue, Jan 05, 2016 at 09:50:58PM +0100, Samuel Thibault wrote:
> > > Rene Engelhard, on Tue 05 Jan 2016 21:43:33 +0100, wrote:
> > > > So that it will immediately fail w
On Tue, Jan 05, 2016 at 09:58:03PM +0100, Rene Engelhard wrote:
> On Tue, Jan 05, 2016 at 09:50:58PM +0100, Samuel Thibault wrote:
> > Rene Engelhard, on Tue 05 Jan 2016 21:43:33 +0100, wrote:
> > > So that it will immediately fail when something eventually picks
> > > up the experimental packages
On Tue, Jan 05, 2016 at 09:50:58PM +0100, Samuel Thibault wrote:
> Rene Engelhard, on Tue 05 Jan 2016 21:43:33 +0100, wrote:
> > So that it will immediately fail when something eventually picks
> > up the experimental packages (as experimental buildds right now do in some
> > situations)?
>
> ? No
Rene Engelhard, on Tue 05 Jan 2016 21:43:33 +0100, wrote:
> So that it will immediately fail when something eventually picks
> up the experimental packages (as experimental buildds right now do in some
> situations)?
? No, experimental buildds only pick from experimental what is not
available from
On Tue, Jan 05, 2016 at 08:04:53PM +0100, Andreas Metzler wrote:
> Tobias Frost wrote:
> > For those want to test against libpng1.6:
> > Note that the libpn16 package in experimental does NOT Provide libpng-
> > dev at the moment. As I've hacked something together for my rebuild,
> > you can grab
Tobias Frost wrote:
> For those want to test against libpng1.6:
> Note that the libpn16 package in experimental does NOT Provide libpng-
> dev at the moment. As I've hacked something together for my rebuild,
> you can grab the dsc here:
> https://libpng.sviech.de/libpng_package_used/libpng1.6_1.
On Mon, Jan 4, 2016 at 9:06 PM, Simon McVittie wrote:
> https://lintian.debian.org/tags/embedded-library.html and
> https://anonscm.debian.org/viewvc/secure-testing/data/embedded-code-copies?view=co
> might be useful, although the latter seems to be outdated (it says
> libtk-img embeds libpng, whi
Am Montag, den 04.01.2016, 12:02 +0100 schrieb Tobias Frost:
For those want to test against libpng1.6:
Note that the libpn16 package in experimental does NOT Provide libpng-
dev at the moment. As I've hacked something together for my rebuild,
you can grab the dsc here:
https://libpng.sviech.de/l
Am 04.01.2016 um 14:06 schrieb Simon McVittie:
> In addition to texlive:
>
> chromium and ice* might be able to move from their embedded copies to a
> newer system copy, or not, depending whether they've patched them.
Happily Icedove isn't using here a embedded version of libpng, that's a
little
On 04/01/16 12:50, Tobias Frost wrote:
> Am Montag, den 04.01.2016, 12:00 + schrieb Bastien Roucaries:
>> Add also bug to package using embeded libpng 1.6 like texlive ?
>
> Thanks for the hint, I frankly forgot to check for code copies.
https://lintian.debian.org/tags/embedded-library.html a
Hi Tobias,
> I guess I'll drop Norbert a line for now to make him aware
> of the libpng transistion... (CC'ed)
Oh, I would be more than happy to have libpng16 in unstable!!!
I can rebuild texlive-bin at any time with system-libpng, just
need a working copy. But first I need the other libs being
Hi Sebastien,
Am Montag, den 04.01.2016, 12:00 + schrieb Bastien Roucaries:
>
>
> Add also bug to package using embeded libpng 1.6 like texlive ?
Thanks for the hint, I frankly forgot to check for code copies.
Yes, I guess the security team would be happy to drop embedded code
copies or at
Le 4 janvier 2016 12:02:00 GMT+01:00, Tobias Frost a écrit :
>Dear debian-devel,
>
>we are currently planning to start the transition of libpng.
>The transition bug can be found here:
>https://bugs.debian.org/650601.
>
>Out of the 463 rebuilt packages 117 FTBFS with the new libpng, however
>not
* Tobias Frost , 2016-01-04, 12:02:
Logs from the rebuild can be found here: http://libpng.sviech.de, as
well as a scratchpad with a short analysis:
https://titanpad.com/libpng16-transistion
Plain-text version for people who don't enjoy running non-free JS code:
https://titanpad.com/ep/pad/ex
Dear debian-devel,
we are currently planning to start the transition of libpng.
The transition bug can be found here:
https://bugs.debian.org/650601.
Out of the 463 rebuilt packages 117 FTBFS with the new libpng, however
not every failure can be attributed to the library.
Logs from the rebuild c
Hello,
On Tue, 19 Mar 2013 23:44:22 +
"brian m. carlson" wrote:
> > Well, as far as I know, mawk has some sort of terrible UTF-8
> > support, so it's a no way for many applications.
> Could you please explain? And if you haven't filed a bug report,
> could you please do so? Searching Goog
On Mon, Mar 18, 2013 at 11:23:45PM +, brian m. carlson wrote:
> If your script does require some feature that is not available in mawk
> or original-awk, you explicitly need to call gawk, since /usr/bin/awk is
> an alternative and you cannot assume that it will point to gawk.
I wonder, would a
On Tue, Mar 19, 2013 at 07:59:14AM +0100, Andrew Shadura wrote:
> On Mon, 18 Mar 2013 23:23:45 +
> "brian m. carlson" wrote:
>
> > I've seen a lot of cases over the years of packages depending on gawk
> > that do not need it. If you only need a standard nawk (new awk), you
> > do not need to
Hello,
On Mon, 18 Mar 2013 23:23:45 +
"brian m. carlson" wrote:
> I've seen a lot of cases over the years of packages depending on gawk
> that do not need it. If you only need a standard nawk (new awk), you
> do not need to depend on gawk. mawk is smaller and faster and
> sufficient for al
I've seen a lot of cases over the years of packages depending on gawk
that do not need it. If you only need a standard nawk (new awk), you do
not need to depend on gawk. mawk is smaller and faster and sufficient
for almost all needs, and the existence of some awk on the system is
guaranteed by ba
On Thu, 08 Nov 2012, Christoph Egger wrote:
> Peter Samuelson writes:
> > ...But it does bring up the question of why intel-microcode and
> > amd64-microcode are not built on kFreeBSD or the Hurd. Maybe those
> > kernels lack a CPU microcode interface?
>
> http://www.freebsd.org/doc/faq/compatib
Hi!
Peter Samuelson writes:
> ...But it does bring up the question of why intel-microcode and
> amd64-microcode are not built on kFreeBSD or the Hurd. Maybe those
> kernels lack a CPU microcode interface?
http://www.freebsd.org/doc/faq/compatibility-processors.html
Though I rather doubt the li
> On Donnerstag, 8. November 2012, Ben Hutchings wrote:
> > > And an annoying technical detail makes it suboptimal to add the microcode
> > > packages as a recommendation of the firmware-linux-nonfree package.
> > ...which is that dpkg does not support architecture-specific relations
> > in binary
Hi,
On Donnerstag, 8. November 2012, Ben Hutchings wrote:
> > And an annoying technical detail makes it suboptimal to add the
microcode
> > packages as a recommendation of the firmware-linux-nonfree package.
> ...which is that dpkg does not support architecture-specific relations
> in binary pack
On Thu, 08 Nov 2012, Carlos Alberto Lopez Perez wrote:
> On 06/11/12 17:05, Henrique de Moraes Holschuh wrote:
> > Still, it did lead me to a possible cause: I am not trying to modprobe
> > "microcode" in the intel-microcode postinst. This can indeed cause the
> > failure to update microcode at p
On 06/11/12 17:05, Henrique de Moraes Holschuh wrote:
> Still, it did lead me to a possible cause: I am not trying to modprobe
> "microcode" in the intel-microcode postinst. This can indeed cause the
> failure to update microcode at package install time.
>
> I forget why I didn't do it that way
On Thu, 2012-11-08 at 02:35 +0200, Adrian Fita wrote:
> On 08/11/12 01:44, Ben Hutchings wrote:
> > On Wed, Nov 07, 2012 at 04:33:00PM -0200, Henrique de Moraes Holschuh wrote:
> >> On Wed, 07 Nov 2012, Adrian Fita wrote:
> >>> Fair enough, but how about having the linux-image packages recommend th
On 08/11/12 01:44, Ben Hutchings wrote:
> On Wed, Nov 07, 2012 at 04:33:00PM -0200, Henrique de Moraes Holschuh wrote:
>> On Wed, 07 Nov 2012, Adrian Fita wrote:
>>> Fair enough, but how about having the linux-image packages recommend the
>>> *microcode packages for installation so users won't get
On Wed, Nov 07, 2012 at 04:33:00PM -0200, Henrique de Moraes Holschuh wrote:
> On Wed, 07 Nov 2012, Adrian Fita wrote:
> > Fair enough, but how about having the linux-image packages recommend the
> > *microcode packages for installation so users won't get confused by the
> > message caused by the m
On Wed, 07 Nov 2012, Adrian Fita wrote:
> Fair enough, but how about having the linux-image packages recommend the
> *microcode packages for installation so users won't get confused by the
> message caused by the module trying to load the file with the microcode
> update and not finding it?
I don'
On 07/11/12 02:50, Henrique de Moraes Holschuh wrote:
> On Wed, 07 Nov 2012, Adrian Fita wrote:
>> My CPU is an AMD Turion(tm)X2 Dual Core Mobile RM-76, cpu family: 17, so
>> it doesn't need the amd64-microcode package which contains microcode
>> updates only for cpu families: 10h - 14h & 15h. But
On Wed, 07 Nov 2012, Nikolaus Rath wrote:
> Henrique de Moraes Holschuh writes:
> >> > # iucode_tool --scan-system -vv
> >> > iucode_tool: cpuid kernel driver unavailable, cannot scan system
> >> > processor signatures
> >
> > Hmm, that should happen only if iucode-tool is installed/configured af
Henrique de Moraes Holschuh writes:
>> > # iucode_tool --scan-system -vv
>> > iucode_tool: cpuid kernel driver unavailable, cannot scan system processor
>> > signatures
>
> Hmm, that should happen only if iucode-tool is installed/configured after
> intel-microcode.
I've seen this message too, du
Dropping users and adding pkg-xen-devel and debian-kernel.
On Tue, 2012-11-06 at 15:43 +0100, Stephan Seitz wrote:
> On Mon, Nov 05, 2012 at 06:12:53PM -0200, Henrique de Moraes Holschuh wrote:
> >I would like to bring to your attention the improved support for system
> >processor (CPU) microcode
On Wed, 07 Nov 2012, Adrian Fita wrote:
> My CPU is an AMD Turion(tm)X2 Dual Core Mobile RM-76, cpu family: 17, so
> it doesn't need the amd64-microcode package which contains microcode
> updates only for cpu families: 10h - 14h & 15h. But the microcode kernel
Family 17 (decimal) is family 11h (he
On 05/11/12 22:12, Henrique de Moraes Holschuh wrote:
> Hello all,
>
> I would like to bring to your attention the improved support for system
> processor (CPU) microcode updates, for x86/i686/x86-64/amd64 systems
> that was recently added to [non-free] Wheezy.
>
> System Processors from Intel an
On Tue, 06 Nov 2012, Stephan Seitz wrote:
> On Mon, Nov 05, 2012 at 06:12:53PM -0200, Henrique de Moraes Holschuh wrote:
> >I would like to bring to your attention the improved support for system
> >processor (CPU) microcode updates, for x86/i686/x86-64/amd64 systems
> >that was recently added to [
On Tue, 06 Nov 2012, Jon Dowland wrote:
> On Mon, Nov 05, 2012 at 06:12:53PM -0200, Henrique de Moraes Holschuh wrote:
> > Microcode updates will be applied immediately when the microcode
> > packages are installed or updated: you don't have to reboot. You will
> > have to keep the packages instal
On Mon, Nov 05, 2012 at 06:12:53PM -0200, Henrique de Moraes Holschuh wrote:
I would like to bring to your attention the improved support for system
processor (CPU) microcode updates, for x86/i686/x86-64/amd64 systems
that was recently added to [non-free] Wheezy.
Alas, this will not work for XE
On Mon, Nov 05, 2012 at 06:12:53PM -0200, Henrique de Moraes Holschuh wrote:
> Microcode updates will be applied immediately when the microcode
> packages are installed or updated: you don't have to reboot. You will
> have to keep the packages installed, though: as explained above, the
> microcode
Hello all,
I would like to bring to your attention the improved support for system
processor (CPU) microcode updates, for x86/i686/x86-64/amd64 systems
that was recently added to [non-free] Wheezy.
System Processors from Intel and AMD may need updates to their microcode
(sort of a control sequenc
Bug Squashing Party in Dublin
=
http://wiki.debian.org/BSP/2012/11/ie/Dublin
Come and help get Wheezy released, a second time!
After the success of the first Irish Debian BSP, we're holding a
second one in November. We will gather to collectively fix bugs and
help each
On Tue, Nov 11, 2008 at 10:10:37AM +1100, Brian May wrote:
> I saw the name and initially thought it was related to blender.
[...]
It struck me as a coffee reference, since the term often gets used
to describe blends of coffee beans from the same region. Then again,
perhaps I drink too much coffee
Neil Williams wrote:
> On Mon, 2008-11-10 at 13:28 +0100, Andreas Tille wrote:
>> On Mon, 10 Nov 2008, Neil Williams wrote:
>>
>>> I guess what are talking about here is the mirrors. Do all Blends use
>>> unchanged Debian mirrors?
>> Yes. What else would you expect if it says _inside_ Debian? A D
On Tue, 11 Nov 2008, Daniel Baumann wrote:
to avoid such things, especially with defining naming terminology for
things that covers such broad aspects of debian, a poll on your
sub-project only mailinglists is probably not enough, and imho at least
one of either d-devel or d-project should be CC
Andreas Tille wrote:
> Your remark above just ignores that the concept tries to profit from
> synergies inside these projects which for instance are reflected in
> these tasks or bugs pages, a common technique to build metapackages etc.
that's not my point; my point is that i don't see why a bunch
Miriam Ruiz wrote:
I'm not exactly sure that I like the new name, to be honest.
I saw the name and initially thought it was related to blender.
http://www.blender.org/
Brian May
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTE
Le Mon, Nov 10, 2008 at 01:51:05PM +, Neil Williams a écrit :
> That is where I found "Blends" confusing - it conjures up images of
> mixing two different things into one.
This tempts me a lot to mix stable and backports.debian.org (once it exists) in
our shiny new blender :)
By the way, I re
2008/11/10 Miriam Ruiz <[EMAIL PROTECTED]>:
> that I don't particurally like the game, but if it has been voted and
s/game/name/
Sorry,
Miry
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
2008/11/10 Andreas Tille <[EMAIL PROTECTED]>:
> On Mon, 10 Nov 2008, Miriam Ruiz wrote:
>
>> I'm not exactly sure that I like the new name, to be honest.
>
> Well, the renaming was announced on debian-custom list and all lists
> of existing CDDs (also for instance on Debian Junior list[1]). And,
>
On Mon, 2008-11-10 at 13:28 +0100, Andreas Tille wrote:
> On Mon, 10 Nov 2008, Neil Williams wrote:
>
> > I guess what are talking about here is the mirrors. Do all Blends use
> > unchanged Debian mirrors?
>
> Yes. What else would you expect if it says _inside_ Debian? A Debian
> Pure Blend has
ugh people are so keen on all this naming issues that the
technical part in the beginning of the announcement did not deserved
any comment so far. This fits perfectly into my observation that the
thread about renaming on the CDD list attracted more people than any
other technical topic before.
Y
Andreas Tille wrote:
> Yes. What else would you expect if it says _inside_ Debian? A Debian
> Pure Blend has no separate mirror - THIS is the basic idea of the concept.
so then call them 'Debian Foo' team, since this is what they are and no
different to the various teams we have already (where s
On Mon, 10 Nov 2008, Neil Williams wrote:
I guess what are talking about here is the mirrors. Do all Blends use
unchanged Debian mirrors?
Yes. What else would you expect if it says _inside_ Debian? A Debian
Pure Blend has no separate mirror - THIS is the basic idea of the concept.
If so, w
On Mon, 2008-11-10 at 12:32 +0100, Andreas Tille wrote:
> On Mon, 10 Nov 2008, Neil Williams wrote:
>
> > I was never particularly clear on why "Custom" was a bad name to use.
>
> Actually "distribution" was the worst part of the old name.
ok
> Before we have another round of discussing names:
On Mon, 10 Nov 2008, Neil Williams wrote:
I was never particularly clear on why "Custom" was a bad name to use.
Actually "distribution" was the worst part of the old name.
Before we have another round of discussing names: Could everybody
who is really interested in the projects please have a
On Mon, Nov 10, 2008 at 8:07 PM, Neil Williams <[EMAIL PROTECTED]> wrote:
> I'm confused by the new name - what are we blending and why confuse
> "Pure" and "Blend" in the same name?
>
> Emdebian is a customised Debian too - we will have two flavours soon, a
> functionally-identical but smaller De
On Mon, 10 Nov 2008, Miriam Ruiz wrote:
We realised that the old name Custom Debian Distributions just sended
the wrong message to outsiders: The conclusion that CDDs are something
else than Debian was to "obvious" if people did not read the relevant
documentation. So we finally found a raw con
On Mon, 10 Nov 2008, Adeodato Simó wrote:
What does "raw consensus" mean here? It doesn't seem to be an existing
English idiom... :-) [Maybe you meant "rough", I don't know.]
Yes, sorry - I intended to writh rough (perhaps I should ask co authors
for announcements next time).
In practice the
On Mon, 10 Nov 2008, Stefano Zacchiroli wrote:
On Mon, Nov 10, 2008 at 10:26:46AM +0100, Andreas Tille wrote:
Renaming Custom Debian Distributions to Debian Pure Blend
- -
[3] http://cdd.alioth.debian.org/blends
^^^
On Mon, 2008-11-10 at 11:53 +0100, Miriam Ruiz wrote:
> 2008/11/10 Andreas Tille <[EMAIL PROTECTED]>:
>
> > We realised that the old name Custom Debian Distributions just sended
> > the wrong message to outsiders: The conclusion that CDDs are something
> > else than Debian was to "obvious" if peop
2008/11/10 Andreas Tille <[EMAIL PROTECTED]>:
> We realised that the old name Custom Debian Distributions just sended
> the wrong message to outsiders: The conclusion that CDDs are something
> else than Debian was to "obvious" if people did not read the relevant
> documentation. So we finally fou
* Andreas Tille [Mon, 10 Nov 2008 10:26:46 +0100]:
> Hello,
Hi Andreas,
> So we finally found a raw consensus for a new name:
> Debian Pure Blends
What does "raw consensus" mean here? It doesn't seem to be an existing
English idiom... :-) [Maybe you meant "rough", I don't know.]
Chee
On Mon, Nov 10, 2008 at 10:26:46AM +0100, Andreas Tille wrote:
> Renaming Custom Debian Distributions to Debian Pure Blend
> - -
> [3] http://cdd.alioth.debian.org/blends
^^^
.oO( Have you thought about renaming the
Olivier Berger <[EMAIL PROTECTED]> (28/07/2008):
> I haven't noticed any announcement sent to [EMAIL PROTECTED] about "Debian
> GNU/Linux 4.0 updated and support for newer hardware added"
> (http://lists.debian.org/debian-announce/2008/msg3.html) ...
> mayb
Hi.
I haven't noticed any announcement sent to [EMAIL PROTECTED] about "Debian
GNU/Linux 4.0 updated and support for newer hardware
added" (http://lists.debian.org/debian-announce/2008/msg3.html) ...
maybe this is a user news mostly, but doesn't hurt to notify devs
On Fri, Mar 14, 2008 at 06:14:26AM +0200, Guillem Jover wrote:
> I seems I'll need to clarify this as well
To be honest, I'd love to see you ignore this entire thread if it means
you'll spend time whipping the triggers stuff into whatever shape you
think it needs to be in to go into sid.
Perhaps
On Wed, 2008-03-12 at 10:01:35 +, Ian Jackson wrote:
> Guillem Jover writes ("Re: dpkg semi-hijack - an announcement (also,
> triggers)"):
> > On Mon, 2008-03-10 at 14:42:48 +1000, Anthony Towns wrote:
> > > Against the wishes of, afaict, Guillem and Raphael
* Mike Bird
| Please recall that Ian wrote dpkg (replacing Murdock's earlier
| PERL dpkg). Ian knows dpkg better than any of the current team.
Ian had one upload of dpkg after September 1996, which was in 1998
before he suddenly regained interest in it about a year or so ago. I'm
not questionin
Le Thursday 13 March 2008 15:32:18 John Goerzen, vous avez écrit :
> > Right. But currently, this has a good chance to keep Triggers out of
> > lenny, which is a bloody shame.
>
> I understand, which is my point. People need to get a sense of
> perspective. What is the more important goal: trigg
On Thu March 13 2008 8:34:19 am Marc Haber wrote:
> On Wed, 12 Mar 2008 07:58:15 -0600, John Goerzen
>
> <[EMAIL PROTECTED]> wrote:
> >I think both you and Ian are making a mountain out of a molehill here.
> > So what if the history isn't pretty? It won't impact anybody running
> > dpkg. It like
On Wed, 12 Mar 2008 07:58:15 -0600, John Goerzen
<[EMAIL PROTECTED]> wrote:
>I think both you and Ian are making a mountain out of a molehill here. So
>what if the history isn't pretty? It won't impact anybody running dpkg. It
>likely won't even impact the people hacking on dpkg. In fact, 2 y
Andreas Tille writes ("Re: dpkg semi-hijack - an announcement (also,
triggers)"):
> Well, I don't want to interrupt your guys thrilling discussion
> about indentation of source code and I can not really imagine
> that you are not aware of
> apt-cache show i
John Goerzen writes ("Re: dpkg semi-hijack - an announcement (also, triggers)"):
> I think both you and Ian are making a mountain out of a molehill here. So
> what if the history isn't pretty? It won't impact anybody running dpkg. It
> likely won't even impa
Hi,
On Wed, 2008-03-12 at 11:16 -0700, Mike Bird wrote:
> Ian appears to have chosen to speak truth to power rather than
> forking. Do you have a constructive alternative to suggest?
$ echo ":/dpkg/i" >> ~/.killfile
William
signature.asc
Description: This is a digitally signed message part
On Wed March 12 2008 10:26:52 Luk Claes wrote:
> Ian Jackson wrote:
> > It would be flogging a dead horse if we didn't have the core packaging
> > software maintained by an obstructive and naive programmer supported
> > by someone who is more interested in pretty revision logs than good
> > code.
>
Ian Jackson wrote:
> William Pitcock writes ("Re: dpkg semi-hijack - an announcement (also,
> triggers)"):
>> On Tue, 2008-03-11 at 22:06 -0700, Mike Bird wrote:
>>> It's easy to see negatives such as making it harder to merge
>>> long-awaited fe
On Tue March 11 2008 10:45:43 pm Guillem Jover wrote:
> Anyway, after the freeze was announced it was clear that Ian was not
> going to fix the branch, and because having this feature for lenny is
> highly desirable I was just going to have to fix it myself and review
> during that process, but got
On Wed, Mar 12, 2008 at 01:19:58PM +0100, Robert Millan wrote:
>
> And most importantly, you wouldn't contemplate deploying somewhere else an
> implementation of triggers that hasn't been accepted in dpkg, because of the
> danger of creating (and maintaining) a sustained incompatibility.
Oh wait,
On Wed, Mar 12, 2008 at 10:01:35AM +, Ian Jackson wrote:
> > On Mon, 2008-03-10 at 14:42:48 +1000, Anthony Towns wrote:
> > > Against the wishes of, afaict, Guillem and Raphael, Ian's made applying
> > > his triggers patch dependent on:
> > >
> > > - reversion to two space indenting
>
> The
On Wed, 12 Mar 2008, Ian Jackson wrote:
The history of this change is as follows:
* At some point, without any kind of discussion, Guillem
unilaterally reformats several files to 8-character indents.
...
Well, I don't want to interrupt your guys thrilling discussion
about indentation of so
Le mercredi 12 mars 2008 à 10:01 +, Ian Jackson a écrit :
> Guillem Jover writes ("Re: dpkg semi-hijack - an announcement (also,
> triggers)"):
> > I'd like to clarify few more things, which have been brough up the past
> > few days. Even if I don
Guillem Jover writes ("Re: dpkg semi-hijack - an announcement (also,
triggers)"):
> I'd like to clarify few more things, which have been brough up the past
> few days. Even if I don't usually accept open invitations to flamefests
> (re the OP).
Guillem emerges! At
1 - 100 of 236 matches
Mail list logo
