On 04/05/2016 05:32 PM, Ben Hutchings wrote:
On Tue, 2016-04-05 at 17:19 +0200, Mathieu Malaterre wrote:
[CC me please]
I am trying to find a user-friend solution to :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790694#52
Apparently the few people with G5+nvidia card out there cannot ge
oldsys-preseed_3.21_i386.changes uploaded successfully to localhost
along with the files:
oldsys-preseed_3.21.dsc
oldsys-preseed_3.21.tar.xz
oldsys-preseed_3.21_i386.udeb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
oldsys-preseed_3.21_i386.changes uploaded successfully to ftp-master.debian.org
along with the files:
oldsys-preseed_3.21.dsc
oldsys-preseed_3.21.tar.xz
oldsys-preseed_3.21_i386.udeb
Greetings,
Your Debian queue daemon (running on host coccia.debian.org)
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 06 Apr 2016 08:36:09 +0200
Source: oldsys-preseed
Binary: oldsys-preseed
Architecture: source i386
Version: 3.21
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
Changed-By: Christian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Begin forwarded message:
Date: Tue, 5 Apr 2016 12:08:08 -0700
From: Andrew Kurn
To: bugs.andreas.glae...@freenet.de
Subject: Re: Bug#755230 closed by Andreas Glaeser
Thanks for your attention to this matter.
I agree with you that there is no nee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello, there,
I forwarded your message to the respective bug-report.
In my opinion the workaround, which I don't fully understand to be honest, does
not have
much relevance for the PC-platform, since most BIOSes do boot from USB
nowadays, often
eve
Your message dated Wed, 6 Apr 2016 11:22:43 +0200
with message-id <20160406112243.38c71841@a68n.lokal>
and subject line Issue resolved
has caused the Debian Bug report #741197,
regarding installation-reports
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 6 Apr 2016 11:57:02 +0200
with message-id <20160406115702.46c7e55e@a68n.lokal>
and subject line Report acknowledged
has caused the Debian Bug report #741137,
regarding installation-reports
to be marked as done.
This means that you claim that the problem has been dealt with.
Control: reassign -1 src:blends
Control: tag -1 pending
I have created the package mentioned in my last mail in the blends git
repository:
https://anonscm.debian.org/cgit/blends/blends.git/
Package: blends-tasks
Architecture: all
Priority: important
Section: misc
Depends: tasksel
Description: De
Processing control commands:
> reassign -1 src:blends
Bug #758116 [tasksel] tasksel: Allow to select Blends selection during
installation - just "DE", "Web server", "Mail server" is NOT enough
Bug reassigned from package 'tasksel' to 'src:blends'.
No longer marked as found in versions tasksel/3.1
On Wed, Apr 06, 2016 at 09:22:44AM +0200, gianluca wrote:
> In this case during install it should be possible to use nouveaufb instead
> of nouveau. It is a minor issue and during install I clearly see no
> performance penalty.
>
> Nope. It looks like to say to people: your server which is running
Hi,
I've made some changes to tasksel recently, which I've pushed to the
repository. As there were some errors when pushing, I guess no mail was sent
to the list (not sure if it's usually the case anyway), so I'm sending a mail
to notify you. There's no urgency to the upload.
Here is the dpkg-par
Package: console-setup
Version: 1.123
Severity: minor
Dear Maintainer,
In fr_FR.UTF-8 charset, Lat15 for console-setup or also guest charset,
console-setup change the non-breaking space in the boot message of systemd to
garbage character.
The first line of message on the boot screen says about
On Wed, Apr 06, 2016 at 07:02:03PM +0200, rpnpif wrote:
>
> In fr_FR.UTF-8 charset, Lat15 for console-setup or also guest charset,
> console-setup change the non-breaking space in the boot message of
> systemd to garbage character.
Unfortunately, at the moment I have no idea what might have cau
On Thu, Apr 07, 2016 at 01:06:10AM +0300, Anton Zinoviev wrote:
>
> Unfortunately, at the moment I have no idea what might have caused this
> strange behaviour.
Ah, it just occured to me that maybe you have observed the following:
1. fsck displays its messages with correct non-break space.
2.
Caso não consiga visualizar esta newsletter, clique aqui
Esta mensagem é enviada sob a nova legislação sobre correio Electrónico, Secção
301, Parágrafo (a) (2) (c) Decreto S 1618, Título Terceiro aprovado pelo 105º
Congresso Base das Normativas Internacionais sobre o SPAM. "Um e-mail não
poderá
Package: installation-reports
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this a
17 matches
Mail list logo
