Bug#1069019: rustc: request to upgrade to 1.71.0 or later

2024-04-15 Thread WANG Rui
Source: rustc
Version: 1.70.0+dfsg1-9
Severity: normal

Dear Maintainer,

I am the maintainer for the Rust LoongArch target, and I am reporting a build
failure issue with `rustc` on LoongArch64. I am seeking your assistance in
addressing this issue.

In Rust compiler v1.71.0, the `loongarch64-unknown-linux-gnu` target was 
promoted
to tier 2. If we were able to upgrade to 1.71.0 or later, this would easily 
resolve
the loongarch64 build issue.

Release notes: https://github.com/rust-lang/rust/releases/tag/1.71.0

-- System Information:
Debian Release: trixie/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: loong64 (loongarch64)

Kernel: Linux 6.8.5 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect



Bug#1061131: Acknowledgement (Package does not purge quite well, but maybe could.)

2024-01-18 Thread Rui Damas
I just went to check about the libvirt-qemu group removal warning...
grep libvirt-qemu /etc/group ... o.O?... and there is not such
group... seams it got removed anyway, so why the warning?...

On 1/19/24, Debian Bug Tracking System  wrote:
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1061131:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061131.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian Libvirt Maintainers
> 
>
> If you wish to submit further information on this problem, please
> send it to 1061...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1061131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061131
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>



Bug#1061131: Package does not purge quite well, but maybe could.

2024-01-18 Thread Rui Damas
Package: libvirt-daemon-system
Version: 9.0.0-4

I installed this package by mistake, by installing virt-manager with
recommends... so i purged virt-manager (and dependencies) to then
reinstall it.

... and noticed the following warnings:

Purging configuration files for libvirt-daemon-system (9.0.0-4) ...
userdel: group libvirt-qemu not removed because it is not the primary
group of user libvirt-qemu.
dpkg: warning: while removing libvirt-daemon-system, directory
'/var/lib/libvirt/qemu' not empty so not removed

O.o ... think that there is no need for the '/var/lib/libvirt/qemu'
not empty, since it only contains another empty directory inside:
/var/lib/libvirt/qemu/checkpoint/

As for the group libvirt-qemu complain, i have no idea about it

ps: similar happens to libvirt-daemon-config-nwfilter, for which i
will also fill a bug report.



Bug#1061132: Package does not purge quite well, but maybe could.

2024-01-18 Thread Rui Damas
Package: libvirt-daemon-config-nwfilter
Version: 9.0.0-4

I installed this package by mistake, by installing virt-manager with
recommends... so i purged virt-manager (and dependencies) to then
reinstall it.

... and noticed the following warning:

Purging configuration files for libvirt-daemon-config-nwfilter (9.0.0-4) ...
dpkg: warning: while removing libvirt-daemon-config-nwfilter,
directory '/etc/libvirt' not empty so not removed

O.o ... think that there is no need for the '/etc/libvirt' not empty,
since it only contains another empty directory inside:
/etc/libvirt/secrets/

ps: similar happens to libvirt-daemon-system, for which i will also
fill a bug report.



Bug#1060910: rust-cty: fails to build rust-cty on loong64

2024-01-16 Thread WANG Rui
Source: rust-cty
Version: 0.2.1-1
Severity: normal

Dear Maintainer,

I am the maintainer for the Rust LoongArch target, and I am reporting a build
failure issue with `rust-cty` on LoongArch64. I am seeking your assistance in
addressing this issue.

I am aware that the build failure is due to the lack of LoongArch support in
`cty`. Previously, I attempted to submit a pull request to the upstream `cty`
project to address the issue. However, the project is no longer maintained, so
I kindly request your help in incorporating a fix patch into the Debian project.
The fix is a single line of code.

PR: https://github.com/japaric/cty/pull/23

-- System Information:
Debian Release: trixie/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: loong64 (loongarch64)

Kernel: Linux 6.6.8 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect



Bug#1042394: More thoughs on bash --rcfile

2023-07-30 Thread Rui Damas
Just also noticed that 'bash --rcfile' returns an 'option requires an
argument' error... as expected, of course... :) ... but ::: it just
feels strange when the argument may be invalid and just ignored...
like ::: 'bash --rcfile ""' ... or 'bash --rcfile "non-existing"'.

again... if this is supposed to be expected from --rcfile and
--init-file... i suggest adding a --existing-rcfile... :) ... or just
give other use to the redundant --init-file and get it to complain
about a missing file.

On 7/27/23, Rui Damas  wrote:
> Just noticed...
>
> The subject of this bug is supposed to be:
>
>   Bash does NOT complain of a missing file given for options: --rcfile
> or --init-file
>
> & sorry about that...
>
> On 7/27/23, Debian Bug Tracking System  wrote:
>> Thank you for filing a new Bug report with Debian.
>>
>> You can follow progress on this Bug here: 1042394:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042394.
>>
>> This is an automatically generated reply to let you know your message
>> has been received.
>>
>> Your message is being forwarded to the package maintainers and other
>> interested parties for their attention; they will reply in due course.
>>
>> Your message has been sent to the package maintainer(s):
>>  Matthias Klose 
>>
>> If you wish to submit further information on this problem, please
>> send it to 1042...@bugs.debian.org.
>>
>> Please do not send mail to ow...@bugs.debian.org unless you wish
>> to report a problem with the Bug-tracking system.
>>
>> --
>> 1042394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042394
>> Debian Bug Tracking System
>> Contact ow...@bugs.debian.org with problems
>>
>



Bug#1042394: Acknowledgement (Bash does complain of a missing file fiven for options: --rcfile or --init-file)

2023-07-27 Thread Rui Damas
Just noticed...

The subject of this bug is supposed to be:

  Bash does NOT complain of a missing file given for options: --rcfile
or --init-file

& sorry about that...

On 7/27/23, Debian Bug Tracking System  wrote:
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1042394:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042394.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Matthias Klose 
>
> If you wish to submit further information on this problem, please
> send it to 1042...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1042394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042394
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>



Bug#1042394: Bash does complain of a missing file fiven for options: --rcfile or --init-file

2023-07-27 Thread Rui Damas
Package: bash
Version: 5.2.15-2+b2

problem: when using the option --rcfile or --init-file, no matter
weather the file path given is valid or not... it will load the file
if is present... :) ... and will just ignore the file (and without
loading the default ~/.bashrc)... :( ... while i expected it to exit
with an error and saying like ::: given rcfile 'non/existing/file' not
found.

my current work around: make a wrapper that checks for the file existence... :(

While in the manual says nothing about this being supposed to
happen... it just says:

"When  an interactive shell that is not a login shell is started, bash
reads and executes commands from /etc/bash.bashrc and ~/.bashrc, if
these files exist.  This may be inhibited by using the --norc option.
The --rcfile file option will force bash to read and execute commands
from file instead of /etc/bash.bashrc and ~/.bashrc."

Thoughts on this...

O.o ... as bash (with no --rcfile) ignores ~/.bashrc if it does not
exist... :) ... maybe is supposed to behave like that... though
strange, since the it is being specified.

.. but if that is the case, then i would suggest that with --rcfile
behaves as it does now... but with --init-file (that now behaves as
--rc-file) would make the check for it's file (argument) existence.

[ bom dia ], r



Bug#1022559: firmware-misc-nonfree: With firmware-misc-nonfree instaled, system crashes (complete freeze/lockup) every few minutes

2022-12-23 Thread Rui Dinis
Hi.

Installed the new firmware-nonfree 20221214-1 unstable and Debian still
crashes after a few minutes/hours. The machine completely freezes/locks up.
The graphic card is not defective, installed windows to test, played a few
games, and had no issue in windows (I hate windows). Tried with Linux Mint
with proprietary drivers, and no issues, works flawless, no crashes or
issues in games with wine and games with a virtual machine.
This is a SERIOUS problem and after a few months, the issue is not solved.

Regards
Rui Dinis


-Original Message-
From: Rui Dinis  
Sent: Tuesday, November 22, 2022 10:04
To: '1022...@bugs.debian.org' <1022...@bugs.debian.org>
Subject: RE: Bug#1022559: firmware-misc-nonfree: With firmware-misc-nonfree
instaled, system crashes (complete freeze/lockup) every few minutes

Hi.

Installed the new firmware-nonfree 20221109-2 (unstable) and Debian still
crashes after a few minutes/hours. The machine completely freezes/locks up.

Regards
Rui Dinis



AVISO: A mensagem e eventuais anexos são suscetíveis de conter informação
sujeita a sigilo profissional, ao regime legal de proteção de dados
pessoais, de direitos de autor ou outro, pelo que a sua divulgação depende
de autorização do remetente. No caso de esta mensagem ser recebida com erro
ou por destinatários indevidos, solicita-se a sua destruição e subsequente
aviso ao remetente da mensagem. É expressamente proibido o uso, a
distribuição, a impressão, a cópia ou qualquer outra forma de difusão não
autorizada desta mensagem e respetivos anexos. A mensagem pode ter sido
intercetada, alterada ou chegar ao seu destinatário num momento posterior ao
pretendido e com vírus.


-Original Message-
From: Diederik de Haas 
Sent: Friday, November 11, 2022 20:48
To: Rui Dinis ; 1022...@bugs.debian.org
Subject: Re: Bug#1022559: firmware-misc-nonfree: With firmware-misc-nonfree
instaled, system crashes (complete freeze/lockup) every few minutes

Control: tag -1 -moreinfo upstream
Control: found -1 20221012-1

On Friday, 11 November 2022 20:41:56 CET Rui Dinis wrote:
> After further testing with firmware-misc-nonfree 20220913-1 and 
> firmware-misc-nonfree 20221012-1, the problem still persists the 
> machine crashes after several minutes or hours.
> Without this firmware installed, the machine never crashes, is rock solid!

Thanks for testing and reporting back.

> Would it possible to explain me why would the new version correct the 
> problem that I'm having with these crashes?

There were 2 new versions of the firmware then what you reported against and
it could have been that your issue was fixed in the meantime.
Now we know it was not.

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
log/nvidia
actually only shows 1 commit in which new firmware was added, thus no update
to existing ones, so if I had checked that before, I could've known.

What remains is reporting this 'upstream' (to nvidia), but I don't know
where that should be done. Hopefully someone else does.

One reason I didn't check is that I never saw the additional information you
did supply, so for completeness sake, I'll quote that below:

On Sun, 23 Oct 2022 22:10:51 +0100 "Rui Dinis" 
wrote:
> Here is some aditional information.
> 
> I have a Nvidia Zotac 1080TI mini. With firmware-misc-nonfree 
> installed, system crashes (complete freeze/lockup, no errors on
> screen) every few minutes/hours, and the only solution is a reset. 
> Without firmware-misc-nonfree, never crashes.
> 
> The package version of firmware-misc-nonfree is 20210818-1
> 
> I'm using 4 screens connected to my Nvidia Graphic Card, and I'm with 
> KDE Plasma.
> 
> Without the package firmware-misc-nonfree installed, the systems 
> throws this errors, but it never crashes:
> 
> # journalctl -b | grep firmware
> 
> Oct 23 20:08:23 Blackbeard kernel: nouveau :01:00.0: firmware: 
> failed to load nvidia/gp102/nvdec/scrubber.bin (-2) Oct 23 20:08:23 
> Blackbeard kernel: nouveau :01:00.0: firmware: failed to load 
> nvidia/gp102/acr/bl.bin (-2) Oct 23 20:08:23 Blackbeard kernel:
> nouveau :01:00.0: firmware: failed to load nvidia/gp102/acr/bl.bin
> (-2) Oct 23 20:08:23 Blackbeard kernel: nouveau :01:00.0: acr: 
> firmware unavailable Oct 23 20:08:23 Blackbeard kernel: nouveau
> :01:00.0: pmu: firmware unavailable Oct 23 20:08:23 Blackbeard
> kernel: nouveau :01:00.0: gr: firmware unavailable Oct 23 20:08:23 
> Blackbeard kernel: nouveau :01:00.0: sec2: firmware unavailable
> 
> # inxi -G
> Graphics:
>   Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] driver: nouveau v: kernel
>   Device-2: Microdia Camera type: USB driver: snd-usb-audio,uvcvideo



Bug#1022559: firmware-misc-nonfree: With firmware-misc-nonfree instaled, system crashes (complete freeze/lockup) every few minutes

2022-11-22 Thread Rui Dinis
Hi.

Installed the new firmware-nonfree 20221109-2 (unstable) and Debian still
crashes after a few minutes/hours. The machine completely freezes/locks up.

Regards
Rui Dinis



AVISO: A mensagem e eventuais anexos são suscetíveis de conter informação
sujeita a sigilo profissional, ao regime legal de proteção de dados
pessoais, de direitos de autor ou outro, pelo que a sua divulgação depende
de autorização do remetente. No caso de esta mensagem ser recebida com erro
ou por destinatários indevidos, solicita-se a sua destruição e subsequente
aviso ao remetente da mensagem. É expressamente proibido o uso, a
distribuição, a impressão, a cópia ou qualquer outra forma de difusão não
autorizada desta mensagem e respetivos anexos. A mensagem pode ter sido
intercetada, alterada ou chegar ao seu destinatário num momento posterior ao
pretendido e com vírus.


-Original Message-
From: Diederik de Haas  
Sent: Friday, November 11, 2022 20:48
To: Rui Dinis ; 1022...@bugs.debian.org
Subject: Re: Bug#1022559: firmware-misc-nonfree: With firmware-misc-nonfree
instaled, system crashes (complete freeze/lockup) every few minutes

Control: tag -1 -moreinfo upstream
Control: found -1 20221012-1

On Friday, 11 November 2022 20:41:56 CET Rui Dinis wrote:
> After further testing with firmware-misc-nonfree 20220913-1 and 
> firmware-misc-nonfree 20221012-1, the problem still persists the 
> machine crashes after several minutes or hours.
> Without this firmware installed, the machine never crashes, is rock solid!

Thanks for testing and reporting back.

> Would it possible to explain me why would the new version correct the 
> problem that I'm having with these crashes?

There were 2 new versions of the firmware then what you reported against and
it could have been that your issue was fixed in the meantime.
Now we know it was not.

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
log/nvidia
actually only shows 1 commit in which new firmware was added, thus no update
to existing ones, so if I had checked that before, I could've known.

What remains is reporting this 'upstream' (to nvidia), but I don't know
where that should be done. Hopefully someone else does.

One reason I didn't check is that I never saw the additional information you
did supply, so for completeness sake, I'll quote that below:

On Sun, 23 Oct 2022 22:10:51 +0100 "Rui Dinis" 
wrote:
> Here is some aditional information.
> 
> I have a Nvidia Zotac 1080TI mini. With firmware-misc-nonfree 
> installed, system crashes (complete freeze/lockup, no errors on 
> screen) every few minutes/hours, and the only solution is a reset. 
> Without firmware-misc-nonfree, never crashes.
> 
> The package version of firmware-misc-nonfree is 20210818-1
> 
> I'm using 4 screens connected to my Nvidia Graphic Card, and I'm with 
> KDE Plasma.
> 
> Without the package firmware-misc-nonfree installed, the systems 
> throws this errors, but it never crashes:
> 
> # journalctl -b | grep firmware
> 
> Oct 23 20:08:23 Blackbeard kernel: nouveau :01:00.0: firmware: 
> failed to load nvidia/gp102/nvdec/scrubber.bin (-2) Oct 23 20:08:23 
> Blackbeard kernel: nouveau :01:00.0: firmware: failed to load 
> nvidia/gp102/acr/bl.bin (-2) Oct 23 20:08:23 Blackbeard kernel: 
> nouveau :01:00.0: firmware: failed to load nvidia/gp102/acr/bl.bin 
> (-2) Oct 23 20:08:23 Blackbeard kernel: nouveau :01:00.0: acr: 
> firmware unavailable Oct 23 20:08:23 Blackbeard kernel: nouveau 
> :01:00.0: pmu: firmware unavailable Oct 23 20:08:23 Blackbeard 
> kernel: nouveau :01:00.0: gr: firmware unavailable Oct 23 20:08:23 
> Blackbeard kernel: nouveau :01:00.0: sec2: firmware unavailable
> 
> # inxi -G
> Graphics:
>   Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] driver: nouveau v: kernel
>   Device-2: Microdia Camera type: USB driver: snd-usb-audio,uvcvideo



Bug#1022559: firmware-misc-nonfree: With firmware-misc-nonfree instaled, system crashes (complete freeze/lockup) every few minutes

2022-11-11 Thread Rui Dinis
Hi.

After further testing with firmware-misc-nonfree 20220913-1 and
firmware-misc-nonfree 20221012-1, the problem still persists the machine
crashes after several minutes or hours.
Without this firmware installed, the machine never crashes, is rock solid!

Would it possible to explain me why would the new version correct the
problem that I'm having with these crashes?

Thanks in advance.

-Original Message-
From: Diederik de Haas  
Sent: Friday, October 28, 2022 23:54
To: the.wingmanx ; 1022...@bugs.debian.org
Subject: Re: Bug#1022559: firmware-misc-nonfree: With firmware-misc-nonfree
instaled, system crashes (complete freeze/lockup) every few minutes

Control: tag -1 moreinfo

On Sunday, 23 October 2022 22:51:09 CEST the.wingmanx wrote:
> Package: firmware-misc-nonfree
> Version: 20210818-1

Can you verify whether the issue is fixed with version 20220913-1 ?



Bug#1022559: Acknowledgement (firmware-misc-nonfree: With firmware-misc-nonfree instaled, system crashes (complete freeze/lockup) every few minutes)

2022-10-23 Thread Rui Dinis
Hi.

 

Here is some aditional information.

 

I have a Nvidia Zotac 1080TI mini. With firmware-misc-nonfree installed,
system crashes (complete freeze/lockup, no errors on screen) every few
minutes/hours, and the only solution is a reset. Without
firmware-misc-nonfree, never crashes.

 

The package version of firmware-misc-nonfree is 20210818-1

 

I'm using 4 screens connected to my Nvidia Graphic Card, and I'm with KDE
Plasma.

 

Without the package firmware-misc-nonfree installed, the systems throws this
errors, but it never crashes:

# journalctl -b | grep firmware

Oct 23 20:08:23 Blackbeard kernel: nouveau :01:00.0: firmware: failed to
load nvidia/gp102/nvdec/scrubber.bin (-2)

Oct 23 20:08:23 Blackbeard kernel: nouveau :01:00.0: firmware: failed to
load nvidia/gp102/acr/bl.bin (-2)

Oct 23 20:08:23 Blackbeard kernel: nouveau :01:00.0: firmware: failed to
load nvidia/gp102/acr/bl.bin (-2)

Oct 23 20:08:23 Blackbeard kernel: nouveau :01:00.0: acr: firmware
unavailable

Oct 23 20:08:23 Blackbeard kernel: nouveau :01:00.0: pmu: firmware
unavailable

Oct 23 20:08:23 Blackbeard kernel: nouveau :01:00.0: gr: firmware
unavailable

Oct 23 20:08:23 Blackbeard kernel: nouveau :01:00.0: sec2: firmware
unavailable

 

# inxi -G

Graphics:

  Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] driver: nouveau v: kernel

  Device-2: Microdia Camera type: USB driver: snd-usb-audio,uvcvideo

  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting

unloaded: fbdev,vesa dri: swrast gpu: nouveau resolution: 1:
1920x1080~60Hz

2: 1920x1080~60Hz 3: 1920x1080~60Hz 4: 1920x1080~60Hz

 OpenGL: renderer: llvmpipe (LLVM 14.0.6 256 bits) v: 4.5 Mesa 22.2.0

 

$ glxinfo|egrep "OpenGL vendor|OpenGL renderer"

OpenGL vendor string: Mesa/X.org

OpenGL renderer string: llvmpipe (LLVM 14.0.6, 256 bits)

 

$ lspci | grep -i "nvidia"

01:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX
1080 Ti] (rev a1)

01:00.1 Audio device: NVIDIA Corporation GP102 HDMI Audio Controller (rev
a1)

 

Thanks.

 

Regards

 

 

 

 

Thank you for filing a new Bug report with Debian.

 

You can follow progress on this Bug here: 1022559:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022559.

 

This is an automatically generated reply to let you know your message has
been received.

 

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

 

Your message has been sent to the package maintainer(s):

Debian Kernel Team < 
debian-ker...@lists.debian.org>

 

If you wish to submit further information on this problem, please send it to
 1022...@bugs.debian.org.

 

Please do not send mail to  
ow...@bugs.debian.org unless you wish to report a problem with the
Bug-tracking system.

 

--

1022559:  
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022559

Debian Bug Tracking System

Contact   ow...@bugs.debian.org with problems

 



Bug#985603: bottom Drawer with open window(s) interferes with x2x

2021-03-20 Thread Rui Damas
Package: xmonad
Version: 0.14.2-3+b1
Severity: important

note ::: this bug may be in other packages: xmonad-contrib* or x2x.

while using the Drawer layout (
https://hackage.haskell.org/package/xmonad-contrib-0.16/docs/XMonad-Layout-Drawer.html
) at the bottom of the screen:

  simpleDrawer 0.002 0.35 (Role "in_drawer") `onBottom`

... works just fine... but, then i use x2x with the remote screen bellow:

  x2x -to :0 -south

... also works fine... but only there are no windows in the drawer :::
if i have open windows (focused or not) in the drawer, it prevents the
mouse from leaving the main screen to the remote screen... as soon as
all the windows in the drawer are closed it works fine... if i change
to a workspace with no windows in the drawer also works fine...



Bug#981701: on install, suggested/recommended could also list the depending package(s)

2021-02-02 Thread Rui Damas
Package: apt
Version: 1.8.2.2
Severity: wishlist

when `apt install'  lists the recommended/suggested packages to be
installed, would be nice to know which of the required packages are
depending in it.

often i found my self wishing to know that, when i install something
(typically with --no-install-recommends).



Bug#970240: missing desktop menu icon.

2020-09-13 Thread Rui Damas
Package: nut-monitor
Version: 2.7.4-8

i'm running rofi as menu to access applications...

  rofi -show-icons -show drun

... and `Nut Monitor' does not show an icon.



Bug#923390: Umlet package missing from the desktop menu

2019-02-27 Thread Rui Maciel
Package: hello
Version: 13.3-1.1

The umlet installer does not register umlet by not installing a desktop entry.

I've attached a desktop entry which, when installed in the
applications' directory (i.e., /usr/share/applications), enables Umlet
to be featured among the system's applications.


umlet.desktop
Description: application/desktop


Bug#900675: qt5-default: The Qt package is missing the scxml module, including the qscxmlc compiler.

2018-06-03 Thread Rui
Package: qt5-default
Version: 5.10.1+dfsg-7
Severity: important

Dear Maintainer,

The Qt packages currentlyl available in Debian's repository is missing
Qt's SCXML module.  Note that Qt Creator ships with support for SCXML
state machines and there's already a package available through Debian's
repository for  state machine charts in QML (qml-module-qtqml-statemachine).


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.16.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qt5-default depends on:
ii  qtbase5-dev  5.10.1+dfsg-7
ii  qtchooser64-ga1b6736-5

qt5-default recommends no packages.

Versions of packages qt5-default suggests:
ii  qt5-qmake  5.10.1+dfsg-7
ii  qtbase5-dev-tools  5.10.1+dfsg-7

-- no debconf information



Bug#882022: Congratulations Amazon Shopper! 9buQ

2017-11-18 Thread Rui Zhai
It is not my. You got mistake.

2017年11月18日 上午8:51,"Thank you" 写道:

> Your $50 Reward
>
>
> 
>
>
> 
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Your message dated Sat, 18 Nov 2017 16:18:11 +0100 with message-id
> <20171118151811.zmc3avxjwvqml...@dinghy.sail.spinnaker.de> has caused the
> report #882022, regarding fig2dev: buffer underwrite in get_line() to be
> marked as having been forwarded to the upstream software author(s) Thomas
> Loimer (NB: If you are a system administrator and have no idea what this
> message is talking about, this may indicate a serious mail system
> misconfiguration somewhere. Please contact ow...@bugs.debian.org
> immediately.) -- 882022: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882022
> Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
>
> -- 已转发邮件 --
> From: Roland Rosenfeld 
> To: Thomas Loimer 
> Cc: 882022-forwar...@bugs.debian.org
> Bcc:
> Date: Sat, 18 Nov 2017 16:18:11 +0100
> Subject: Bug#882022: fig2dev: buffer underwrite in get_line()
> Hi Thomas!
>
> I'm not sure, whether a string length of 0 or 1 can really happen
> here, but you're deeper in the code than me...
>
> - Forwarded message from Jakub Wilk  -
>
> From: Jakub Wilk 
> Subject: Bug#882022: fig2dev: buffer underwrite in get_line()
> To: sub...@bugs.debian.org
> Date: Fri, 17 Nov 2017 19:00:56 +0100
> Reply-To: Jakub Wilk , 882...@bugs.debian.org
>
> Package: fig2dev
> Version: 1:3.2.6a-6
>
> The get_line() function in fig2dev/read.c does this:
>
>   len = strlen(buf);
>   buf = '\0';   /* strip trailing newline */
>   if (buf == '\r')
>   buf = '\0';   /* strip any trailing CRs */
>   return 1;
>
> If the string length is 0 (or 1 is some cases), this writes outside the
> buffer.
>
> --
> Jakub Wilk
>
>
> - End forwarded message -
>
> Tscho
>
> Roland
>
>


Bug#881542: qtcreator: Qt Creator requires Valgrind and gdb-python2 to debug programs but neither package is listed as a dependency or even as a recommendation.

2017-11-12 Thread Rui
Package: qtcreator
Version: 4.2.0-1+b1
Severity: normal

Dear Maintainer,

Qt-Creator requires Valgrind to debug and profile code.  Yet, no package is 
listed as a dependency or even a
requirement.


-- System Information:
Debian Release: 9.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages qtcreator depends on:
ii  libbotan-1.10-1   1.10.16-1
ii  libc6 2.24-11+deb9u1
ii  libclang1-3.9 1:3.9.1-9
ii  libgcc1   1:6.3.0-18
ii  libqbscore1.7 1.7.0+dfsg-4
ii  libqbsqtprofilesetup1.7   1.7.0+dfsg-4
ii  libqt5concurrent5 5.7.1+dfsg-3+b1
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5designer5   5.7.1-1
ii  libqt5designercomponents5 5.7.1-1
ii  libqt5gui55.7.1+dfsg-3+b1
ii  libqt5help5   5.7.1-1
ii  libqt5network55.7.1+dfsg-3+b1
ii  libqt5printsupport5   5.7.1+dfsg-3+b1
ii  libqt5qml5 [qtdeclarative-abi-5-7-0]  5.7.1-2+b2
ii  libqt5quick5  5.7.1-2+b2
ii  libqt5quickwidgets5   5.7.1-2+b2
ii  libqt5sql55.7.1+dfsg-3+b1
ii  libqt5sql5-sqlite 5.7.1+dfsg-3+b1
ii  libqt5widgets55.7.1+dfsg-3+b1
ii  libqt5xml55.7.1+dfsg-3+b1
ii  libstdc++66.3.0-18
ii  qml-module-qtqml-models2  5.7.1-2+b2
ii  qml-module-qtquick-controls   5.7.1~20161021-2
ii  qml-module-qtquick2   5.7.1-2+b2
ii  qtchooser 63-g13a3d08-1
ii  qtcreator-data4.2.0-1

Versions of packages qtcreator recommends:
ii  clang  1:3.8-36
ii  gdb-python2 [gdb]  7.12-6
ii  konsole [x-terminal-emulator]  4:16.12.0-4
ii  make   4.1-9.1
ii  qmlscene   5.7.1-2+b2
ii  qt5-doc5.7.1-2
ii  qt5-qmltooling-plugins 5.7.1-2+b2
ii  qtbase5-dev-tools  5.7.1+dfsg-3+b1
ii  qtcreator-doc  4.2.0-1
ii  qtdeclarative5-dev-tools   5.7.1-2+b2
ii  qttools5-dev-tools 5.7.1-1
ii  qttranslations5-l10n   5.7.1~20161021-1
ii  qtxmlpatterns5-dev-tools   5.7.1~20161021-3
ii  xterm [x-terminal-emulator]327-2

Versions of packages qtcreator suggests:
ii  cmake  3.7.2-1
ii  g++4:6.3.0-4
ii  git1:2.11.0-3+deb9u2
ii  kdelibs5-data  4:4.14.26-2
pn  subversion 

-- no debconf information



Bug#849011: quagga 1.1.0-2 deleted support for sysV

2016-12-26 Thread Rui Ribeiro
Hello Scott,

I am interested. I am out of town, will get back to you in a couple of days.

On 23 December 2016 at 04:52, Scott Leggett <sc...@sl.id.au> wrote:

> On 2016-12-22.11:18, Rui Ribeiro wrote:
> > Hi Scott,
> >
> > I understand your answer.
> >
> >  It is sad people discontinuing functionalities that server a community
> and
> > have been working for so many years.
> >
> > I will starting doing my own debs, and will migrate in short time to
> > FreeBSD.
> >
> > Regards,
> > Rui Ribeiro
> >
>
> I understand your position but I do not run any SysV Debian systems
> myself so I am unable to properly debug, test and maintain SysV scripts
> with known bugs.
>
> If you or anyone else who uses SysV would like to help with the quagga
> package in Debian by testing and maintaining such scripts, they would be
> very welcome. I think the way to do that would be to form a quagga
> maintenance team. Let me know if you are interested.
>
> --
> Regards,
> Scott.
>



-- 
--
Senior Linux Sysadmin


Bug#849011: quagga 1.1.0-2 deleted support for sysV

2016-12-21 Thread Rui Ribeiro
Package: quagga
Version: 1.1.0-2
Severity: important

Dear Maintainer,

Today, after the updates, in my DNS server using Debian Stretch, OSPF
stopped working and thus the server does not belong to the DNS anycast
group.

When I try to do /etc/init.d/quagga start, the init.d script is no
longer there. I shall say I am still using sysVinit, and not systemd.

Apparently the quagga packages suffered a revision, and they are not
supporting SysVinit.

Several files have gone missing, including /etc/init.d/quagga, and
/etc/quagga/daemons. The binary watchquagga is not longer installed too.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 4.8.0-1-686-pae (SMP w/3 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages quagga depends on:
ii  quagga-bgpd1.1.0-2
ii  quagga-core1.1.0-2
ii  quagga-isisd   1.1.0-2
ii  quagga-ospf6d  1.1.0-2
ii  quagga-ospfd   1.1.0-2
ii  quagga-pimd1.1.0-2
ii  quagga-ripd1.1.0-2
ii  quagga-ripngd  1.1.0-2

quagga recommends no packages.

quagga suggests no packages.

-- debconf information excluded



Bug#840012: nagios-nrpe-server: post install does not allow upgrading for people not using it as a daemon

2016-10-07 Thread rui
Package: nagios-nrpe-server
Version: 2.15-1+b1
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 action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


When upgrading from Jessie to Stretch, at the end of dist-upgrade, it
ends with an error:

Errors were encountered while processing:
 nagios-nrpe-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To finish installing nagios-nrpe-server, I ended up verifying the
post-install scripts.

At nagios-nrpe-server.postinst:

#!/bin/sh
set -e
# Automatically added by dh_installinit
if [ -x "/etc/init.d/nagios-nrpe-server" ]; then
update-rc.d nagios-nrpe-server defaults >/dev/null
invoke-rc.d nagios-nrpe-server start || exit $?
fi


As I have nagios-nrpe being invoked by (x)inetd and not running
as a daemon, it failed startup and thus the apt dist-upgrade
error.

I do not recommend activating the service for boot and starting it, as
the service can also be started on non daemon-mode.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-0.bpo.1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages nagios-nrpe-server depends on:
ii  adduser  3.115
ii  libc62.24-3
ii  libssl1.0.2  1.0.2j-1
ii  libwrap0 7.6.q-25
ii  lsb-base 9.20160629

Versions of packages nagios-nrpe-server recommends:
ii  nagios-plugins2.1.2-2
ii  nagios-plugins-basic  2.1.2-2

nagios-nrpe-server suggests no packages.

-- Configuration Files:
/etc/default/nagios-nrpe-server changed [not included]
/etc/nagios/nrpe.cfg changed [not included]

-- no debconf information



Bug#772522: Bug#772651: live-build: --initsystem does not control which of live-config-{systemd, sysvinit} gets installed

2014-12-09 Thread Rui Miguel P. Bernardo
Hello,

the following patch will fix this bug and bug #772522 (casper is not
installed in ubuntu mode in live-build 4.0.3-1). It fixes the
--initsystem option and --mode ubuntu.

Example (one may want a live cd with sysvinit without systemd nor
consolekit installed):

Now, to get a jessie live system with sysvinit instead of systemd with
live-build 4.0.3-1:

lb config -d jessie

sed -i 's|live-config-systemd|live-config-sysvinit|'
config/package-lists/live.list.chroot
echo sysvinit-core  config/package-lists/live.list.chroot

sudo lb build

With the following patch applied one can symply select the prefered
supported initsystem (being the default systemd) and just do:

lb config -d jessie --initsystem sysvinit
sudo lb build

And live-build will build a jessie livesystem with sysvinit instead of systemd.

Obviously, in this case, because fluxbox does not depend on neither
systemd nor consolekit, they both don't get installed in the live
system. If a user selects packages that depend on systemd then he/she
should not select sysvinit as the initsystem for the image.

I did not tested it but last time I tried to build a wheezy live image
with live-build 4.0.3-1 it didn't booted. I think this patch will also
fix it, but I did not try.

The patch is against latest live-build debian-next branch but IMHO I
think this patch should be applied to the debian branch (jessie). I
can provide it if needed.

I've CC bug #772522 because I think it is related.

Please keep the --initsystem option in lb4.

Thank you.


On Tue, Dec 9, 2014 at 5:43 PM, Daniel Baumann
daniel.baum...@progress-technologies.net wrote:
 found 772651 4.0.3-1
 notfound 772651 4.0.3-1kali2
 thanks

 On 12/09/14 16:39, Raphaël Hertzog wrote:
 Version: 4.0.3-1kali2

 please don't report against versions never have been present in debian.

 Unfortunately, this means that the --initsystem option does not allow one to
 override this choice.

 given that this doesn't really work anyway due to the fact how
 debootstrap handles excludes (by ignoring them effectivly, #557322) and
 the state of the late state of the freeze, i'll remove the --initsystem.

 this will have to be properly re-added post jessie (jftr, eventhough i'm
 pro-systemd, i'll intend to support initsystem choice in lb as much as
 possible, so no need to worry about not getting that option back for
 stretch).

 Furthermore the check based on the distribution codename
 is very restrictive and doesn't work for derivatives.

 which is why, as said many times, lb5 is going to address that bottom-up.

 --
 Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
 Email:  daniel.baum...@progress-technologies.net
 Internet:   http://people.progress-technologies.net/~daniel.baumann/


 --
 To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: https://lists.debian.org/548734bd.9090...@progress-technologies.net

From 74b3f4a003488e4514f43d05cdda85aa596faca9 Mon Sep 17 00:00:00 2001
From: Rui Miguel P. Bernardo rui.bernardo...@gmail.com
Date: Wed, 10 Dec 2014 03:20:29 +
Subject: [PATCH] fix choice of --initsystem in debian and ubuntu.

---
 functions/defaults.sh |   10 +-
 scripts/build/config  |   51 +
 2 files changed, 44 insertions(+), 17 deletions(-)

diff --git a/functions/defaults.sh b/functions/defaults.sh
index aa9c3dd..20d6921 100755
--- a/functions/defaults.sh
+++ b/functions/defaults.sh
@@ -288,7 +288,15 @@ Set_defaults ()
 		*)
 			case ${LB_SYSTEM} in
 live)
-	LB_INITSYSTEM=${LB_INITSYSTEM:-sysvinit}
+	case ${LB_PARENT_DISTRIBUTION} in
+		wheezy)
+			LB_INITSYSTEM=${LB_INITSYSTEM:-sysvinit}
+			;;
+
+		*)
+			LB_INITSYSTEM=${LB_INITSYSTEM:-systemd}
+			;;
+	esac
 	;;
 
 normal)
diff --git a/scripts/build/config b/scripts/build/config
index e3b1e51..e18812f 100755
--- a/scripts/build/config
+++ b/scripts/build/config
@@ -1353,22 +1353,41 @@ done
 
 if [ ! -e config/package-lists/live.list.chroot ]
 then
-
-cat  config/package-lists/live.list.chroot  EOF
-live-boot
-live-config
-EOF
-
-case ${LB_PARENT_DISTRIBUTION} in
-	wheezy)
-		echo live-config-sysvinit  config/package-lists/live.list.chroot
-		;;
-
-	*)
-		echo live-config-systemd  config/package-lists/live.list.chroot
-		;;
-esac
-
+	case ${LB_INITRAMFS} in
+		live-boot)
+			echo live-boot  config/package-lists/live.list.chroot
+			echo live-config  config/package-lists/live.list.chroot
+			case ${LB_PARENT_DISTRIBUTION} in
+wheezy)
+	echo live-config-sysvinit  config/package-lists/live.list.chroot
+	;;
+*)
+	case ${LB_INITSYSTEM} in
+		none)
+			# do nothing		
+			;;
+		systemd)
+			echo live-config-systemd  config/package-lists/live.list.chroot
+			;;
+		sysvinit|runit|upstart)
+			echo live-config-${LB_INITSYSTEM}  config/package-lists/live.list.chroot

Bug#772522: live-build 4.0.3-1 does not install casper in ubuntu mode

2014-12-08 Thread Rui Miguel P. Bernardo
Hi,

thank you for your prompt reply. The patch works perfectly but after
the live image boot it does not work because of the live boot options
(they were set for live-boot, not casper). The way to go is with
LB_INITRAMFS so we don't break all the other live-build options like
[--initramfs auto|none|live-boot|casper] and the boot options
live-build sets at build time.

So I've edited your patched /usr/lib/live/build/config file version
and changed 3 things: LB_MODE for LB_INITRAMFS, debian) for
live-boot) and ubuntu) for casper).

I've then clean up the build tree, ran lb config again and finally
sudo lb build. At the binary stage zsync package could not be found
because it is in the universe repository. Atfer updating auto/config
with the option --archive-areas main universe the ubuntu live image
was finally built.

The image booted correctly and configured with casper.

Could you please update your patch with those 3 changes? It worked
perfectly and as expected in my tests. Thank you.

Cheers.

On Mon, Dec 8, 2014 at 5:21 AM, jnqnfe jnq...@gmail.com wrote:
 tags 772522 patch

 Patch attached, build against debian-next, please test it ;)


 On 08/12/2014 04:38, Rui Miguel P. Bernardo wrote:
 Package: live-build
 Version: 4.0.3-1
 Severity: normal

 Dear Maintainer,

 * What led up to the situation?

 I wanted to build a live image based on Ubuntu 14.10 utopic using
 latest live-build.

 * What exactly did you do (or not do) that was effective (or
   ineffective)?

 I have created a new build tree with lb config, copied the files from
 /usr/share/doc/live-build/examples/auto/* to auto/config and then I've
 added the following to config/auto:

 #!/bin/sh

 set -e

 lb config noauto \
 --mode ubuntu \
 -d utopic \
 ${@}

 I ran sudo lb clean, recreated the configuration with lb config to
 apply the new settings added in auto/config and finally a ran sudo lb
 build.

 * What was the outcome of this action?

 The live image build failed with:

 [2014-12-08 03:19:45] lb chroot_install-packages install
 P: Begin installing packages (install pass)...
 Reading package lists...
 Building dependency tree...
 Reading state information...
 E: Unable to locate package live-boot
 E: Unable to locate package live-config
 E: Unable to locate package live-config-systemd
 P: Begin unmounting filesystems...
 P: Saving caches...
 Reading package lists...
 Building dependency tree...
 Reading state information...
 user@galaxy:~/live$

 * What outcome did you expect instead?

 I expected that a live image of ubuntu utopic was built.

 After digging what the problem was I've found that the following two
 commits do not consider ubuntu mode, only debian and wheezy/jessie,
 breaking the whole ubuntu mode of live-build:

 
 http://live.debian.net/gitweb/?p=live-build.git;a=commitdiff;h=d1eae015774db9e11ddb656ad8bc377c565f503a

 
 http://live.debian.net/gitweb/?p=live-build.git;a=commitdiff;h=8eaba8ea5ced274ceb8357a64ead3ff05854e9bc

 I know that ubuntu mode support not a priority ATM but I was testing
 live-build 4.0.3-1 with ubuntu mode and the this issue came up.

 To workaround the problem I've simply edited manually the file
 /usr/lib/live/build/config. I have replaced the content of
 config/package-lists/live.list.chroot file with

 casper

 instead of live-boot live-config live-config-systemd.

 Then I clean up the build tree, ran lb config again and run sudo lb
 build to build the live image, which was then completed and booted
 successfully.

 I would provide a patch but I really don't know if you guys want to
 deal with the content of config/package-lists/live.list.chroot using
 just $LB_PARENT_DISTRIBUTION or using $LB_MODE and/or also
 $LB_INITRAMFS or any other solution you may already have.

 Thank you.


 -- Package-specific info:

 -- System Information:
 Debian Release: 7.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
 Architecture: amd64 (x86_64)

 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
 Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash

 Versions of packages live-build depends on:
 ii  debootstrap  1.0.64~bpo70+1

 Versions of packages live-build recommends:
 ii  cpio2.11+dfsg-0.1
 pn  live-boot-doc   none
 pn  live-config-doc none
 pn  live-manual-html | live-manual  none

 live-build suggests no packages.

 -- no debconf information





-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#772522: live-build 4.0.3-1 does not install casper in ubuntu mode

2014-12-07 Thread Rui Miguel P. Bernardo
Package: live-build
Version: 4.0.3-1
Severity: normal

Dear Maintainer,

* What led up to the situation?

I wanted to build a live image based on Ubuntu 14.10 utopic using
latest live-build.

* What exactly did you do (or not do) that was effective (or
  ineffective)?

I have created a new build tree with lb config, copied the files from
/usr/share/doc/live-build/examples/auto/* to auto/config and then I've
added the following to config/auto:

#!/bin/sh

set -e

lb config noauto \
--mode ubuntu \
-d utopic \
${@}

I ran sudo lb clean, recreated the configuration with lb config to
apply the new settings added in auto/config and finally a ran sudo lb
build.

* What was the outcome of this action?

The live image build failed with:

[2014-12-08 03:19:45] lb chroot_install-packages install
P: Begin installing packages (install pass)...
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package live-boot
E: Unable to locate package live-config
E: Unable to locate package live-config-systemd
P: Begin unmounting filesystems...
P: Saving caches...
Reading package lists...
Building dependency tree...
Reading state information...
user@galaxy:~/live$

* What outcome did you expect instead?

I expected that a live image of ubuntu utopic was built.

After digging what the problem was I've found that the following two
commits do not consider ubuntu mode, only debian and wheezy/jessie,
breaking the whole ubuntu mode of live-build:


http://live.debian.net/gitweb/?p=live-build.git;a=commitdiff;h=d1eae015774db9e11ddb656ad8bc377c565f503a


http://live.debian.net/gitweb/?p=live-build.git;a=commitdiff;h=8eaba8ea5ced274ceb8357a64ead3ff05854e9bc

I know that ubuntu mode support not a priority ATM but I was testing
live-build 4.0.3-1 with ubuntu mode and the this issue came up.

To workaround the problem I've simply edited manually the file
/usr/lib/live/build/config. I have replaced the content of
config/package-lists/live.list.chroot file with

casper

instead of live-boot live-config live-config-systemd.

Then I clean up the build tree, ran lb config again and run sudo lb
build to build the live image, which was then completed and booted
successfully.

I would provide a patch but I really don't know if you guys want to
deal with the content of config/package-lists/live.list.chroot using
just $LB_PARENT_DISTRIBUTION or using $LB_MODE and/or also
$LB_INITRAMFS or any other solution you may already have.

Thank you.


-- Package-specific info:

-- System Information:
Debian Release: 7.7
   APT prefers stable-updates
   APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages live-build depends on:
ii  debootstrap  1.0.64~bpo70+1

Versions of packages live-build recommends:
ii  cpio2.11+dfsg-0.1
pn  live-boot-doc   none
pn  live-config-doc none
pn  live-manual-html | live-manual  none

live-build suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#293454: qjackctl: Display does not resize with font

2014-12-01 Thread Rui Nuno Capela

On 12/01/2014 01:00 PM, Jaromír Mikeš wrote:



2014-11-30 16:07 GMT+01:00 Lukas F. Hartmann lu...@mnt.mn
mailto:lu...@mnt.mn:

Hello Lukas,

Dear Maintainer,

This bug is especially obvious on high resolution displays. Also,
the buttons
do not resize vertically, only horizontally, which leads to a
cramped UI with
bigger font sizes.

I attached a patch to fix these problems. The patch also removes the
manual
indentation of the left-aligned status labels in the main status
display and
rather increases the overall margin of the status display.

The interface is now fully scalable and looks good when disabling
the shiny
background bitmap option. I would recommend to drop this bitmap and
its toggle
option to reduce code and settings complexity for a feature that
does not
(IMHO) increase end user value.


Thank you for the patch, I am forwarding it upstream.
Maybe Rui also have some idea how to improve shiny background to be
scalable too.



well, it wasn't ever supposed to scale as to grow in screen space that is.

from the cradle, it was designed to stayy as is, as *low profile* as 
much as it's possible.


tbh. once you get those settings au point, or al dente, whatever 
semantics better suits you, the least you get qjackctl pesking your 
screen estate the better :)


byee
--
rncbc aka Rui Nuno Capela
rn...@rncbc.org


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#731374: Reproducable

2013-12-19 Thread Rui Mourato
Not an isolated bug as I'm also experiencing the same with this package.
Hanging at:

apache2_invoke: Enable module mod_mono
[] Restarting web server: apache2[Thu Dec 19 13:15:27.042986 2013] 
[so:warn] [pid 4636] AH01574: module mono_module is already loaded, skipping
. ok



Bug#729540: open-vm-tools-dkms: Fails to compile with Linux Kernel version 3.11

2013-12-03 Thread Rui Lopes
Package: open-vm-tools-dkms
Version: 2:9.2.3-1031360-7
Followup-For: Bug #729540

Dear Maintainer,

Fails to compile, rendering package useless for current version of the kernel 
in testing.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.11-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages open-vm-tools-dkms depends on:
ii  dkms  2.2.0.3-1.2
ii  make  3.81-8.3

Versions of packages open-vm-tools-dkms recommends:
ii  open-vm-tools  2:9.2.3-1031360-7

Versions of packages open-vm-tools-dkms suggests:
ii  open-vm-tools-desktop  2:9.2.3-1031360-7

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#663227: wrong permissions for /etc/shadow

2013-11-10 Thread Rui Maciel
I'm experiencing this bug after a fresh install (Debian 7.2.0 i386 
xfce).  The error messages included in my /var/log/auth.log are 
identical to those posted by lina, and when xscreensaver fails to 
authenticate I'm still able to login through a virtual terminal.


I've checked the owner:group and permissions of /etc/shadow and they are 
exactly like the ones Sebastien Koechlin said were the right ones.


Does anyone know how to circumvent this issue?


Thanks,
Rui Maciel


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#642357: Solution implemented upstream, please upgrade gnutls!

2013-06-08 Thread Rui Miguel Silva Seabra
From http://rutschle.net/pipermail/sslh/2012-March/000189.html we learn
that...

The maintainer of mod_gnutls just gave me the solution. The
problem is a bug in mod_gnutls 0.5.10 that causes mod_gnutls to
answer in plain text if the connection comes from localhost.
The bug has already been fixed and will be gone in the next
version.

Now... in current Debian:

rms@bernie:/etc/apache2/alias$ dpkg -l | grep mod-gnutls
ii  libapache2-mod-gnutls0.5.10-1.1
i386 Apache module for SSL and TLS encryption with GnuTLS


Oopsie! Can the maintainer please upgrade!?


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#642357: Ok, new release not out yet and the log isn't very clear what the patch is

2013-06-08 Thread Rui Miguel Silva Seabra
Ok, nevermind. There is no new version out *yet*.

I digged through the logs https://mod.gnutls.org/log/mod_gnutls/ and
it's possible that this is the patch:

@33826c520 months   neuromancer mod_proxy
support 

https://mod.gnutls.org/changeset/33826c53d7991024eeed255f860e9818188e2bcb/mod_gnutls/
 

I'm totally not currently able to tell whether it can be applied
directly or not.

Sigh, uninstalling libapache2-mod-gnutls as I need to answer https from
localhost connections.

Rui


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#705749: DHCP returns IP lease when wrong mask when the MAC is already registered in a different subnet

2013-04-19 Thread Rui Ribeiro
Package: isc-dhcp-server 
Version: 4.2.2.dfsg.1-5+deb70u3 

When we place a computer in a different network with allows unknow clients, the 
IP comes right, however the netmask comes from the subnet where the MAC is 
registered. If we delete the MAC or different MAC which is not registered in 
any subnet, that doesn't happen.

I am using Debian 7.0,  3.2.0-4-686-pae #1 SMP Debian 3.2.41-2 i686 GNU/Linux.

Best regards,
Rui Ribeiro


--
Rui Ribeiro
Linux Sysadmin  Network administrator / SI
ISCTE-IUL
http://www.linkedin.com/profile/view?id=56478568


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#693317: e1000e runtime suspend breaks shutdown

2012-11-25 Thread Zhang Rui
On Sun, 2012-11-25 at 23:48 +0800, Adam Lee wrote:
 CC Zhang Rui. 
 
 On Sun, Nov 25, 2012 at 02:33:54PM +0100, Ben Hutchings wrote:
  Control: tag -1 fixed-upstream patch moreinfo
  
  On Thu, 2012-11-15 at 21:29 +0800, Adam Lee wrote:
   Package: src:linux
   Version: 3.2.32-1
   Severity: important
   
   Hi, all
   
   As $subject, system hangs when halting, it's a e1000e driver bug. Please
   backport from upstream to fix it.
   
   Steps to reproduce:
   1, # for i in /sys/bus/pci/devices/*/power/control; do echo auto  
   $i; done
   2, shutdown or reboot
   
   Another way to reproduce, which makes this bug important:
   1, install laptop-mode-tools
   2, start laptop-mode-tools service
   3, shutdown or reboot
   
   This bug is fixed in kernel 3.3
   https://bugzilla.kernel.org/show_bug.cgi?id=36132
   
   Just FYI,
   https://bbs.archlinux.org/viewtopic.php?id=113985
  [...]
  
  But it's not clear how it was fixed...
  
  Can you test whether the attached patch works, following the
  instructions at
  http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official?
 
 No, the attached patch doesn't fix this. I think it maybe a e1000e
 but not a general bug.
 
 Mr. Zhang, could you please comment what was the problem behind this
 issue and how did it get fixed?
 
 Great thanks to you both.
 
I have no idea about this neither. sorry I can not help you.

-rui


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#691692: qbittorrent: Can't close About qBittorrent box

2012-10-28 Thread Rui Branco
Package: qbittorrent
Version: 2.9.8-1
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
Opening About qBittorrent box

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
Box opens, can't close it

   * What outcome did you expect instead?
A close button or a close box X.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages qbittorrent depends on:
ii  geoip-database 20121005-1
ii  libboost-filesystem1.49.0  1.49.0-3.1
ii  libboost-system1.49.0  1.49.0-3.1
ii  libc6  2.13-35
ii  libgcc11:4.7.1-7
ii  libqt4-dbus4:4.8.2+dfsg-2
ii  libqt4-network 4:4.8.2+dfsg-2
ii  libqt4-xml 4:4.8.2+dfsg-2
ii  libqtcore4 4:4.8.2+dfsg-2
ii  libqtgui4  4:4.8.2+dfsg-2
ii  libssl1.0.01.0.1c-4
ii  libstdc++6 4.7.1-7
ii  libtorrent-rasterbar6  0.15.10-1+b1
ii  python 2.7.3~rc2-1

qbittorrent recommends no packages.

Versions of packages qbittorrent suggests:
pn  qbittorrent-dbg  none

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#524741: ITP: adsuck -- small DNS server that filters blacklisted addresses

2012-08-22 Thread Rui Bernardo
Hello,

I'm planning to package adsuck for Debian. I've been working on it this 
week and it seem to be working here. Still have to clean lintians and 
other crufts, but its working. I expect to have something ready next 
week.

I am not a debian developer but I'm planning to become one to help; 
could anyone point me the procedure for a non debian developer to get 
a package into debian repos? I can't see anything relevant in the wnpp 
webpage [1]. Should I fill a new bug report?


Thank you

[1](http://www.debian.org/devel/wnpp/) 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#683261: live-build: please re-add losetup-lukshome hook

2012-07-30 Thread Rui Miguel P. Bernardo
Package: live-build
Version: 3.0_a53-1
Severity: wishlist
Tags: patch

Dear Maintainer,

the losetup-lukshome hook was removed from live-build recently because 
it was broken since the recent live-boot changes.

I have corrected this and now the hook works in squeeze/wheezy/sid and 
should work with either old versions of live-boot and live-build, as with 
the more recent ones.

I've tested with a squeeze build and a sid build, with live-build 3.0_a54-1.

This new version has some other minor changes and improvements.

Attached is the complete script.

Thank you.

-- Package-specific info:

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages live-build depends on:
ii  debootstrap  1.0.39

Versions of packages live-build recommends:
pn  cpio2.11-7
pn  gnu-fdisk   none
pn  live-boot-doc   3.0~a25-1
pn  live-config-doc 3.0~a35-1
pn  live-manual-html | live-manual  none

Versions of packages live-build suggests:
pn  dosfstools  none
pn  fakeroot1.18.2-1
pn  genisoimage none
pn  grub0.97-66
pn  memtest86+ | memtest86  none
pn  mtools  none
pn  parted  2.3-10
pn  squashfs-tools | mtd-tools  none
pn  sudo1.8.3p2-1
pn  syslinux2:4.05+dfsg-2
pn  uuid-runtimenone
pn  win32-loadernone

-- debconf-show failed
#!/bin/sh

## lukshome - a live-build(7) hook to have an encrypted /home
## Copyright (C) 2009-2012 Rui Bernardo rui.bernardo...@gmail.com
##
## This program is free software: you can redistribute it and/or modify
## it under the terms of the GNU General Public License as published by
## the Free Software Foundation, either version 3 of the License, or
## (at your option) any later version.
##
## This program is distributed in the hope that it will be useful, but
## WITHOUT ANY WARRANTY; without even the implied warranty of
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
## General Public License for more details.

# This hook was based and adapted from:
# http://lists.debian.org/debian-live/2009/04/msg00186.html
# -
#
#
# NOTE 1: this was not tested with persistent boot option,
# but it seems logic that persistent and lukshome can't
# coexist as boot options (because of snapshots and others), so lukshome
# won't be executed if any persistent option is given on boot.
#
# NOTE 2: if using an USB key, it will eventualy end up failing someday.
# You should backup the encrypted disk image file itself (luks-home.img) to
# prevent loosing your data.
#
# This hook will create 3 files:
#
# /usr/local/sbin/create-lukshome-file.sh
#	script to create an disk file image (luks-home.img) with a
#	LUKS encrypted ext2 filesystem inside to be placed in a
#	partition labeled lukshome.
#
# /usr/local/sbin/lukshome.sh
#	detects a partition with lukshome label, updates fstab and crypttab so
#	the encrypted file is mounted later in a loopback device (/dev/loopX).
#	It also changes /etc/init.d/umountfs so the encrypted home is correctly
#	umounted.
#
# (old live-boot) /usr/share/initramfs-tools/scripts/live-bottom/13live_luks_home
# (new live-boot) /lib/live/boot/-live_luks_home
#	a live-initramfs hook to execute lukshome.sh script
#	in initrd.
#
#
# HOWTO lukshome
# --
#
# First build your live system with this hook inside config/chroot_local-hooks/.
# If you have an existing live-build build directory with a previous live
# build, you might have to run
#
#	lb clean
#
# to make sure this hook is included in the live system. Then (re)build your
# live system.
#
#	lb build
#
# After booting your (re)built live system, setup the encrypted losetup
# filesystem to be used as /home using the instructions present in the
# create-lukshome-file.sh script.
#
# Reboot and now use the lukshome boot option to mount the encrypted /home,
# like when using persistent boot option with a home-rw file in some partition.
#


# install needed packages (in case apt recommends are off)
# make sure that cryptsetup is installed
echo I: checking for cryptsetup.
if [ ! -x /sbin/cryptsetup ]
then
	echo I: installing cryptsetup.
	DEBIAN_FRONTEND=dialog apt-get install --yes --force-yes -y cryptsetup
fi


echo I: to see how to use lukshome hook run create-lukshome-file.sh as root.
echo I: creating script /usr/local/sbin/create-lukshome-file.sh
cat  /usr/local/sbin/create-lukshome-file.sh  'EOF'
#!/bin/sh

# This script will create an encrypted filesystem in a file to
# be used as /home in a live system built with Debian Live with
# this hook in config/hooks

Bug#655198: live-installer does not remove live packages in the installed system

2012-07-20 Thread Rui Bernardo
On Mon, Jul 09, 2012 at 07:35:56PM +0100, Rui Bernardo wrote:
 Today I've built debian sid live images with live-installer 36. It's 
 working, thanks.
 
 This bug can be closed for wheezy, but what about squeeze?

When I was going to try to fix this bug in squeeze, and after reading 
live-installer changelog, building version 31 udeb file and including it 
in a squeeze live image, it turned out to be obvious that version 31 was 
supposed to be uploaded to squeeze. I suppose that time passed, d-i 
development continued and live-installer 31 never made to squeeze.

live-installer 31 removed the live packages correctly in the end of the 
installation. Version 30, the one in squeeze, does not.

Dear maintainers, could you please upload live-installer version 31 to 
squeeze so it is included in squeeze 6.0.6 and close this bug? tyvm.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#681261: live-build: please don't leave an empty fstab in chroot

2012-07-12 Thread Rui Bernardo
Sorry, forgot to CC the BTS, so I'm resending this mail.

On Thu, Jul 12, 2012 at 05:35:53PM +0200, Daniel Baumann wrote:
 severity 681261 normal
 retitle 681261 update fstab even if non-existent (possibly fstab.d too)
 reassign 681261 partman
 thanks
 
 On 07/11/2012 09:18 PM, Rui Bernardo wrote:
  when installing to disk, with live-installer and using a multiple

Just to clarify, when using a multiple schema is when the problem really 
shows up, but even with a all-in-one schema, fstab is empty. There 
aren't any aparent problems on boot because initramfs-tools (or 
initscripts) mounts the root filesystem. But still the fstab is empty 
and it will not find swap, for example.

  partition schema in partman, the presence of an empty fstab in the
  squashed filesystem breaks the fstab that is created by partman.
 
 as i said on irc some month ago when you first reported this, this is
 not a bug in live-build, we do not want an fstab on purpose.
 
 d-i (or partman) do need to handle that properly, ideally by using
 fstab.d as of wheezy anyway.

That would be good. Maybe live-build should also use fstab.d instead of 
overwriting what partman wrote with an empty one by default. It breaks 
any partitioning preseed and any encryption chosen in partman.

If a live-build user wants an empty (or not) fstab he/she can add it in 
the includes.chroot, even using fstab.d, but live-build forcing an 
empty fstab if the user don't include one is a problem.

 
 -- 
 Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
 Email:  daniel.baum...@progress-technologies.net
 Internet:   http://people.progress-technologies.net/~daniel.baumann/



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#681261: live-build: please don't leave an empty fstab in chroot

2012-07-12 Thread Rui Bernardo
After the short irc talk (it was a bit late), I have to believe that you 
did not had the time to drop an eye in the link [1] in the first post in 
this bug report.

On Thu, Jul 12, 2012 at 11:12:04PM +0200, Daniel Baumann wrote:
 On 07/12/2012 07:55 PM, Rui Bernardo wrote:
  That would be good. Maybe live-build should also use fstab.d instead of 
  overwriting what partman wrote with an empty one by default.
 
 again, live-build does not touch fstab, except making sure that there is
 no fstab at all in the live image.

I'm very sorry but I have to disagree. The commit message [2] says 
another thing. You really must be overlooking this issue. Look:

When removing fstab for live-installer also touch an empty file 
for it to avoid other packages failing on non-existing fstab.

So, some other package(s) needs to deal with fstab absence. And the line:

touch chroot/etc/fstab

in lb_chroot_hacks clearly creates an empty fstab. It _is_ this empty 
fstab that breaks live-installer, and by consequence, debian-installer.

FTR: For live-installer, that will extract the squashfs content to disk 
upon disk install _after_ partman created fstab with the user choices or 
preseed, it is the _absence_ of fstab inside the squashed chroot that 
makes partman setup in fstab work in live-installer, including swap and 
encryption, because the last is not overwriten by the tar extraction.

  If a live-build user wants an empty (or not) fstab he/she can add it in 
  the includes.chroot, even using fstab.d, but live-build forcing an 
  empty fstab if the user don't include one is a problem.
 
 right, customizations should be done through fstab.d via local includes
 only, and never through fstab. hence the latter should be always
 empty/not-used, and that's why live-build enforces that, sort-of.

Yes, but not with an empty file. live-build should only make sure that, 
if a fstab is _not_ in the user includes, then no fstab should be left in 
the chroot, not even an empty one, like live-build always did and 
live-installer always expected.

If partman should create another file other that /etc/fstab is another 
-valid- issue for me. But the thing is that, using this principle, it 
would imply for coerence, that sources.list also should not be created 
and instead a file inside sources.list.d/ should be created by d-i's 
apt-setup, as it is done by several other packages and live-build inside 
apt.conf.d/ and apt.preferences.d/.

At this point, with d-i near beta, it will be hard to implement that 
without some (natural) resistence from other people.

For coerence, the same also could/should be done with bash.bashrc (like 
it's done with profile.d/) and others (/etc/hosts.d/?). That would 
greatly improve the customization of the system without having to edit 
the main file during upgrades and all, and just drop a file in the 
*.d/ directory and maintain it (the file) separated from other packages 
and users always unpredictable edits/aditions/removals/truncates.

Sorry for taking your scarce spare time with this issue and insist on 
this. Maybe I should have made this more clear from the start.

Peace.


[1] http://lists.debian.org/debian-live/2012/06/msg00041.html
[2] 
http://live.debian.net/gitweb?p=live-build.git;a=commit;h=f3f9ad8bdec8df12bf20ae542c92ebfe75b1a86e



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#652946: busybox tar fails to copy filesystem.squashfs

2012-07-11 Thread Rui Bernardo
On Tue, Jul 10, 2012 at 06:38:57AM +0100, Rui Bernardo wrote:
 I was going to prepare another patch but I hold myself this time...
 
 I've searched what was creating those directories in the /target/. Turns 
 out to be /lib/partman/finish.d/20mount_partitions from partman-target [1].
 
 That code isn't touched since 2007 and creates the var/run and var/lock 
 directories in /target.

I meant that the relevant file was not changed since 2007.
 
 I'm not sure if /var/run and /var/lock still need to be created in 
 /target since debian policy changed for those directories. As Michael 
 pointed out, they are links now.

Reading the debian wiki about /var/run transition [2] and debian policy 
9.1.1.7 [3] I think debian-installer partman-target could only create 
/run now. It shouldn't be a problem if initscripts and initramfs-tools 
are ready to use /run instead of /var/run.


[1] http://anonscm.debian.org/gitweb/?p=d-i/partman-target.git
[2] http://wiki.debian.org/ReleaseGoals/RunDirectory
[3] http://www.debian.org/doc/debian-policy/ch-opersys.html



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#652946: partman-target should not create /var/run

2012-07-11 Thread Rui Bernardo
Attached is an eventual patch that could fix the issue.

From 93eec27e0bbedc9958ef6604f1d8062f6e1a9877 Mon Sep 17 00:00:00 2001
From: Rui M. P. Bernardo rui.bernardo...@gmail.com
Date: Wed, 11 Jul 2012 18:38:29 +0100
Subject: [PATCH] create /run instead of /var/run in target. Closes #652946.

---
 finish.d/mount_partitions |3 +--
 1 ficheiro modificado, 1 adição(+), 2 eliminados(-)

diff --git a/finish.d/mount_partitions b/finish.d/mount_partitions
index 9c8499e..f0c4efe 100755
--- a/finish.d/mount_partitions
+++ b/finish.d/mount_partitions
@@ -62,8 +62,7 @@ for f in $fstab; do
 			/)
 # Create these before /var is mounted,
 # so that they can be mounted as tmpfses
-mkdir -p /target/var/lock
-mkdir -p /target/var/run
+mkdir -p /target/run
 ;;
 			esac
 			continue 2
-- 
1.7.10



Bug#681261: live-build: please don't leave an empty fstab in chroot

2012-07-11 Thread Rui Bernardo
Package: live-build
Version: 3.0~a47-1
Severity: important

Dear Maintainer,

when installing to disk, with live-installer and using a multiple
partition schema in partman, the presence of an empty fstab in the
squashed filesystem breaks the fstab that is created by partman.

When the installed system boots the 1st time it gives several errors
because of missing mount entries that were created by partman in fstab
but were overwitten by the empty fstab present in the squashfs.

This was reported to the mailist [1] and I thought it was reported as a
bug or fixed in git but it wasn't, so I'm reporting it now.

Thank you.

[1] http://lists.debian.org/debian-live/2012/06/msg00041.html


-- Package-specific info:

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to pt_PT.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages live-build depends on:
ii  debootstrap  1.0.41

Versions of packages live-build recommends:
ii  cpio2.11-8
pn  gnu-fdisk   none
pn  live-boot-doc   none
pn  live-config-doc none
pn  live-manual-html | live-manual  none

Versions of packages live-build suggests:
pn  dosfstools  none
ii  fakeroot1.18.4-2
pn  genisoimage none
pn  memtest86+ | memtest86  none
pn  mtools  none
pn  parted  none
pn  squashfs-tools | mtd-tools  none
ii  sudo1.8.3p2-1.1
ii  syslinux2:4.05+dfsg-5
ii  uuid-runtime2.20.1-5.1
pn  win32-loadernone

-- no debconf information




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#652946: partman-target should not create /var/run

2012-07-11 Thread Rui Bernardo
On Wed, Jul 11, 2012 at 07:34:10PM +0100, Rui Bernardo wrote:
 Attached is an eventual patch that could fix the issue.

Sorry, the previous patch didn't create /target/run/lock. Better create 
it to prevent other possible failures about missing /run/lock.

New patch attached.

From 8e6298618e3583fa92fd106d42bcf7d24e673a42 Mon Sep 17 00:00:00 2001
From: Rui M. P. Bernardo rui.bernardo...@gmail.com
Date: Thu, 12 Jul 2012 00:38:11 +0100
Subject: [PATCH] create /run instead of /var/run in target. Closes #652946.

---
 finish.d/mount_partitions |4 ++--
 1 ficheiro modificado, 2 adições(+), 2 eliminados(-)

diff --git a/finish.d/mount_partitions b/finish.d/mount_partitions
index 9c8499e..a0a716d 100755
--- a/finish.d/mount_partitions
+++ b/finish.d/mount_partitions
@@ -62,8 +62,8 @@ for f in $fstab; do
 			/)
 # Create these before /var is mounted,
 # so that they can be mounted as tmpfses
-mkdir -p /target/var/lock
-mkdir -p /target/var/run
+mkdir -p /target/run
+mkdir -p /target/run/lock
 ;;
 			esac
 			continue 2
-- 
1.7.10



Bug#652946: busybox tar fails to copy filesystem.squashfs

2012-07-09 Thread Rui Bernardo
Today I've gave another try and this is still happening with today's sid 
build.

Following your hint that this is busybox related I've tried to find how 
far back this issue was happening using a patched live-build to use 
snapshots.debian.org. From the available daily installers this bug is 
present in all installers in http://d-i.debian.org/daily-images/i386. 
The only date I didn't confirm this bug was 20110509 because the 
installer stopped in the keyboard step. So I can assume this bug is 
present at least since 20110930.

I've tried to enable/disable config options in busybox udeb that were 
enabled since 20110930 (the last build I could reproduce this).

Looking at 
http://anonscm.debian.org/gitweb/?p=d-i/busybox.git;a=history;f=debian/config/pkg;hb=HEAD
 
I've tried to disable in busybox udeb CONFIG_MKTEMP and 
CONFIG_SWITCH_ROOT, just because their names are suspicious. Didn't 
work. The installer stopped in the keyboard step without any of them.

I can't check all the busybox udeb changes to trace this, it takes too 
much time to do it without knowing why the changes were made.

Another factor is busybox upstream version change since squeeze. It went 
from 1.17 to actual 1.20. So, this can also be an upstream problem or 
something that changed upstream. I don't know busybox enough to trace 
this in upstream versions in debian-installer.

But, while I was messing with busybox udeb, I've tried to enable 
CONFIG_FEATURE_TAR_FROM and tried to exclude var/lock and var/run in 
busybox tar (not the target's tar as in my previous patches) and all 
worked ok.

In busybox:

@@ -152,7 +152,7 @@ CONFIG_GZIP_FAST=0
 CONFIG_TAR=y
 CONFIG_FEATURE_TAR_CREATE=y
 # CONFIG_FEATURE_TAR_AUTODETECT is not set
-# CONFIG_FEATURE_TAR_FROM is not set
+CONFIG_FEATURE_TAR_FROM=y
 # CONFIG_FEATURE_TAR_OLDGNU_COMPATIBILITY is not set
 # CONFIG_FEATURE_TAR_OLDSUN_COMPATIBILITY is not set
 CONFIG_FEATURE_TAR_GNU_EXTENSIONS=y

In live-installer:

@@ -42,9 +42,13 @@ install_live_system () {
 
COUNT=0
OLD_IFS=$IFS
+
+   echo 'var/lock'  /tmp/excludes
+   echo 'var/run'  /tmp/excludes
+
mkdir -p /target
exec 40
-   tar c . | \
+   tar c . -X /tmp/excludes | \
(chdir /target  tar xv) | \
(
while read line; do
@@ -60,6 +64,8 @@ install_live_system () {
exec 04
IFS=$OLD_IFS
 
+   rm /tmp/excludes
+
chdir /
eval ${SUPPORT}_teardown
done

It worked, without using target tar and without chroot.

busybox udeb must be changed or the tar command will fail during the 
install.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#655198: live-installer does not remove live packages in the installed system

2012-07-09 Thread Rui Bernardo
Today I've built debian sid live images with live-installer 36. It's 
working, thanks.

This bug can be closed for wheezy, but what about squeeze?



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#652946: busybox tar fails to copy filesystem.squashfs

2012-07-09 Thread Rui Bernardo
Hi Michael,

On Mon, Jul 09, 2012 at 11:11:24PM +0400, Michael Tokarev wrote:
 Um.  This is just insane.  The bug is filed 22-Dec 2011,
 today is 09-Jul 2012, you have the actual cause, and it
 is still open, and the maintainers of suspected package
 (busybox) knows nothing about it... :(

I think we didn't know for sure that busybox was the to blame. Daniel 
said the error is in busybox, not a busybox error.

Because this bug is hard to trace (got to build and rebuild several live 
images), lack of time, etc, time passed... Anyway, as you pointed out, 
it's not busybox. Thank you.

 
 Okay.
 
 Rui, you found the root cause of this issue, it is there:
 
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652946#15
 
 The problem is that during extraction, target directory
 var/lock exists, and the installer tries to replace it
 with something else (I guess a symlink).
 
 Busybox tar does not try to remove directories in this
 case, to be replaced with files.  So it stops there,
 treating it as fatal error, and does not extract remaining
 files, creating issues for the system running later.
 
 Whenever it is a bug in busybox tar or not is an open
 question.  POSIX does not specify whenever it should do
 that or not.  GNU tar tries to rmdir() the existing
 file if unlink()ing it returned EISDIR, and will fail
 only if the directory is non-empty.  Ofcourse this rmdir
 can be added to busybox tar too, it is rather trivial.
 
 But this is not the point.
 
 The point is the presence of var/lock directory in the
 target system.  It should not be there to start with.
 We're extracting a whole set of directories, and any
 existing directory in the target which clashes with
 a file in the archive we're extracting may break the
 extraction with any tar implementation, not just
 busybox one.  Ie, always extract to empty target
 directory.

Thanks again for clearing the fog here :)

Following your pointers I've put a sleep 2000 in 
live-installer.postinst just _before_ the line mkdir -p /target and 
then I've open tty2 console in debian-installer to check what was in 
/target (see below).

 
 Now, I've no idea how this live system works, so I can't
 say more.
 
 Besides, I verified - busybox tar will correctly return
 failure (and write accutate reason to stderr) in this
 case.  So something else in the live installer should be
 broken too -- the part which loses error messages and
 non-zero status codes.

I think the problem about redirecting the error messages is because 
live-installer.postint extracts the filesystem in background with exec 
4. The relevant part of postinst:

eval ${SUPPORT}_prepare
STEPS=$(eval ${SUPPORT}_count)

db_progress INFO live-installer/progress/copying

COUNT=0
OLD_IFS=$IFS
mkdir -p /target
exec 40
tar c . | \
(chdir /target  tar xv) | \
(
while read line; do
COUNT=$(($COUNT + 1))
CURRENT=$(($COUNT * 100 / $STEPS))

[ x$CURRENT = x$LAST_UPDATE ]  continue

LAST_UPDATE=$CURRENT
db_progress STEP 1 4
done
)
exec 04

I don't know if adding a 2 or a |tee -a would work. It's a question 
of trying it. It would really help in the future.

 
 So, to sum it all: it is a bug in the live installer,
 it a) calls tar incorrectly (losing exit code and stderr)
 and b) does not verify that the target directory is empty
 or at least has sane content.

Thanks for this, I really thought it was something about links or 
hardlinks in the squash filesystem all the time. Turns out that is 
/target that is not empty when the extraction happens!

As I've said above, I've put a sleep 2000 before mkdir -p /target 
and SURPRISE (for me at least): /target, which I thought should be empty 
because it is apparently created after partman has formated the 
partitions (so I assumed completely empty), is _not_ empty:

root@quartor:~# tar tf target.tar.gz 
./
./etc/
./etc/fstab
./lost+found/
./media/
./media/cdrom0/
./media/cdrom
./var/
./var/lock/
./var/run/

I've attached the tar file with what I've found in /target/ before the 
extraction began.

I presume this must be something that line eval ${SUPPORT}_prepare 
does.

 
 Thanks,
 
 /mjt

Thank you very much!! Debian is just great :)


target.tar.gz
Description: Binary data


Bug#652946: busybox tar fails to copy filesystem.squashfs

2012-07-09 Thread Rui Bernardo
I was going to prepare another patch but I hold myself this time...

I've searched what was creating those directories in the /target/. Turns 
out to be /lib/partman/finish.d/20mount_partitions from partman-target [1].

That code isn't touched since 2007 and creates the var/run and var/lock 
directories in /target.

I'm not sure if /var/run and /var/lock still need to be created in 
/target since debian policy changed for those directories. As Michael 
pointed out, they are links now.

If the directories still need to exist for another package other than 
live-installer or for anything else, then we should patch live-installer 
to rmdir /target/var/run /target/var/lock before extracting the squashfs.

If not, maybe it should be partman-target that should stop creating
those directories.

What do you guys think?


[1] http://anonscm.debian.org/gitweb/?p=d-i/partman-target.git



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#673450: debian-installer-launcher: Uses xterm even if --text specified

2012-07-07 Thread Rui Miguel P. Bernardo
I have followed Kent suggestions and --text option works as it should 
from tty.

I've also tried from ssh and it also worked.

Attached is a fixed live plugin and an eventual patch.
#!/bin/sh

LIVE_TERMINAL=

live_usage()
{
cat EOF
 'live' plugin:

   WARNING: To use the installer without rebooting, the current kernel and the
installer's kernel must have the same version.

   -t, --textForce use of text installer
   -e, --expert  Use expert installation mode
EOF
}

live_prepare()
{
for arg in $@; do
case $arg in
-t|--text)
TEXT=true
export TEXT
;;

-e|--expert)
EXPERT=true
export EXPERT
;;
esac
done

if [ $TEXT != true ]; then
# Checking for x11
if [ -n $DISPLAY ]; then
# Checking for debconf frontend (gnome)
if dpkg -s libgnome2-perl  /dev/null 21; then
DEBIAN_FRONTEND=gnome
export DEBIAN_FRONTEND
fi
fi
else
DI_FRONTEND=newt
export DI_FRONTEND
[ $TEXT = true ]  export DEBIAN_FRONTEND=DI_FRONTEND
fi

# Checking for debconf frontend (LIVE_TERMINAL fallback)
if [ -z $DEBIAN_FRONTEND ]; then
LIVE_TERMINAL=x-terminal-emulator -e
fi

# Find an debian-installer initrd, preferably the gtk one
for IMAGE in /live/image/install/gtk/initrd.gz 
/live/image/install/initrd.gz; do
# don't use gtk in text mode (Bug#673450)
[ $IMAGE = /live/image/install/gtk/initrd.gz ]  [ $TEXT = 
true ]  continue
[ -e $IMAGE ]  break
done

[ ! -e $IMAGE ]  echo no suitable d-i initrd image found, aborting. 
 return 1

echo Loading debian-installer...

# Create the temporary directory
mkdir -p /live/installer

# Unpack the initrd
cd /live/installer
zcat $IMAGE | cpio -id  /dev/null 21

$LIVE_TERMINAL /usr/share/debian-installer-launcher/debconf_kernel.sh 
|| return 1

# Preseeding shutdown command
cat  preseed.cfg  EOF
# Select udeb for installation to allow exiting the installer
d-i anna/choose_modules string di-utils-exit-installer
# Ask question regardless from that it's preseeded above
d-i anna/choose_modules seen false
# Skip the exit timeout
d-i di-utils-reboot/really_reboot boolean false
EOF

# Preseeding installer expert mode
if [ $EXPERT = true ]; then
cat  preseed.cfg  EOF
# Setting expert mode
d-i debconf/priority select low
debconf debconf/priority select low
EOF
fi
}

live_cleanup () {
# Stopping syslogd/klogd
# -the sed horror could be improved (FIXME;)
# string: [A-Z][a-z]: [0-9] [0-9]rce [0-9]...
# we only want the [0-9]rce, but without the rce.
for PID in $(fuser -m /live/installer/var/log/syslog 21 | \
sed s,.*: ,,g;s, ,\n,g | grep 'rce$' | \
sed -e 's/rce//g'); do
kill -9 $PID  /dev/null 21 || true
done

# Unmounting filesystems
for fs in /cdrom /dev/pts /dev /proc /sys /tmp; do
umount -f /live/installer/$fs  /dev/null 21 || true
done

# Remove unpacked initrd
rm -rf /live/installer
rm -f /tmp/debian-installer
}

live_run()
{
# Bindmount installer media
mkdir -p /live/installer/cdrom
mount -o bind /live/image /live/installer/cdrom

# Bindmount filesytem
for fs in /dev /dev/pts /proc /sys /tmp; do
mount -o bind $fs /live/installer/$fs
done

if [ -n $DISPLAY ]; then
xhost +local:
fi

# Launching debian-installer
/usr/share/debian-installer-launcher/debian-installer.sh
}
From 9ee71ff3f5a995d5639b6f0b163ef7eeac13f50e Mon Sep 17 00:00:00 2001
From: Rui M. P. Bernardo rui.bernardo...@gmail.com
Date: Sat, 7 Jul 2012 05:32:28 +0100
Subject: [PATCH] Fix --text option. Thanks to Kent Loving (Closes: #673450)

---
 plugins/live |3 +++
 1 ficheiro modificado, 3 adições(+)

diff --git a/plugins/live b/plugins/live
index e352d46..bd9e779 100644
--- a/plugins/live
+++ b/plugins/live
@@ -43,6 +43,7 @@ live_prepare()
 	else
 		DI_FRONTEND=newt
 		export DI_FRONTEND
+		[ $TEXT = true ]  export DEBIAN_FRONTEND=DI_FRONTEND
 	fi
 
 	# Checking for debconf frontend (LIVE_TERMINAL fallback)
@@ -52,6 +53,8 @@ live_prepare()
 
 	# Find an debian-installer initrd, preferably the gtk one
 	for IMAGE in /live/image/install/gtk/initrd.gz /live/image/install/initrd.gz; do
+		# don't use gtk

Bug#655198: live-installer does not remove live packages in the installed system

2012-05-26 Thread Rui Miguel P. Bernardo
On Fri, Jan 13, 2012 at 6:17 PM, Joey Hess jo...@debian.org wrote:
 Rui Miguel P. Bernardo wrote:
 I've noticed that debian-installer-launcher was not removed in the
 installed system, as were not removed also live-config, live-boot and
 others.

 Related to this is the search for /cdrom/live/filesystem.packages-remove
 file. I suppose the /cdrom is not mounted when
 finish-install.d/60remove-live-packages is executed

 [...]

       15cdrom-detect: logger -t cdrom-detect $@
       15cdrom-detect:# Cannot just tell eject to eject /cdrom as it is not 
 compatible
       15cdrom-detect:# with busybox umount. Instead, unmount the cdrom 
 first, and then
       15cdrom-detect:CDDEV=$(mount | grep on /cdrom | cut -d ' ' -f 1)
       15cdrom-detect: umount /cdrom || true
       15cdrom-detect: db_get cdrom-detect/eject
       60remove-live-packages:for list in 
 /cdrom/live/filesystem.packages-remove; do

 If that's the case then something should be done. Move
 60remove-live-packages to before 15cdrom-detect (or vice-versa), or just
 remove manually the live packages, or something else.

 I agree, it looks broken for 60remove-live-packages to come after cdrom-detect
 cleans up after itself, if it depends on the CD being mounted.

 +do_manual_removal=true
 +
  # Remove packages as specified in specific package removal list
  for list in /cdrom/live/filesystem.packages-remove; do
       if [ -e $list ]; then

 This patch seems correct anyway, so I have applied it, but I don't
 feel it really fixes the bug, the intent seems to be for the list
 of packages to remove to be moved out of live-installer and into
 the creation of the live CD, and this only papers over that not working.

 --
 see shy jo

Hi Joey,

I've also found this bug in squeeze this week, while building a
squeeze live image with live-installer. The live-boot package (and the
others that depends on it) is/are not removed after disk install.

I've been using a patched version 34 live-installer in wheezy. It's
patched with fix for this bug and also with workaround for bug 655198
in wheezy.

I've built a squeeze live image with this patched udeb and,
apparently, all works ok in squeeze with live-installer 34+patch; live
packages are removed after the install. The patched live image can be
downloaded from http://www.adrive.com/public/gDgZaK.html and the
patched udeb(s) from github
(https://github.com/rbern/bravance/blob/master/live-installer_35~2.gbpe79f3c~debian6460%2B0_i386.udeb
and 
https://github.com/rbern/bravance/blob/master/live-installer_35~2.gbpe79f3c~debian6460%2B1_amd64.udeb).
The patched udeb should be copied into config/packages/ directory in
live-build config tree and --debian-installer live option included
in lb config to build with it.

Because squeeze live-installer also has this bug and building squeeze
with version 34 works ok, I would suggest to release a new 35 version
of live-installer and included it in next 6.0.x release. If that can't
happen, then  a fix release with a fresh
live-installer.d/remove-package file with the actual
finish-install.d/60remove-live-packages file (the file was renamed and
changed directory between version 30 and 34) could be done. Diffs:
http://anonscm.debian.org/gitweb/?p=d-i/live-installer.git;a=blobdiff;f=finish-install.d/60remove-live-packages;h=a70466e7e3ce248d509c3b5713c7ff7ce58f7676;hp=2d65ed4604c3ba6db3c474c73ff8c02b71a1d619;hb=HEAD;hpb=33fb8d6830c9b13232597968e2773c2804c723d2

Should I send a patch with this solution in version 30?

I don't know if this can be done, but a fix should be released because
leaving live-* packages in installed systems is not the supposed to
happen.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#652946: live-installer does not install /var/spool and breaks crontab

2012-05-26 Thread Rui Miguel P. Bernardo
 i cannot reproduce it with plain squeeze, and not with custom squeeze
 images (that use the same live-installer/d-i as wheezy, mostly).

 while the error clearly is in busybox, and using the tar from the target
 system is not acceptable solution, i assume this was a temporary issue
 with busybox in wheezy.

 i'll try to reproduce it later with a wheezy and sid/daily based image.

Hi Daniel,

sorry for the long delay. Only now I can reproduce live-installer bugs
in squeeze and wheezy with confidence.

I can also confirm that this bug does __not__ happen in squeeze for sure.

I suspect that bug #673328 is the same as this one because /var/log is
not restored in disk installation.

To confirm it I've build a wheezy standard live image with daily
installer udeb, and with a patched live-installer udeb. In the patched
live-installer /var/log/ directory is in /target/ after install,
without it /var/log does not exist in /target/.

wheezy with patched udeb http://www.adrive.com/public/q4BeZW.html
wheeze-standard-may2012-patched-udeb.iso

normal wheezy http://www.adrive.com/public/HPRHfB.html
wheeze-standard-may2012-without-patch.iso

The patched udebs can be found in github
https://github.com/rbern/bravance/blob/master/live-installer_35~2.gbpe79f3c~debian6460%2B0_i386.udeb

Should this bug be re-assigned to busybox/tar?



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#602956: nfs-kernel-server: not limited to ext4

2012-02-09 Thread Rui DaCosta
I've got the same issue on ARM, there is a known issue that UBIFS does not 
support NFS.


See this page and link to thread.

http://www.linux-mtd.infradead.org/faq/ubifs.html#L_nfs

Regards,
Rui

Bug#659167: cacti: [INTL:pt] Updated Portuguese translation for debconf messages

2012-02-08 Thread Rui Pedro - DebianPT
Package: cacti
Version: 0.8.7g-3
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for cacti's debconf messages.
Translator: Rui Branco ru...@debianpt.org
Feel free to use it.

For translation updates please contact 'Last Translator' or the
Portuguese Translation Team traduz _at_ debianpt.org.


-- 
Rui Branco
Traduz! - Portuguese Translation Team

# Portuguese translation of cacti's debconf messages.
# 01-11-2005 - Luís Ferreira ana...@gmail.com- Initial translation
# Rui Branco ru...@debianpt.org, 2011, 2012.
#
msgid 
msgstr 
Project-Id-Version: cacti 0.8.7g-3\n
Report-Msgid-Bugs-To: ca...@packages.debian.org\n
POT-Creation-Date: 2012-01-25 07:09+0100\n
PO-Revision-Date: 2012-02-08 20:59+\n
Last-Translator: Rui Branco ru...@debianpt.org\n
Language-Team: Portuguese tra...@debianpt.org\n
Language: pt\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
Plural-Forms: nplurals=2; plural=(n != 1)\n

#. Type: select
#. Choices
#: ../cacti.templates:2001
msgid Apache2
msgstr Apache2

#. Type: select
#. Choices
#: ../cacti.templates:2001
msgid None
msgstr Nenhum

#. Type: select
#. Description
#: ../cacti.templates:2002
msgid Web server:
msgstr Servidor Web: 

#. Type: select
#. Description
#: ../cacti.templates:2002
msgid 
Please select the web server for which Cacti should be automatically 
configured.
msgstr 
Por favor seleccione o tipo de servidor web para o qual o cacti deve ser 
automaticamente configurado.

#. Type: select
#. Description
#: ../cacti.templates:2002
msgid Select \None\ if you would like to configure the web server manually.
msgstr 
Seleccione \Nenhum\ se deseja configurar o seu servidor web manualmente.


Bug#655198: live-installer does not remove live packages in the installed system

2012-01-08 Thread Rui Miguel P. Bernardo
Package: live-installer
Version: 34
Severity: normal
Tags: d-i patch

Dear Maintainer,

I've noticed that debian-installer-launcher was not removed in the 
installed system, as were not removed also live-config, live-boot and 
others.

The problem was that a missing var initialization of do_manual_removal 
in finish-install.d/60remove-live-packages, preventing the packages to 
be manually removed by default.

do_manual_removal=true

Related to this is the search for /cdrom/live/filesystem.packages-remove 
file. I suppose the /cdrom is not mounted when 
finish-install.d/60remove-live-packages is executed, so the file 
/cdrom/live/filesystem.packages-remove is not found, and I can confirm 
that the file *is* in the image.

/usr/lib/finish-install.d # ls
01kickseed
05crypto
05localechooser
06user-setup
07brltty
07preseed
07speakup
10apt-cdrom-setup
10clock-setup
15cdrom-detect
20final-message
30hw-detect
50config-target-network
55netcfg-network-manager
60cleanup
60remove-live-packages
65partman-md
90base-installer
90console
94save-logs
95umount
97release-dhcp-lease
98exit-installer
99reboot

/usr/lib/finish-install.d # grep /cdrom *
10apt-cdrom-setup:if [ -e /cdrom/.disk/base_installable ]  \
10apt-cdrom-setup:   [ -e /cdrom/.disk/cd_type ]  \
10apt-cdrom-setup:   [ $(cat /cdrom/.disk/cd_type) = not_complete ] 
 \
10apt-cdrom-setup:  sed -i /^deb cdrom:/s/^/#/ 
/target/etc/apt/sources.list
15cdrom-detect: logger -t cdrom-detect $@
15cdrom-detect:# Cannot just tell eject to eject /cdrom as it is not 
compatible
15cdrom-detect:# with busybox umount. Instead, unmount the cdrom first, 
and then
15cdrom-detect:CDDEV=$(mount | grep on /cdrom | cut -d ' ' -f 1)
15cdrom-detect: umount /cdrom || true
15cdrom-detect: db_get cdrom-detect/eject
60remove-live-packages:for list in 
/cdrom/live/filesystem.packages-remove; do

I could not find any mount or umount command in 
/usr/lib/finish-install.d/*, just in 15cdrom-detect. Maybe it's 
15cdrom-detect that umounts the /cdrom. If it is cdrom-detect is 
misleading.

If that's the case then something should be done. Move 
60remove-live-packages to before 15cdrom-detect (or vice-versa), or just 
remove manually the live packages, or something else.

Anyway, to fix/workaroung the original problem by removing manually the 
packages, adding the variable an initial value makes the manual 
removal happen.

Patch attached. Thank you.

From 20ba218a7b3507a5cba54b78e6453b387aa4dc3a Mon Sep 17 00:00:00 2001
From: Rui Miguel P. Bernardo rui.bernardo...@gmail.com
Date: Mon, 9 Jan 2012 06:07:25 +
Subject: [PATCH] Initialize do_manual_removal var.

---
 finish-install.d/60remove-live-packages |2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/finish-install.d/60remove-live-packages 
b/finish-install.d/60remove-live-packages
index aab6db2..a70466e 100755
--- a/finish-install.d/60remove-live-packages
+++ b/finish-install.d/60remove-live-packages
@@ -1,5 +1,7 @@
 #!/bin/sh -e
 
+do_manual_removal=true
+
 # Remove packages as specified in specific package removal list
 for list in /cdrom/live/filesystem.packages-remove; do
if [ -e $list ]; then
-- 
1.7.7.1




-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
From 20ba218a7b3507a5cba54b78e6453b387aa4dc3a Mon Sep 17 00:00:00 2001
From: Rui Miguel P. Bernardo rui.bernardo...@gmail.com
Date: Mon, 9 Jan 2012 06:07:25 +
Subject: [PATCH] Initialize do_manual_removal var.

---
 finish-install.d/60remove-live-packages |2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/finish-install.d/60remove-live-packages b/finish-install.d/60remove-live-packages
index aab6db2..a70466e 100755
--- a/finish-install.d/60remove-live-packages
+++ b/finish-install.d/60remove-live-packages
@@ -1,5 +1,7 @@
 #!/bin/sh -e
 
+do_manual_removal=true
+
 # Remove packages as specified in specific package removal list
 for list in /cdrom/live/filesystem.packages-remove; do
 	if [ -e $list ]; then
-- 
1.7.7.1



Bug#652946: live-installer does not install /var/spool and breaks crontab

2011-12-25 Thread Rui Miguel P. Bernardo
Package: live-installer
Version: 34
Followup-For: Bug #652946


Hi again.

Because tar process doesn't return ant error, apparently, I didn't try 
to extract it's error output in my previous tests. When I did, by adding 
someting like 2 /target/tar-errors.txt in the tar xv line, the file 
showed this

tar: can't remove old file ./var/lock: Is a directory

So the extraction is not completed and stops when extracting /var/lock 
**and** does not return an error to live-installer. Maybe the exit code 
of tar extraction process should be also be redirected to track future 
errors while extracting the filesystem.

After trying to get busybox tar to exclude var/lock, without success 
because tar in debian busybox does not handle exclude option, I've tried 
the lenny approach I've seen in live-installer.postinst history in git 
repo, and use live system installed tar to extract the filesystem 
excluding var/lock.

chroot . tar c . --exclude=var/lock | \
(chdir /target  tar xv 2 /target/tar-errors.txt) | \

This gave me another error later upon install about /var/run:

tar: can't remove old file ./var/run: Is a directory

Then I added var/run to excludes, rebuilt udeb, rebuild live image and 
the install worked without missing dirs and files, even the excluded 
dirs were in /target/var. After boot no errors.

Patch attached.

Merry Christmas.


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.1.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
From a99ca344df7ac6f40e550bf5ab1e4b7172b07b23 Mon Sep 17 00:00:00 2001
From: Rui Miguel P. Bernardo rui.bernardo...@gmail.com
Date: Sat, 24 Dec 2011 14:24:52 +
Subject: [PATCH] use live system tar to use exclude

---
 debian/live-installer.postinst |3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/debian/live-installer.postinst b/debian/live-installer.postinst
index 800038b..1779082 100644
--- a/debian/live-installer.postinst
+++ b/debian/live-installer.postinst
@@ -44,7 +44,8 @@ install_live_system () {
 		OLD_IFS=$IFS
 		mkdir -p /target
 		exec 40
-		tar c . | \
+		# we need to use live system tar to use exclude
+		chroot . tar c . --exclude=var/lock --exclude=var/run | \
 		(chdir /target  tar xv) | \
 		(
 			while read line; do
-- 
1.7.2.5



Bug#652946: live-installer does not install /var/spool and breaks crontab

2011-12-21 Thread Rui Miguel P. Bernardo
Package: live-installer
Version: 34
Severity: normal

Hello,

after building a live image with live-build using the daily wheezy/sid 
installer and installed the image to disk crontab and postfix failed to 
start (this is a debian wheezy/testing image). The problem was a missing 
/var/spool directory in the installed system, that live-installer did 
not copy to disk.

While the installer copies the files in /live/filesystem.squashfs I've 
opened tty2 and confirmed that /var/spool is in the image

ls /mnt/var/spool

and is polulated. But after copying the files to disk, still in the 
installer, /var/spool does not exist.

ls /target/var/spool

After install /var/spool does not exist. This breaks crontab and 
probably all other packages that expect a /var/spool directory.

To fix (only) the crontab error, recreate the /var/spool directory in 
the installed system after 1st boot:

sudo mkdir /var/spool

I also had postfix in the image, but this one requires one to recreate 
its directory in /var/spool, not just /var/spool:

sudo mkdir -p /var/spool/postfix

Samba is another package that might break (not confirmed).

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.1.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#630329: live-config fails if sysv-rc= boot option is used

2011-06-12 Thread Rui Miguel P. Bernardo
Package: live-config
Version: 2.0.15-1
Severity: minor

*** Please type your report below this line *** When using 
live-config.sysv-rc= boot option to disable a service at boot like 
live-config.sysv-rc=cron the following error happens on boot:

startpar: service(s) returned failure: live-config ... failed!

Using debug in boot options we can see:


+ update-rc.d -f cron remove
+ grep -v update-rc.d: using dependency based boot sequencing
+ Trap
+ _RETURN=1
+ echo :ERROR
:ERROR
+ return 1

After boot, the service is indeed removed and is not running.

The code in /lib/live/config/scripts/config/015-sysv-rc is:


if [ -n ${LIVE_SYSV_RC} ]
then
for SERVICE in $(echo ${LIVE_SYSV_RC} | sed -e 's|,| |g')
do
update-rc.d -f ${SERVICE} remove | \
grep -v update-rc.d: using dependency based boot 
sequencing
done
fi

After some google research I read that grep -v always returns 1 when 
it has an inverted match (grep -v).

Because of the pipe, update-rc.d error can't be extracted without some 
bashism or digging into some output redirections as described in [1]. 
In my testings I've found that update-rc.d always returns 0:

sudo /usr/sbin/update-rc.d bogus_service_name remove
update-rc.d: using dependency based boot sequencing
echo $?
0

Even if all /etc/rc?.d/ directories are removed from the system 
update-rc.d always returns 0. Great. So it's useless to get update-rc.d 
exit status.

Because of that I would suggest to append a || true in the end of the 
line, as a workaround for the grep -v exit status.

update-rc.d -f ${SERVICE} remove | \
grep -v update-rc.d: using dependency based boot 
sequencing || true

I think this is better than using a  /dev/null 21 because any 
future changes in update-rc.d will still be shown in debug output.

Using the following live-build hook stops the original starpar error.

cat config/chroot_local-hooks/99-fix-grep-v-live-config-sysv-rc 

#!/bin/sh

# fix bug in live-config
sed  -i '/grep/ s|$| \|\| true|' /lib/live/config/01?-sysv-rc

A patch to live-config that applies this solution:

From 47539ee6fe5cbb916f2446d7c5846302ffabeab9 Mon Sep 17 00:00:00 2001
From: Rui Miguel P. Bernardo rui.bernardo...@gmail.com
Date: Sun, 12 Jun 2011 22:55:47 +0100
Subject: [PATCH] Fix non 0 exit status of grep -v ini sysv-rc.

---
 scripts/config/015-sysv-rc |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/scripts/config/015-sysv-rc b/scripts/config/015-sysv-rc
index 83e96cf..8191782 100755
--- a/scripts/config/015-sysv-rc
+++ b/scripts/config/015-sysv-rc
@@ -38,7 +38,7 @@ Configure_sysv_rc ()
for SERVICE in $(echo ${LIVE_SYSV_RC} | sed -e 's|,| |g')
do
update-rc.d -f ${SERVICE} remove | \
-   grep -v update-rc.d: using dependency based boot 
sequencing
+   grep -v update-rc.d: using dependency based boot 
sequencing || true
done
fi
 
-- 
1.7.2.5

Thank you


Rui Miguel P. Bernardo

[1]: http://tldp.org/LDP/abs/html/io-redirection.html   tldp.org documentation


-- System Information:
Debian Release: 6.0.1
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages live-config depends on:
ii  live-config-sysvinit [live-co 2.0.15-1   Debian Live - System Configuration

Versions of packages live-config recommends:
ii  sudo 1.7.4p4-2.squeeze.2 Provide limited super user privile
ii  user-setup   1.38Set up initial user and password

Versions of packages live-config suggests:
ii  wget  1.12-2.1   retrieves files from the web

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#625798: [ qtractor-Bugs-3298177 ] Track names with slashes cause MIDI recording to fail

2011-05-06 Thread Rui Nuno Capela

Fixed on svn trunk rev.2035 (qtractor 0.4.8.90).

- Session and track names are now sanitized from
  slashes.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#624198: more complete backtrace with both threads

2011-04-26 Thread Rui Nuno Capela

On 04/26/2011 05:18 PM, Adrian Knoth wrote:

On Wed, Apr 27, 2011 at 12:21:10AM +1000, Grant Diffey wrote:

JFTR, here's a more detailed backtrace:


snip


Steps to reproduce the bug:

1. start qjackctl
2. press start button (dummy driver is sufficient, but also works
   with alsa. If you want dummy, go to setup, first)
3. press connect button
4. select system on the left and system on the right, then, connect
5. press stop button
6. confirm termination
7. segfault


The attached patch against qjackctl fixes the problem, though I don't
know if it's addressing the real issue at hand.



applied to svn trunk (rev.685, qjackctl 0.3.7.12)

thanks
--
rncbc aka Rui Nuno Capela
rn...@rncbc.org



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#622749: traceroute nanog wrapper doesn´t know all the options

2011-04-14 Thread Rui Ribeiro
Package: traceroute-nanog 
Version: 1:2.0.15-1

The traceroute shell script wrapper doesn´t seem to know all the options 
described on the traceroute manual and supported by /usr/bin/traceroute.db.

#traceroute -N 6 www.sapo.pt
getopt: invalid option -- 'N'
Usage: /usr/bin/traceroute [-adnruvAMOPQU$] [-w wait] [-S start_ttl]
[-m max_ttl] [-p port] [-q nqueries] [-g gateway] [-t tos]
[-s src_addr] [-I proto]  host  [data_size]

I am using Debian 6.0.1 and kernel 2.6.32-5-686.

Best regards,
Rui Ribeiro


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#622234: gdm3: gdmsetup isn't working (doesn't unblock)

2011-04-13 Thread Rui Salvaterra
Also check dmesg, PolicyKit is SEGFAULTing. Mine shows (after trying to unlock):

[  134.212257] polkitd[972]: segfault at 0 ip b78b93da sp bfff3530
error 4 in libpolkit-backend-1.so.0.0.0[b78ae000+15000]



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#613711: php-geshi: Incorrect HTML generation while parsing Java source files

2011-02-16 Thread Rui Ferrao
Package: php-geshi
Version: 1.0.8.4-1
Severity: normal


Geshi is messing up the HTML when parsing Java files.
Problem is related to the insertion of Java documentation links together with 
class names.

Did a simple replacement of /usr/share/php-geshi/geshi.php with geshi.php from 
upstream version 1.0.9 and problem was fixed. 


-- System Information:
Debian Release: 6.0
  APT prefers squeeze-updates
  APT policy: (500, 'squeeze-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages php-geshi depends on:
ii  php5  5.3.3-7server-side, HTML-embedded scripti
ii  php5-cli  5.3.3-7command-line interpreter for the p

php-geshi recommends no packages.

php-geshi suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#601150: subversion reports 'SQLite compiled for 3.7.2, but running with 3.6.23.1'

2010-10-23 Thread Zhang Rui
Package: subversion
Version: 1.6.12dfsg-2
Severity: important

The subversion worked correctly before upgrading debian. After upgrading it, 
subversion can not commit, import anymore. On any client through network, 
clients report 'svn: Couldn't perform atomic initialization'. If the repository 
is local, svn reports 'SQLite compiled for 3.7.2, but running with 3.6.23'.
This bug can be re-produced by following experiment.

/tmp$ svnadmin create mytest
/tmp$ mkdir tt
/tmp$ cd tt/
/tmp/tt$ svn co file:///tmp/mytest/ .
Checked out revision 0.
/tmp/tt$ touch aa
/tmp/tt$ svn add aa
A aa
/tmp/tt$ svn ci -m 'test'
Adding aa
Transmitting file data .svn: Commit failed (details follow):
svn: While preparing '/home/zhr/tmp/tt/aa' for commit
svn: Couldn't perform atomic initialization
svn: Couldn't perform atomic initialization
svn: SQLite compiled for 3.7.2, but running with 3.6.23.1


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages subversion depends on:
ii  libapr11.4.2-6   The Apache Portable Runtime Librar
ii  libc6  2.11.2-6+squeeze1 Embedded GNU C Library: Shared lib
ii  libsasl2-2 2.1.23.dfsg1-6Cyrus SASL - authentication abstra
ii  libsvn11.6.12dfsg-2  Shared libraries used by Subversio

subversion recommends no packages.

Versions of packages subversion suggests:
pn  db4.8-utilnone (no description available)
ii  patch 2.6-2  Apply a diff file to an original
pn  subversion-tools  none (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#573287: dash: read function does not work as specified in manpage towards backslashes

2010-03-10 Thread Rui Damas
Package: dash
Version: 0.5.5.1-3
Severity: important

the bellow examples explain it:

#bash:
$ read line  echo $line
\\ \\ \\ \\
\ \ \ \

$ read -r line  echo $line
\\ \\
\\ \\

#dash:
$ read line  echo $line
\\ \\ \\ \\
\\

$ read -r line  echo $line
\\ \\
\ \



-- System Information:
Debian Release: squeeze/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500, 
'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-2-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages dash depends on:
ii  debianutils   3.2.2  Miscellaneous utilities specific t
ii  dpkg  1.15.5.6   Debian package management system
ii  libc6 2.10.2-6   Embedded GNU C Library: Shared lib

dash recommends no packages.

dash suggests no packages.

-- debconf information:
* dash/sh: true



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#567515: python-wxgtk2.6 fails to install

2010-01-29 Thread Rui Damas
Package: python-wxgtk2.6
Version: 2.6.3.2.2-4+b1
Severity: grave
Justification: renders package unusable

The bug has been reported already...

For the time being i did:

cd /usr/lib/python2.6/dist-packages
ln -s ../../python2.5/site-packages/wxversion.py 

 and it instaled fine.


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'squeeze'), (500, 
'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-2-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-wxgtk2.6 depends on:
ii  libc6 2.10.2-2   GNU C Library: Shared libraries
ii  libgcc1   1:4.4.2-9  GCC support library
ii  libstdc++64.4.2-9The GNU Standard C++ Library v3
ii  libwxbase2.6-02.6.3.2.2-4+b1 wxBase library (runtime) - non-GUI
ii  libwxgtk2.6-0 2.6.3.2.2-4+b1 wxWidgets Cross-platform C++ GUI t
ii  python2.5.4-9An interactive high-level object-o
ii  python-central0.6.14+nmu2register and build utility for Pyt
ii  python-wxversion  2.8.10.1-2 wxWidgets Cross-platform C++ GUI t
ii  python2.6 2.6.4-4An interactive high-level object-o

python-wxgtk2.6 recommends no packages.

Versions of packages python-wxgtk2.6 suggests:
ii  wx2.6-doc2.6.3.2.2-4 wxWidgets Cross-platform C++ GUI t
pn  wx2.6-examples   none  (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#565860: FTBFS - configure: error: JACK library not found

2010-01-19 Thread Rui Nuno Capela
On Tue, 19 Jan 2010 12:08:27 +0100, Adrian Knoth
a...@drcomp.erfurt.thur.de wrote:
 On Tue, Jan 19, 2010 at 10:19:45AM +0100, Adrian Knoth wrote:
 
 Hi!
 
 It's probably a bug in configure(.ac), however, you can work around if
 you conditionally set --disable-sse on non-amd64. (i386 doesn't have
 SSE, i686 could, but that's not an ordinary Debian target)
 
 It's really a bug in configure.ac. The test extends CFLAGS to enable
 SSE, but it doesn't restore the old value in case the test fails.
 
 The attached patch corrects this problem. Tested on sparc (no SSE) and
 i686 (with SSE).
 
 Rui: See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565860 for the
 whole story. I guess you want to include the patch in your repository.
 
 Note that I'm not really common with autoconf, so there might be a more
 elegant way of restoring CFLAGS upon negative test. At least it works.
 ;)
 

patch applied to upstream svn trunk (qtractor 0.4.4.1495+)

thankU 
-- 
rncbc aka Rui Nuno Capela
rn...@rncbc.org



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#533046: live-initramfs: cron services in live system

2009-06-14 Thread Rui Bernardo
Package: live-initramfs
Version: 1.157.2+20090608.075451
Severity: minor



-- Package-specific info:

-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages live-initramfs depends on:
ii  busybox   1:1.10.2-2 Tiny utilities for small and embed
ii  file  4.26-1 Determines file type using magic
ii  initramfs-tools   0.92o  tools for generating an initramfs
ii  sudo  1.6.9p17-2 Provide limited super user privile
ii  udev  0.125-7+lenny1 /dev/ and hotplug management daemo
ii  user-setup1.23   Set up initial user and password

Versions of packages live-initramfs recommends:
ii  cryptsetup  2:1.0.6-7configures encrypted block devices
ii  eject   2.1.5+deb1-4 ejects CDs and operates CD-Changer
ii  uuid-runtime1.41.3-1 universally unique id library
ii  wget1.11.4-2 retrieves files from the web

Versions of packages live-initramfs suggests:
pn  curlftpfs none (no description available)
pn  genext2fs none (no description available)
pn  httpfs2   none (no description available)
ii  loop-aes-utils2.13.1-4   Tools for mounting and manipulatin
pn  mtd-tools none (no description available)
ii  squashfs-tools1:3.3-7Tool to create and append to squas

-- no debconf information

Hello,

this is the first time I use reportbug so excuse me if something is 
wrong and please correct this.

I'm using live-helper from live.debian.net/debian/ repository, 
stable-live version in an updated lenny 5.0.1 live system build.

After login in, the system starts to be loaded with cron jobs. I was 
going to create a hook to stop cron execution and, while I was digging 
live-initramfs for examples to how to do it, I've found it was already 
made in /usr/share/initramfs-tools/scripts/live-bottom/25configure_init:

# This has the nice side effect of the 
cron.{daily,weekly,monthly} jobs in
# /etc/crontab remaining disabled, yet also not run by anacron
if [ -x /root/usr/sbin/anacron ]
then
chroot /root dpkg-divert --add --rename --quiet 
/usr/sbin/anacron
ln -s /bin/true /usr/sbin/anacron
fi

From what I see the link isn't working because it's not linking in the 
/root filesystem. I guess it should be:

ln -s /root/bin/true /root/usr/sbin/anacron



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#533046: live-initramfs: cron services in live system

2009-06-14 Thread Rui Bernardo
Package: live-initramfs
Followup-For: Bug #533046



-- Package-specific info:

-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages live-initramfs depends on:
ii  busybox   1:1.10.2-2 Tiny utilities for small and embed
ii  file  4.26-1 Determines file type using magic
ii  initramfs-tools   0.92o  tools for generating an initramfs
ii  sudo  1.6.9p17-2 Provide limited super user privile
ii  udev  0.125-7+lenny1 /dev/ and hotplug management daemo
ii  user-setup1.23   Set up initial user and password

Versions of packages live-initramfs recommends:
ii  cryptsetup  2:1.0.6-7configures encrypted block devices
ii  eject   2.1.5+deb1-4 ejects CDs and operates CD-Changer
ii  uuid-runtime1.41.3-1 universally unique id library
ii  wget1.11.4-2 retrieves files from the web

Versions of packages live-initramfs suggests:
pn  curlftpfs none (no description available)
pn  genext2fs none (no description available)
pn  httpfs2   none (no description available)
ii  loop-aes-utils2.13.1-4   Tools for mounting and manipulatin
pn  mtd-tools none (no description available)
ii  squashfs-tools1:3.3-7Tool to create and append to squas

-- no debconf information


Correction: the whole if block wasn't being executed also, so the 
dpkg-divert command and the wrong link weren't executed too. More, the 
correct link should be from /bin/true to /root/usr/sbin/anacron (I 
guess /bin gets mounted before /root).

Here is a diff from the changes I made (with a corrected link):


--- /usr/share/initramfs-tools/scripts/live-bottom/25configure_init 
2009-06-14 06:45:13.0 +
+++ modified/25configure_init   2009-06-14 22:21:41.444530789 +
@@ -87,14 +87,14 @@ then
 fi
 
 # do not try to remove files if using file-rc
-if [ -d /etc/rc0.d ]
+if [ -d /root/etc/rc0.d ]
 then
# This has the nice side effect of the cron.{daily,weekly,monthly} jobs 
in
# /etc/crontab remaining disabled, yet also not run by anacron
if [ -x /root/usr/sbin/anacron ]
then
chroot /root dpkg-divert --add --rename --quiet 
/usr/sbin/anacron
-   ln -s /bin/true /usr/sbin/anacron
+   ln -s /bin/true /root/usr/sbin/anacron
fi
 
# No point, really

Tested and confirmed working.
anacron is linked and «dpkg-diverted» now:
$ ls -l /usb/sbin/anacron*
lrwxrwxrwx 1 root root14 Jun 14 22:16 /usr/sbin/anacron - /bin/true
-rwxr-xr-x 1 root root 23040 Mar  9  2008 /usr/sbin/anacron.distrib
$ sudo dpkg-divert --list|grep anacron
local diversion of /usr/sbin/anacron to /usr/sbin/anacron.distrib

No more anacron process:
$ ps aux |grep anacron
live  6458  0.0  0.1   3128   736 pts/0R+   22:33   0:00 grep anacron

Now that the if block is working, it's preventing my postfix server from 
starting:

# No point, really
rm -f /root/etc/rc?.d/[SK]??postfix

Postfix isn't installed by default in debian, so I guess the point was 
to do this with exim4. Since there is really no point for doing that for 
neither of them (postfix nor exim4) I would suggest removing that line. 



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#484997: unison: Place logfile in .unison directory instead of home directory

2008-06-07 Thread Rui Boon

Package: unison
Version: 2.27.57-1
Severity: wishlist
Tags: patch


Currently unison places its logfile in the home directory. It would be better (and nicer) if unison, by default, could place its logfile in .unison dir. 


I have attached a patch (in dpatch format) to address this 'wishlist'

This wishlist could also be found at Ubuntu launchpad [0]


[0]: https://bugs.launchpad.net/bugs/234365


Cheers

Rui Boon




#! /bin/sh /usr/share/dpatch/dpatch-run
## change-logfile-location.dpatch by Tan Rui Boon [EMAIL PROTECTED]
##
## All lines beginning with `## DP:' are a description of the patch.
## DP: Change logfile location  
## DP: by prepending .unison to name of logfile in  ubase/trace.ml

@DPATCH@
diff -urNad unison-2.27.57~/ubase/trace.ml unison-2.27.57/ubase/trace.ml
--- unison-2.27.57~/ubase/trace.ml  2007-04-02 11:03:20.0 +0800
+++ unison-2.27.57/ubase/trace.ml   2008-06-02 14:24:54.0 +0800
@@ -98,10 +98,10 @@
 
 let logfile =
   Prefs.createString logfile
-(Util.fileInHomeDir unison.log)
+(Util.fileInHomeDir .unison/unison.log)
 Log file name
 By default, logging messages will be appended to the file
- \\verb|unison.log| in your HOME directory.  Set this preference if
+ \\verb|unison.log| in your .unison directory.  Set this preference if
  you prefer another file.
 
 let logch = ref None


Bug#219220: Millions of men use this

2008-03-25 Thread Rui Parshley
Let her experience the most amazing ride of her life.

http://www.Krytonynes.com/
Stripping for pleasure



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#252419: 2 capsules for 3 inches

2008-03-24 Thread Rui Perros
You deserve only the best, click here

http://www.Crovinci.com/
Find out what works for men



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#280398: Slap that cute tight ass

2008-03-21 Thread Rui Immaisi

Don’t disappoint her when she sees how small you are- fix that today.

http://www.poputinesu.com/
Cum again and shoot harder



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#419613: amule: Program committed suicide (closing search tabs)

2007-08-17 Thread Rui Branco

Package: amule
Version: 2.1.3-3+b1
Severity: important
File: /usr/bin/amule

The program freezes everytime I try to close any or all tabs of a search 
(search page).


Cheers,
Rui Branco

(no debugging symbols found)
Using host libthread_db library /lib/libthread_db.so.1.
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1228982592 (LWP 3748)]
[New Thread -1259746416 (LWP 3755)]
[New Thread -1242969200 (LWP 3753)]
(no debugging symbols found)
..
(no debugging symbols found)
0xb7f92ae1 in ?? ()
#0 0xb7f92ae1 in ?? ()

-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.21-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages amule depends on:
ii amule-common 2.1.3-3 common files for the rest of aMule
ii libc6 2.6-2 GNU C Library: Shared libraries
ii libcrypto++6 5.5-3 General purpose cryptographic shar
ii libgcc1 1:4.2-20070712-1 GCC support library
ii libstdc++6 4.2-20070712-1 The GNU Standard C++ Library v3
ii libwxbase2.6-0 2.6.3.2.1.5 wxBase library (runtime) - non-GUI
ii libwxgtk2.6-0 2.6.3.2.1.5 wxWidgets Cross-platform C++ GUI t
ii zlib1g 1:1.2.3.3.dfsg-5 compression library - runtime

Versions of packages amule recommends:
pn amule-utils (no description available)



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#430029: nautilus: Invalid memory reference

2007-06-21 Thread Rui Pedro

Package: nautilus
Version: 2.14.3-11+b1
Severity: important
File: /usr/bin/nautilus

Just opened nautilus (imediately got a crash).

(no debugging symbols found)
Using host libthread_db library /lib/libthread_db.so.1.
(no debugging symbols found)
...
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226910016 (LWP 4399)]
(no debugging symbols found)
(no debugging symbols found)

(no debugging symbols found)
0xb7723b11 in __waitpid_nocancel () from /lib/libpthread.so.0
#0 0xb7723b11 in __waitpid_nocancel () from /lib/libpthread.so.0
#1 0xb7e87865 in gnome_gtk_module_info_get () from 
/usr/lib/libgnomeui-2.so.0

#2
#3 0xb768fd87 in g_str_hash () from /usr/lib/libglib-2.0.so.0
#4 0xb7668257 in g_hash_table_lookup () from /usr/lib/libglib-2.0.so.0
#5 0x080f4602 in nautilus_file_get_uri ()
#6 0x080f46a5 in nautilus_file_get_uri ()
#7 0x080e23ea in nautilus_directory_async_state_changed ()
#8 0x080e24c1 in nautilus_directory_async_state_changed ()
#9 0x0812aa09 in egg_recent_item_unref ()
#10 0xb775eeb0 in ORBit_c_stub_invoke () from /usr/lib/libORBit-2.so.0
#11 0x08067887 in ?? ()
#12 0x082a5068 in ?? ()
#13 0x0815d364 in ?? ()
#14 0x0001 in ?? ()
#15 0x in ?? ()

Thread 1 (Thread -1226910016 (LWP 4399)):
#0 0xb7723b11 in __waitpid_nocancel () from /lib/libpthread.so.0
No symbol table info available.
#1 0xb7e87865 in gnome_gtk_module_info_get () from 
/usr/lib/libgnomeui-2.so.0

No symbol table info available.
#2
No symbol table info available.
#3 0xb768fd87 in g_str_hash () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#4 0xb7668257 in g_hash_table_lookup () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#5 0x080f4602 in nautilus_file_get_uri ()
No symbol table info available.
#6 0x080f46a5 in nautilus_file_get_uri ()
No symbol table info available.
#7 0x080e23ea in nautilus_directory_async_state_changed ()
No symbol table info available.
#8 0x080e24c1 in nautilus_directory_async_state_changed ()
No symbol table info available.
#9 0x0812aa09 in egg_recent_item_unref ()
No symbol table info available.
#10 0xb775eeb0 in ORBit_c_stub_invoke () from /usr/lib/libORBit-2.so.0
No symbol table info available.
#11 0x08067887 in ?? ()
No symbol table info available.
#12 0x082a5068 in ?? ()
No symbol table info available.
#13 0x0815d364 in ?? ()
No symbol table info available.
#14 0x0001 in ?? ()
No symbol table info available.
#15 0x in ?? ()
No symbol table info available.
#0 0xb7723b11 in __waitpid_nocancel () from /lib/libpthread.so.0

-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.21.5
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages nautilus depends on:
ii desktop-file-utils 0.12-1 Utilities for .desktop files
ii gnome-control-center 1:2.14.2-7 utilities to configure the GNOME d
ii libart-2.0-2 2.3.19-3 Library of functions for 2D graphi
ii libatk1.0-0 1.18.0-2 The ATK accessibility toolkit
ii libbonobo2-0 2.18.0-2 Bonobo CORBA interfaces library
ii libc6 2.5-9+b1 GNU C Library: Shared libraries
ii libeel2-2.14 2.14.3-5 Eazel Extensions Library (for GNOM
ii libesd-alsa0 [libesd0] 0.2.36-3 Enlightened Sound Daemon (ALSA) -
ii libexif12 0.6.15-1 library to parse EXIF files
ii libgail-common 1.8.11-4 GNOME Accessibility Implementation
ii libgail17 1.8.11-4 GNOME Accessibility Implementation
ii libgconf2-4 2.18.0.1-3 GNOME configuration database syste
ii libglade2-0 1:2.6.0-4 library to load .glade files at ru
ii libglib2.0-0 2.12.12-1 The GLib library of C routines
ii libgnome-desktop-2 2.18.2-1 Utility library for loading .deskt
ii libgnome2-0 2.18.0-4 The GNOME 2 library - runtime file
ii libgnomecanvas2-0 2.14.0-3 A powerful object-oriented display
ii libgnomeui-0 2.18.1-2 The GNOME 2 libraries (User Interf
ii libgnomevfs2-0 1:2.18.1-2 GNOME Virtual File System (runtime
ii libgtk2.0-0 2.10.12-2 The GTK+ graphical user interface
ii libnautilus-extension1 2.14.3-11+b1 libraries for nautilus components
ii liborbit2 1:2.14.7-0.1 libraries for ORBit2 - a CORBA ORB
ii libpango1.0-0 1.16.4-1 Layout and rendering of internatio
ii libpopt0 1.10-3 lib for parsing cmdline parameters
ii librsvg2-2 2.16.1-2 SAX-based renderer library for SVG
ii libstartup-notification0 0.9-1 library for program launch feedbac
ii libx11-6 2:1.0.3-7 X11 client-side library
ii libxml2 2.6.28.dfsg-1 GNOME XML library
ii nautilus-data 2.14.3-11 data files for nautilus
ii shared-mime-info 0.21-2 FreeDesktop.org shared MIME databa

Versions of packages nautilus recommends:
ii desktop-base 4.0.3 common files for the Debian Deskto
ii eject 2.1.5-2 ejects CDs and operates CD-Changer
pn fam (no description available)
ii libgnomevfs2-extra 1:2.18.1-2 GNOME Virtual File System (extra m
ii librsvg2-common 2.16.1-2 SAX-based renderer library for SVG
pn nautilus-cd-burner (no description 

Bug#143821: Republican Faltering plays

2007-04-03 Thread Rui Longshore
stolen Get through your
http://img444.imageshack.us/my.php?image=oxna9.jpg
by Dick Kazan Food Network



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#408186: [INTL:pt] Portuguese translation for heimdal (debconf)

2007-02-05 Thread Rui Branco

Brian May wrote:

Rui == Rui Branco [EMAIL PROTECTED] writes:


OB
Rui Portuguese (pt) translation for heimdal's debconf messages by
Rui Carlos Lisboa carloslisboa _at_ gmail.com.  Feel free to
Rui use it.

Hello,

Heimdal already has a pt_BR.po (Brazilian Portuguese). See bug
http://bugs.debian.org/278730.

Can I please just confirm the pt.po file is in addition to the above
file?

  


Hi there ,

indeed the Portuguese (pt) is actually to add (pt.po)

Thank you,

Rui Branco
debianPT.org

Thanks.
  




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#408183: [INTL:pt] Portuguese translation for ca-certificates (debconf)

2007-01-23 Thread Rui Branco

Package: ca-certificates
Version:
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for ca-certificates's debconf messages
by Carlos Lisboa carloslisboa _at_ gmail.com.
Feel free to use it.

For translation updated please contact Carlos Lisboa and CC the
Portuguese
translation team traduz _at_ debianpt.org



























pt.po
Description: application/gettext


Bug#408182: [INTL:pt] Portuguese translation for dictionaries-common (debconf)

2007-01-23 Thread Rui Branco

Package: dictionaries-common
Version:
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for dictionaries-common's debconf messages
by Carlos Lisboa carloslisboa _at_ gmail.com.
Feel free to use it.

For translation updated please contact Carlos Lisboa and CC the
Portuguese
translation team traduz _at_ debianpt.org


























pt.po
Description: application/gettext


Bug#408184: [INTL:pt] Portuguese translation for openslp (debconf)

2007-01-23 Thread Rui Branco

Package: openslp
Version:
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for ca-certificates's debconf messages
by Carlos Lisboa carloslisboa _at_ gmail.com.
Feel free to use it.

For translation updated please contact Carlos Lisboa and CC the
Portuguese
translation team traduz _at_ debianpt.org




























pt.po
Description: application/gettext


Bug#408186: [INTL:pt] Portuguese translation for heimdal (debconf)

2007-01-23 Thread Rui Branco

Package: heimdal
Version:
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for heimdal's debconf messages
by Carlos Lisboa carloslisboa _at_ gmail.com.
Feel free to use it.

For translation updated please contact Carlos Lisboa and CC the
Portuguese
translation team traduz _at_ debianpt.org





























pt.po
Description: application/gettext


Bug#407787: [INTL:pt] Portuguese translation for acidlab (debconf)

2007-01-21 Thread Rui Branco

Package: acidlab
Version:
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for acidlab's debconf messages
by Miguel Figueiredo elmig _at_ debianpt.org.
Feel free to use it.

For translation updated please contact Miguel Figueiredo and CC the
Portuguese
translation team traduz _at_ debianpt.org

























pt.po
Description: application/gettext


Bug#406014: [INTL:pt] Portuguese translation update for boa (debconf)

2007-01-07 Thread Rui Branco

Package: boa
Version:
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for boa's debconf messages
by Ricardo Silva ardoric _at_ gmail.com.
Feel free to use it.

For translation updated please contact Ricardo Silva and CC the
Portuguese
translation team traduz _at_ debianpt.org

























pt.po
Description: application/gettext


Bug#401299: [INTL:pt] Portuguese translation for sitebar (debconf)

2006-12-02 Thread Rui Branco

Package: sitebar
Version: 3.3.8-3
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for sitebar's debconf messages
by Rui Branco ruipb _at_ debianpt.org.
Feel free to use it.

For translation updated please contact Rui Branco and CC the Portuguese
translation team traduz _at_ debianpt.org























pt.po
Description: application/gettext


Bug#401381: [INTL:pt] Portuguese translation for quota (debconf)

2006-12-02 Thread Rui Branco

Package: quota
Version:
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for quota's debconf messages
by Miguel Figueiredo elmig _at_ debianpt.org.
Feel free to use it.

For translation updated please contact Miguel Figueiredo and CC the 
Portuguese

translation team traduz _at_ debianpt.org
























pt.po
Description: application/gettext


Bug#401384: [INTL:pt] Portuguese translation for mkvmlinuz (debconf)

2006-12-02 Thread Rui Branco

Package: mkvmlinuz
Version: 27
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for mkvmlinuz's debconf messages
by Rui Branco ruipb _at_ debianpt.org.
Feel free to use it.

For translation updated please contact Rui Branco and CC the Portuguese
translation team traduz _at_ debianpt.org
























pt.po
Description: application/gettext


Bug#401386: [INTL:pt] Portuguese translation for mapserver (debconf)

2006-12-02 Thread Rui Branco

Package: mapserver
Version: 4.10.0-3
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for mapserver's debconf messages
by Rui Branco ruipb _at_ debianpt.org.
Feel free to use it.

For translation updated please contact Rui Branco and CC the Portuguese
translation team traduz _at_ debianpt.org

























pt.po
Description: application/gettext


Bug#401067: [INTL:pt] Portuguese translation for zope-common (debconf)

2006-11-30 Thread Rui Branco

Package: zope-common
Version: 0.5.27
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for zope-common's debconf messages
by Rui Branco ruipb _at_ debianpt.org.
Feel free to use it.

For translation updated please contact Rui Branco and CC the Portuguese
translation team traduz _at_ debianpt.org






















pt.po
Description: application/gettext


Bug#400988: [INTL:pt] Portuguese translation for debsecan (debconf)

2006-11-29 Thread Rui Branco

Package: debsecan
Version: 0.4.3
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for debsecan's debconf messages
by Miguel Figueiredo elmig _at_ debianpt.org.
Feel free to use it.

For translation updated please contact Miguel Figueiredo and CC the 
Portuguese

translation team traduz _at_ debianpt.org
























pt.po
Description: application/gettext


Bug#400999: [INTL:pt] Portuguese translation for zope-quotafolder (debconf)

2006-11-29 Thread Rui Branco

Package: zope-quotafolder
Version:
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for zope-quotafolder's debconf messages
by Rui Branco ruipb _at_ debianpt.org.
Feel free to use it.

For translation updated please contact Rui Branco and CC the Portuguese
translation team traduz _at_ debianpt.org






















pt.po
Description: application/gettext


Bug#400847: [INTL:pt] Portuguese translation for noflushd (debconf)

2006-11-28 Thread Rui Branco

Package: noflushd
Version:
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for noflushd's debconf messages
by Rui Branco ruipb _at_ debianpt.org.
Feel free to use it.

For translation updated please contact Rui Branco and CC the Portuguese
translation team traduz _at_ debianpt.org





















pt.po
Description: application/gettext


Bug#399346: [INTL:pt] Portuguese translation for trn4 (debconf)

2006-11-19 Thread Rui Branco

Package: trn4
Version: 4.0-test76-11
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for trn4's debconf messages
by Rui Branco ruipb _at_ debianpt.org.
Feel free to use it.

For translation updated please contact Rui Branco and CC the Portuguese
translation team traduz _at_ debianpt.org




















# Portuguese translation of trn4's debconf messages.
# Copyright (C) 2006 THE trn4'S COPYRIGHT HOLDER
# This file is distributed under the same license as the trn4 package.
# 2006-11-19 - Rui Branco [EMAIL PROTECTED] - initial translation
#
#
msgid 
msgstr 
Project-Id-Version: trn4 4.0-test76-11\n
Report-Msgid-Bugs-To: [EMAIL PROTECTED]
POT-Creation-Date: 2006-09-29 11:20+0100\n
PO-Revision-Date: 2006-11-19 12:28+\n
Last-Translator: Rui Branco [EMAIL PROTECTED]\n
Language-Team: Portuguese [EMAIL PROTECTED]\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit

#. Type: string
#. Description
#: ../templates.master:1001
msgid What news server should be used for reading and posting news?
msgstr Que servidor de 'news' deverá ser utilizado para ler e enviar 'news'?

#. Type: string
#. Description
#: ../templates.master:1001
msgid 
trn is configured to read news via an NNTP connection, and needs to know the 
fully-qualified host name of the server (such as news.example.com). If you 
have a local news spool, you should consider installing some NNTP server 
like inn2; in that case, enter \localhost\ as your news server.
msgstr 
O trn está configurado para ler 'news' através de uma ligação NNTP e 
precisa 
de saber o nome de máquina do servidor 'fully-qualified' (como por exemplo 
news.example.com). Se possui um 'local news spool' deverá considerar a 
instalação de um servidor NNTP como inn2; nesse caso introduza \localhost\ 

como o seu servidor de 'news'.

#. Type: string
#. Description
#: ../templates.master:2001
msgid What is your system's mail name?
msgstr Qual o nome de mail do seu sistema?

#. Type: string
#. Description
#: ../templates.master:2001
msgid 
Please enter the 'mail name' of your system. This is the hostname portion of 
the address to be shown on outgoing news and mail messages, and is used by 
many packages. trn4 users may override this individually by setting the FROM 
environment variable.
msgstr 
Por favor introduza o 'nome de mail' do seu sistema. Esta é a porção do 
nome 
da máquina do endereço a ser visualizado nas 'news' de saída e mensagens de 

mail, e é usado por muitos pacotes. Os utilizadores do trn4 podem 
individualmente 
sobrepor esta configuração ao definirem a variável de ambiente FROM.

#. Type: error
#. Description
#: ../templates.master:3001
msgid /etc/news/whoami and /etc/mailname differ
msgstr /etc/news/whoami e /etc/mailname diferem

#. Type: error
#. Description
#: ../templates.master:3001
msgid 
Some versions of Debian's various trn packages used /etc/news/whoami to 
construct the default From: line of outgoing mail and news messages. This 
package uses /etc/mailname instead, to comply with Debian policy.
msgstr 
Algumas versões da Debian variam no uso de pacotes usados pelo /etc/news/
whoami para construir a linha de From por omissão nas mensagens de mail e 
de 'news'. Este pacote utiliza o /etc/mailname para cumprir com a política da 

Debian.

#. Type: error
#. Description
#: ../templates.master:3001
msgid 
However, /etc/news/whoami says that addresses on your system are in the 
domain ${whoami}, while /etc/mailname says that they are in the domain 
${mailname}. In common with your mail configuration, trn4 will use /etc/
mailname from now on anyway; if you need to change this, you might consider 
setting the FROM environment variable for each user to be that user's e-mail 
address.
msgstr 
No entanto, o /etc/news/whoami diz que os endereços no seu sistema estão 
no domínio ${whoami}, enquanto que o /etc/mailname diz que estes estão no 
domínio ${mailname}. Em sintonia com a sua configuração de mail, o trn4 
utilizará /etc/mailname a partir de agora; se precisar de alterar, pode 
considerar 
definir a variável de ambiente FROM para cada utilizador, de modo a servir de 

endereço email de cada utilizador.



Bug#399348: [INTL:pt] Portuguese translation for smb2www (debconf)

2006-11-19 Thread Rui Branco

Package: smb2www
Version: 980804-29
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for smb2www's debconf messages
by Rui Branco ruipb _at_ debianpt.org.
Feel free to use it.

P.S: The pt_PT language ID is depreceated, it has been replaced by the 
pt ID.


For translation updated please contact Rui Branco and CC the Portuguese
translation team traduz _at_ debianpt.org

Cheers



















# Portuguese translation of smb2www's debconf messages.
# 2005, Rui Branco [EMAIL PROTECTED]
# 2005-09-29 - Rui Branco [EMAIL PROTECTED]
# 2005-11-13 - Rui Branco [EMAIL PROTECTED] 3f
# 2006-11-19 - Rui Branco [EMAIL PROTECTED] 6f4u
#
#
msgid 
msgstr 
Project-Id-Version: smb2www 980804-29\n
Report-Msgid-Bugs-To: \n
POT-Creation-Date: 2006-10-19 01:28+0200\n
PO-Revision-Date: 2006-11-19 12:41+\n
Last-Translator: Rui Branco [EMAIL PROTECTED]\n
Language-Team: Portuguese [EMAIL PROTECTED]\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit

#. Type: note
#. Description
#: ../templates:1001
msgid smb2www is DISABLED by default
msgstr O smb2www está DESACTIVADO por omissão

#. Type: note
#. Description
#: ../templates:1001
msgid 
If enabled, by default smb2www will allow anyone to browse your network.
msgstr 
Se activo, o smb2www permite, por omissão, que qualquer um navegue na sua 
rede.

#. Type: note
#. Description
#: ../templates:1001
msgid 
Probably this is not what you want to happen. Please modify your web server 
configuration to suit. Please read /usr/share/doc/smb2www/index.html for 
more information (Especially FAQ 4) on how to do this for Apache.
msgstr 
Provavelmente esta situação não será o que deseja. Por favor modifique a 
configuração do seu servidor web de modo adequado. Leia /usr/share/doc/
smb2www/index.html para mais informação (especialmente a FAQ 4) acerca de 
como fazer isto para o Apache.

#. Type: boolean
#. Description
#: ../templates:2001
msgid Do you want to enable smb2www?
msgstr Pretende activar o smb2www?

#. Type: boolean
#. Description
#: ../templates:2001
msgid Turn this option on if you want to enable smb2www.
msgstr Active esta opção se pretender activar o smb2www.

#. Type: boolean
#. Description
#: ../templates:2001
msgid 
Note that you can enable smb2www at any time by running\n
  dpkg-reconfigure smb2www\n
command.
msgstr 
Repare que pode activar o smb2www em qualquer altura correndo\n
  dpkg-reconfigure smb2www\n

#. Type: string
#. Description
#: ../templates:3001
msgid Which server shall I use as master browser ?
msgstr Qual o servidor que deverá seu usado como navegador principal (master 
browser)?

#. Type: string
#. Description
#: ../templates:3001
msgid 
Please enter name of the server which will be used by smb2www as a master 
browser
msgstr 
Introduza por favor o nome do servidor que será utilizado pelo smb2www como 
navegador principal

#. Type: select
#. Choices
#: ../templates:4001
#
#
msgid English
msgstr Inglês

#. Type: select
#. Choices
#: ../templates:4001
msgid Czech
msgstr Checo

#. Type: select
#. Choices
#: ../templates:4001
msgid Dutch
msgstr Holandês

#. Type: select
#. Choices
#: ../templates:4001
msgid Finnish
msgstr Finlandês

#. Type: select
#. Choices
#: ../templates:4001
msgid French
msgstr Francês

#. Type: select
#. Choices
#: ../templates:4001
msgid Polish
msgstr Polaco

#. Type: select
#. Choices
#: ../templates:4001
msgid Spanish
msgstr Espanhol

#. Type: select
#. Choices
#: ../templates:4001
msgid Swedish
msgstr Sueco

#. Type: select
#. Choices
#: ../templates:4001
msgid Vietnamese
msgstr Vietnamita

#. Type: select
#. Default
#. You must NOT translate this string, but you can change its value.
#. The comment between brackets is used to distinguish this msgid
#. from the one in the Choices list; you do not have to worry about
#. them, and have to simply choose a msgstr among the English values
#. listed in the Choices field above, e.g. msgstr Dutch
#: ../templates:4002
msgid English[ default language ]
msgstr English[ default language ]

#. Type: select
#. Description
#: ../templates:4003
msgid Which language would you like to use with smb2www ?
msgstr Qual o idioma que deseja para utilizar no smb2www ?

#. Type: select
#. Description
#: ../templates:4003
msgid Smb2www can generate its HTML pages in several languages.
msgstr O smb2www pode gerar as suas páginas HTML em vários idiomas.

#. Type: select
#. Description
#: ../templates:4003
msgid Please choose one of them.
msgstr Por favor escolha um deles.

#. Type: boolean
#. Description
#: ../templates:6001
msgid Do you want to install new version of config file?
msgstr Deseja instalar uma nova versão do ficheiro de configuração?

#. Type: boolean
#. Description
#: ../templates:6001
msgid 
Current smb2www configuration file `/etc/smb2www/smb2www.conf' contains some 
variables (e.g. `bindir'), which sometimes needs to be changed on package 
upgrade, and some variables (like `masterbrowser'), which shouldn't

Bug#399397: [INTL:pt] Portuguese translation for gpm (debconf)

2006-11-19 Thread Rui Branco

Package: gpm
Version: 1.19.6-23
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for gpm's debconf messages
by Rui Branco ruipb _at_ debianpt.org.
Feel free to use it.

For translation updated please contact Rui Branco and CC the Portuguese
translation team traduz _at_ debianpt.org





















# Native Portuguese translation of gpm.
# This file is distributed under the same license as the gpm package.
# 2006-11-19 - Rui Branco [EMAIL PROTECTED] - initial translation
#
msgid 
msgstr 
Project-Id-Version: gpm 1.19.6-23\n
Report-Msgid-Bugs-To: [EMAIL PROTECTED]
POT-Creation-Date: 2006-11-16 07:00+0200\n
PO-Revision-Date: 2006-11-19 14:55+\n
Last-Translator: Rui Branco [EMAIL PROTECTED]\n
Language-Team: Portuguese [EMAIL PROTECTED]\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit

#. Type: boolean
#. Description
#: ../gpm.templates:1001
msgid Do you want to start or restart GPM while X is running?
msgstr Deseja iniciar ou reiniciar o GPM enquanto o X está a correr?

#. Type: boolean
#. Description
#: ../gpm.templates:1001
msgid 
Usually, GPM should be started or restarted when it is installed or 
upgraded.  But when X is running and trying to use the same mouse device, 
this can sometimes cause a problem with the X mouse cursor. Switching to the 
console and then back to X will usually fix it.
msgstr 
Normalmente o GPM deve ser iniciado ou reiniciado quando é instalado ou 
actualizado.  No entanto quando o X está a correr e a tentar utilizar o mesmo 

dispositivo de rato, pode por vezes causar um problema com o curso do rato em 
X. Mudar para o modo consola e voltar ao modo X normalmente resolve o 
problema.

#. Type: string
#. Description
#: ../gpm.templates:2001
msgid Which mouse device should gpm use?
msgstr Que dispositivo de rato deverá o gpm usar?

#. Type: string
#. Description
#: ../gpm.templates:2001
msgid 
Where is your mouse device? If you have a regular PS/2 mouse, you probably 
want /dev/psaux. If you have a serial mouse, it may be something like /dev/
ttyS0. If you have a usb mouse (make sure you have the modules loaded), 
it's /dev/input/mice. If you're on a Sun machine, it's probably /dev/
sunmouse. If you're on an 68k Macintosh, it's probably /dev/mouse.
msgstr 
Onde está o seu dispositivo de rato? Se possui um rato PS/2 regular, 
provavelmente quererá o /dev/psaux. Se tem um rato série, poderá ser 
qualquer coisa como /dev/ttyS0. Se tiver um rato usb (certifique-se que tem 
os módulos carregados), será /dev/input/mice. Se estiver numa máquina 
Sun, provavelmente será em /dev/sunmouse. Se estiver numa máquina 
68k Macintosh, estará provavelmente em /dev/mouse.

#. Type: string
#. Description
#: ../gpm.templates:3001
msgid What type is your mouse?
msgstr Qual o tipo do seu rato?

#. Type: string
#. Description
#: ../gpm.templates:3001
msgid Available mouse types are:
msgstr Os tipos disponíveis de rato são:

#. Type: string
#. Description
#: ../gpm.templates:3001
msgid Name Description
msgstr Nome Descrição

#. Type: string
#. Description
#: ../gpm.templates:3001
msgid 
PS/2 mice: round 6-pin connector\n
 autops2Most PS/2 mice; specific protocol will be auto-detected.\n
Also use this for USB and ADB mice.\n
 ps2Standard PS/2 mice, 2 or 3 buttons\n
 imps2  Microsoft IntelliMouse and compatibles; PS/2 mice with\n
3 buttons and a scroll wheel\n
 exps2  Newer Microsoft IntelliMouse and compatible, may have\n
more than 3 buttons.  Most newer PS/2 mice are this type.\n
 synps2 Synaptics PS/2 TouchPad, found on many laptops\n
 netmouse   Genius NetMouse, 2 normal buttons plus an \Up/Down\ button\n
 fups2  Same as \ps2\ but may be needed for certain broken\n
mice or KVM switches\n
 fuimps2Same as \imps2\ but may be needed for certain broken\n
mice or KVM switches
msgstr 
ratos PS/2: conector redondo 6-pins\n
 autops2A maior parte dos ratos PS/2; protocolo especifico será detectado 
automaticamente.\n
utilize também para ratos USB e ADB.\n
 ps2ratos Standard PS/2, 2 ou 3 botões\n
 imps2  Microsoft IntelliMouse e compatíveis; ratos PS/2 com\n
3 botões e roda de scroll\n
 exps2  Novos Microsoft IntelliMouse e compatíveis, podem ter\n
mais que 3 botões.  A maior parte dos novos ratos PS/2 são deste 
tipo.\n
 synps2 Synaptics PS/2 TouchPad, encontrados em muitos portáteis\n
 netmouse   Genius NetMouse, 2 botões normais com um botão \Up/Down\ \n
 fups2  O mesmo que \ps2\ mas pode ser necessário para certas falhas\n
nos ratos ou KVM switches\n
 fuimps2O mesmo que \imps2\ 
mas·pode·ser·necessário·para·certas·falhas\n
nos ratos ou KVM switches

#. Type: string
#. Description
#: ../gpm.templates:3001
msgid 
Serial mice: 9-pin or 25-pin serial connector\n
 mscThe MouseSystems protocol.  Most 3

Bug#398979: [INTL:pt] Portuguese translation for libgcr410 (debconf)

2006-11-16 Thread Rui Branco

Package: libgcr410
Version: 2.4.0-5
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for libgcr410's debconf messages
by Rui Branco ruipb _at_ debianpt.org.
Feel free to use it.

For translation updated please contact Rui Branco and CC the Portuguese
translation team traduz _at_ debianpt.org



















# Portuguese translation of libgcr410 debconf messages.
# This file is distributed under the same license as the libgcr410 package.
# 2006-11-16 - Rui Branco [EMAIL PROTECTED] - initial translation
#
#
msgid 
msgstr 
Project-Id-Version: libgcr410 2.4.0-5\n
Report-Msgid-Bugs-To: \n
POT-Creation-Date: 2006-11-16 05:23+0100\n
PO-Revision-Date: 2006-11-16 21:59+\n
Last-Translator: Rui Branco [EMAIL PROTECTED]\n
Language-Team: Portuguese [EMAIL PROTECTED]\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit

#. Type: select
#. Choices
#: ../libgcr410.templates:1001
msgid ttyS0, ttyS1, ttyS2, ttyS3
msgstr ttyS0, ttyS1, ttyS2, ttyS3

#. Type: select
#. Description
#: ../libgcr410.templates:1002
msgid Serial port to which the smartcard reader is connected:
msgstr Porta série a que o leitor smartcard está ligado:

#. Type: select
#. Description
#: ../libgcr410.templates:1002
msgid 
The driver needs to know to which serial port the GemPlus GCR410 reader is 
connected.
msgstr 
O controlador precisa de saber qual a porta série a que o leitor GemPlus 
GCR410 
está ligado.



Bug#362613: [qsynth-devel] qsynth's sample rate vs. jack's

2006-11-06 Thread Rui Nuno Capela
Hi,

Unfortunately, due to fluidsynth design, this issue is not possible to
tackle at qsynth level, at least in a clean way.

Each qsynth engine instance MUST be setup with exact sample-rate value as
the JACK server is running. Unless qsynth is hacked and ask itself on
libjack which sample-rate is due, thus turning into another redundant
dependency which I'll regret.

As from fluidsynth, there's currently no way to change the sampling rate
of the synthesizer after it's been created. The sample-rate of the
synthesizer engine (synth.sample-rate) is the fludisynth setting which is
accessible on the qsynth setup dialog. The jack sample-rate is specified
on jackd command-line.

Users should then watch on the qsynth messages window and check whether
the following warning is issued:

  Jack sample rate mismatch, expect tuning issues
(synth.sample-rate=44100, jackd=48000)

This warning message is issued when any of the fluidsynth engines are set
with disparate sample-rate from the jackd one. Users are urged to get back
to the qsynth engine setup dialog and set the audio sample-rate
accordingly. The new setting will force the restart of the fluidsynth
engine, hopefully with matching sample-rates. OTOH it will be preserved
and there's no need to change it next time qsynth is ran.

Cheers.
-- 
rncbc aka Rui Nuno Capela
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#362613: [qsynth-devel] qsynth's sample rate vs. jack's

2006-11-05 Thread Rui Nuno Capela
Eric Van Buggenhaut wrote:
 
 I maintain the Debian package of qsynth in the official Debian 
 repository.
 
 One of our users came with the request that the Sample rate be 
 automatically disabled when jackd driver is used.
 
 More of this in the bug report:
 
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=362613
 
 This feature makes sense to me but outpasses my maintainer's duties, 
 so I'll tag it as 'upstream' and kindly ask you to implement it.
 

Got it. Will do the change ASAP but those will only be settled on next
dot release.

Cheers.
-- 
rncbc aka Rui Nuno Capela
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#396606: [INTL:pt] Portuguese translation for daemontools-installer (debconf)

2006-11-01 Thread Rui Branco

Package: daemontools-installer
Version:
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for daemontools-installer's debconf messages
by Rui Branco ruipb _at_ debianpt.org.
Feel free to use it.

For translation updated please contact Rui Branco and CC the Portuguese
translation team traduz _at_ debianpt.org

















# Native Portuguese translation of daemontools-installer debconf messages.
# Copyright (C) 2006 THE daemontools-installer'S COPYRIGHT HOLDER
# This file is distributed under the same license as the daemontools-installer 
package.
# 2006-11-01 - Rui Branco [EMAIL PROTECTED]. (initial translation)
#
msgid 
msgstr 
Project-Id-Version: daemontools-installer\n
Report-Msgid-Bugs-To: \n
POT-Creation-Date: 2006-10-26 09:01+0200\n
PO-Revision-Date: 2006-11-01 19:09+\n
Last-Translator: Rui Branco [EMAIL PROTECTED]\n
Language-Team: Native Portuguese [EMAIL PROTECTED]\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit

#. Type: note
#. Description
#: ../daemontools-installer.templates:1001
msgid To build this package, you must run the included scripts.
msgstr Para construir este pacote precisa de correr os 'scripts' incluídos.

#. Type: note
#. Description
#: ../daemontools-installer.templates:1001
msgid 
This package does not contain the daemontools, but only helping scripts 
which will download the daemontools source onto your system and build a deb 
package from it.
msgstr 
Este pacote não contem o daemontools, apenas 'scripts' de ajuda a partir 
dos quais irá fazer o download da fonte do daemontools para o seu sistema 
e construir o pacote deb a partir dele.

#. Type: note
#. Description
#: ../daemontools-installer.templates:1001
msgid 
Use get-daemontools to fetch the source from internet, and build-daemontools 
to build a daemontools package.
msgstr 
utilize o get-daemontools para obter a fonte a partir da internet, e 
build-daemontools 
para construir o pacote daemontools.



Bug#396639: [INTL:pt] Portuguese translation for foomatic-filters (debconf)

2006-11-01 Thread Rui Branco

Package: foomatic-filters
Version: 3.0.2-20060712-3
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for pconsole's debconf messages
by Rui Branco ruipb _at_ debianpt.org.
Feel free to use it.

For translation updated please contact Rui Branco and CC the Portuguese
translation team traduz _at_ debianpt.org
















# Portuguese translation of foomatic-filters's debconf messages.
# 2006, Rui Branco [EMAIL PROTECTED]
# 2006-08-07 - Rui Branco [EMAIL PROTECTED] - initial translation
# 2006-11-01 - Rui Branco [EMAIL PROTECTED] - 5f2u
#
msgid 
msgstr 
Project-Id-Version: foomatic-filters 3.0.2-20060712-3\n
Report-Msgid-Bugs-To: [EMAIL PROTECTED]
POT-Creation-Date: 2006-08-21 01:32-0500\n
PO-Revision-Date: 2006-11-01 21:41+\n
Last-Translator: Rui Branco [EMAIL PROTECTED]\n
Language-Team: Native Portuguese [EMAIL PROTECTED]\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit

#. Type: boolean
#. Description
#: ../foomatic-filters.templates:1001
msgid Enable logging debug output into a logfile (INSECURE)?
msgstr Activar a saída do depuramento para um ficheiro de relatório 
(INSEGURO)?

#. Type: boolean
#. Description
#: ../foomatic-filters.templates:1001
msgid The logfile will be named /tmp/foomatic-rip.log.
msgstr Este ficheiro de relatório terá o nome de /tmp/foomatic-rip.log.

#. Type: boolean
#. Description
#: ../foomatic-filters.templates:1001
msgid 
WARNING: This logfile is a security hole; do not use in production. However, 
if you are having trouble printing, you should enable this option and 
include this logfile in any bug reports.
msgstr 
ATENÇÃO: Este ficheiro de relatório é um buraco na segurança, não o use 
em 
ambientes de produção. No entanto se tiver problemas a imprimir, deverá 
activar esta opção e incluir este ficheiro de relatório em todos os 
relatórios de 'bug'.

#. Type: select
#. Choices
#: ../foomatic-filters.templates:2001
msgid Automagic
msgstr Automagic

#. Type: select
#. Choices
#. Type: select
#. Choices
#: ../foomatic-filters.templates:2001 ../foomatic-filters.templates:5001
msgid Custom
msgstr Custom

#. Type: select
#. Description
#: ../foomatic-filters.templates:2002
msgid Command for converting text files to PostScript:
msgstr Comando para converter ficheiros de texto em PostScript:

#. Type: select
#. Description
#: ../foomatic-filters.templates:2002
msgid 
If you select ``Automagic'', Foomatic will search for one of a2ps, mpage, 
and enscript (in that order) each time the filter script is executed.
msgstr 
Se seleccionar ``Automagic'',·o Foomatic irá procurar um do a2ps, mpage, e 
do enscript (nesta order) de cada vez que o 'script' do filtro é executado.

#. Type: select
#. Description
#: ../foomatic-filters.templates:2002
msgid 
Please make sure that the selected command is actually available; otherwise 
print jobs may get lost.
msgstr 
Por favor verifique que o comando seleccionado está actualmente disponível; 
de outro modo os trabalhos para impressão serão perdidos.

#. Type: select
#. Description
#: ../foomatic-filters.templates:2002
msgid 
This setting is ignored when foomatic-filters is used with CUPS; instead, 
the texttops program included in the cupsys package is always used to 
convert jobs submitted as plain text to PostScript for printing to raster 
devices.
msgstr 
Esta opção é ignorada quando o foomatic-filters é usado com o CUPS; em vez 

disso o programa texttops incluído no pacote cupsys é sempre utilizado para 
converter trabalhos submetidos como texto ('plain text') para impressão em 
dispositivos raster para PostScript.

#. Type: string
#. Description
#: ../foomatic-filters.templates:3001
msgid Command to convert standard input to PostScript:
msgstr Comando para converter 'input' normal para PostScript:

#. Type: string
#. Description
#: ../foomatic-filters.templates:3001
msgid 
This should be the full command line of a command that converts text from 
standard input to PostScript on standard output.
msgstr 
Esta deverá ser a linha de comando completa para o comando que converte 
texto a partir de 'input' normal para PostScript em stardard 'output'.

#. Type: string
#. Description
#: ../foomatic-filters.templates:3001
msgid 
Please note that entering an invalid command line here may result in lost 
print jobs.
msgstr 
Tome nota que ao introduzir uma linha de comando inválida pode resultar na 
perda de trabalhos para impressão.

#. Type: string
#. Description
#: ../foomatic-filters.templates:3001
msgid 
There are some special tags available usable on the filter command line.  
See the filter.conf manpage for details.
msgstr 
Existem algumas 'tags' especiais disponíveis na linha de comando do filtro. 
Veja a página do manual filter.conf para detalhes.

#. Type: boolean
#. Description
#: ../foomatic-filters.templates:4001
msgid Enable PostScript accounting for CUPS?
msgstr Activar a conta PostScript para o CUPS?

#. Type: boolean
#. Description

Bug#396645: [INTL:pt] Portuguese translation for webalizer (debconf)

2006-11-01 Thread Rui Branco

Package: webalizer
Version: 2.01.10-30.1
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for webalizer's debconf messages
by Rui Branco ruipb _at_ debianpt.org.
Feel free to use it.

For translation updated please contact Rui Branco and CC the Portuguese
translation team traduz _at_ debianpt.org


















# Portuguese translation of webalizer's debconf messages.
# 2005, Rui Branco [EMAIL PROTECTED]
# 2005-09-25 - Rui Branco [EMAIL PROTECTED] initial translation
# 2006-08-03 - Rui Branco [EMAIL PROTECTED] 3t4f2u
# 2006-11-01 - Rui Branco [EMAIL PROTECTED] 3f
#
#
msgid 
msgstr 
Project-Id-Version: webalizer 2.01.10-30.1\n
Report-Msgid-Bugs-To: \n
POT-Creation-Date: 2006-10-19 01:38+0200\n
PO-Revision-Date: 2006-11-01 22:10+\n
Last-Translator: Rui Branco [EMAIL PROTECTED]\n
Language-Team: Portuguese [EMAIL PROTECTED]\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit

#. Type: note
#. Description
#: ../templates:1001
msgid Upgrading from a version  2.01.6
msgstr A actualizar de uma versão  2.01.6

#. Type: note
#. Description
#: ../templates:1001
msgid 
WARNING: If you're upgrading from a version  2.01.6, see /usr/share/doc/
webalizer/README.FIRST.gz for details on upgrading your old data!!
msgstr 
ATENÇÃO: Se estiver a actualizar uma versão  2.01.6 veja /usr/share/doc/
webalizer/README.FIRST.gz para detalhes sobre a actualização da sua 
informação antiga!!

#. Type: note
#. Description
#: ../templates:2001
msgid Upgrading from a version  2.01.10-30
msgstr Está a actualizar a partir de uma versão  2.01.10-30

#. Type: note
#. Description
#: ../templates:2001
msgid 
WARNING: This release will move webalizer.conf file to /etc/webalizer  
directory. There was too new features. Please read README.FIST.gz,  README.
gz and new examples/sample.conf.gz in /usr/share/doc/webalizer directory.
msgstr 
AVISO: Esta versão irá mover o ficheiro webalizer.conf para o directório /
etc/webalizer. Existiam demasiadas funcionalidades. Por favor leia README.
FIST.gz,  README.gz e os novos exemplos (sample.conf.gz em /usr/share/doc/
webalizer·directory.

#. Type: string
#. Description
#: ../templates:3001
msgid Directory to put the output in:
msgstr Directório para colocar o output:

#. Type: string
#. Default
#: ../templates:4001
msgid Usage Statistics for
msgstr Estatísticas de utilização para

#. Type: string
#. Description
#: ../templates:4002
msgid Title of the reports webalizer will generate:
msgstr Título para os relatórios que o webalizer irá gerar:

#. Type: string
#. Description
#: ../templates:4002
msgid (your system's hostname will be appended to it)
msgstr (o nome da sua máquina será adicionado ao mesmo)

#. Type: string
#. Description
#: ../templates:5001
msgid Webserver's rotated log filename:
msgstr Ficheiro de relatório rotativo do servidor Web:

#~ msgid What is the filename of the rotated webserver log?
#~ msgstr Qual o nome de ficheiro para o relatório rotativo do servidor web?


Bug#396643: [INTL:pt] Portuguese translation for apt-listchanges (debconf)

2006-11-01 Thread Rui Branco

Package: apt-listchanges
Version: 2.70
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for apt-listchanges's debconf messages
by Rui Branco ruipb _at_ debianpt.org.
Feel free to use it.

For translation updated please contact Rui Branco and CC the Portuguese
translation team traduz _at_ debianpt.org

















# Portuguese translation of apt-listchanges's debconf messages.
# 2005, Rui Branco [EMAIL PROTECTED]
# 2005-09-25 - Rui Branco [EMAIL PROTECTED] - initial translation
# 2006-08-21 Rui Branco [EMAIL PROTECTED] - 10u2f
# 2006-11-01 Rui Branco [EMAIL PROTECTED] - 4f
#
#
msgid 
msgstr 
Project-Id-Version: apt-listchanges 2.70\n
Report-Msgid-Bugs-To: [EMAIL PROTECTED]
POT-Creation-Date: 2006-08-11 16:20+0200\n
PO-Revision-Date: 2006-11-01 21:55+\n
Last-Translator: Rui Branco [EMAIL PROTECTED]\n
Language-Team: Portuguese [EMAIL PROTECTED]\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n

#. Type: select
#. Choices
#: ../templates:1001
msgid pager
msgstr pager

#. Type: select
#. Choices
#: ../templates:1001
msgid browser
msgstr browser

#. Type: select
#. Choices
#: ../templates:1001
msgid xterm-pager
msgstr xterm-pager

#. Type: select
#. Choices
#: ../templates:1001
msgid xterm-browser
msgstr xterm-browser

#. Type: select
#. Choices
#: ../templates:1001
msgid text
msgstr texto

#. Type: select
#. Choices
#: ../templates:1001
msgid mail
msgstr mail

#. Type: select
#. Choices
#: ../templates:1001
msgid none
msgstr nenhum

#. Type: select
#. Description
#: ../templates:1002
msgid Method for changes display:
msgstr Método de visualização das modificações

#. Type: select
#. Description
#: ../templates:1002
msgid 
apt-listchanges can display package changes in a number of different ways.
msgstr 
O apt-listchanges pode mostrar as modificações nos pacotes através de 
diferentes modos.

#. Type: select
#. Description
#: ../templates:1002
msgid 
 pager : use your preferred pager to display changes one page at\n
 a time;\n
 browser   : display HTML-formatted changes using a web browser;\n
 xterm-pager   : like pager, but in an xterm in the background;\n
 xterm-browser : like browser, but in an xterm in the background;\n
 text  : print changes to your terminal (without pausing);\n
 mail  : only send changes via mail;\n
 none  : do not run automatically from apt.
msgstr 
 pager : utilize o seu pager favorito para visualizar as 
 modificações página a página;\n
 browser   : visualizar as modificações em formato HTML utilizando um 
 browser web;\n
 xterm-pager   : como um pager, mas com uma consola xterm em fundo;\n
 xterm-browser : como um browser, mas·com·uma·consola·xterm·em·fundo;\n
 text  : envia as modificações para o seu terminal (sem pausa);\n
 mail  : apenas envia as modificações via mail;\n
 none  : não corre automaticamente a partir do apt.

#. Type: select
#. Description
#: ../templates:1002
msgid 
This setting can be overridden by a command-line option or an environment 
variable.  Note that you can still send a copy via mail with all of the 
frontends except 'none'.
msgstr 
Esta opção pode ser ultrapassada através de uma opção em comando de linha 
ou 
através de uma variável de ambiente. Note que pode sempre enviar uma cópia 
via mail em todas as opções excepto na opção 'none'.

#. Type: string
#. Description
#: ../templates:2001
msgid E-mail Address(es) which will receive changes:
msgstr Endereço(s) E-mail que receberá as modificações:

#. Type: string
#. Description
#: ../templates:2001
msgid 
apt-listchanges can email a copy of displayed changes.  Please enter the 
email address the changes should be sent to.
msgstr 
O apt-listchanges pode enviar por email uma cópia das modificações 
visualizadas.  Por favor introduza o endereço de email para onde estas 
deverão ser estas enviadas.

#. Type: string
#. Description
#: ../templates:2001
msgid 
Multiple addresses may be specified, delimited by commas.  Leave this empty 
if you do not want any email to be sent.
msgstr 
Podem ser especificados múltiplos endereços, delimitados por vírgulas.  
Deixe este espaço vazio se não quiser que seja enviado qualquer email.

#. Type: boolean
#. Description
#: ../templates:3001
msgid Prompt for confirmation after displaying changes?
msgstr Pedir confirmação após mostrar as modificações?

#. Type: boolean
#. Description
#: ../templates:3001
msgid 
After giving you a chance to read the list of changes, apt-listchanges can 
ask whether or not you would like to continue. This is useful when running 
from apt, as it gives you a chance to abort the upgrade if you see a change 
you do not want to apply (yet).
msgstr 
Depois de lhe possibilidade de ler a lista de modificações, o apt-
listchanges pode pedir-lhe se quer ou não continuar. Esta função é útil 
quando se

Bug#395812: [INTL:pt] Portuguese translation for shaper (debconf)

2006-10-27 Thread Rui Branco

Package: shaper
Version: 2.2.12-0.7.3-2
Tags: l10n, patch
Severity: wishlist

Portuguese (pt) translation for shaper's debconf messages
by Rui Branco ruipb _at_ debianpt.org.
Feel free to use it.

For translation updated please contact Rui Branco and CC the Portuguese
translation team traduz _at_ debianpt.org













# Native Portuguese translation of shaper.
# This file is distributed under the same license as the shaper package.
# Rui Branco [EMAIL PROTECTED], 2006.
#
#
msgid 
msgstr 
Project-Id-Version: shaper 2.2.12-0.7.3-2\n
Report-Msgid-Bugs-To: [EMAIL PROTECTED]
POT-Creation-Date: 2006-10-15 08:53+0200\n
PO-Revision-Date: 2006-10-20 21:04+0100\n
Last-Translator: Rui Branco [EMAIL PROTECTED]\n
Language-Team: Native Portuguese [EMAIL PROTECTED]\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit

#. Type: note
#. Description
#: ../shaper.templates:3
msgid shaper needs some kernel modules
msgstr O shaper necessita de alguns módulos do kernel

#. Type: note
#. Description
#: ../shaper.templates:3
msgid 
In order to use the programs in this package, you need the shaper, sch_cbq, 
sch_tbf, sch_sfq, sch_prio, cls_fw, cls_u32, and cls_route kernel modules. 
Some of these (${missing}) can't be seen on your system currently. There are 
several possibilities. You may have compiled them into your kernel 
statically (as opposed to building them as modules), in which case you may 
discard this message. If, however, they aren't available at all (either as 
modules or as compiled-in drivers), you will need to either recompile your 
kernel or use a different kernel-image package. Please read /usr/share/doc/
shaper/README.Debian for more details.
msgstr 
Para usar os programas deste pacote, necessita dos seguintes módulos do 
kernel shaper, sch_cbq,·sch_tbf,·sch_sfq,·sch_prio,·cls_fw,·cls_u32, e 
cls_route.
Alguns destes (${missing})·podem ser vistos normalmente no seu sistema. 
Existem algumas possibilidades. Pode tê-los compilados no seu kernel de um 
modo estático (em oposição à sua construção como módulos), caso em que 
pode ignorar esta mensagem. Se no entanto, estes não estão disponíveis (ou 
como módulos ou como drivers compilados), pode ter que; ou recompilar o 
kernel ou usar um pacote de imagem do kernel diferente. Por favor leia /usr/
share/doc/shaper/README.Debian para mais detalhes.

#. Type: note
#. Description
#: ../shaper.templates:3
msgid 
Once again, if you have these features compiled directly into your kernel, 
then please ignore this note.
msgstr 
Uma vez mais, se possuir estas funcionalidades compiladas directamente 
no seu kernel, por favor ignore esta nota.



  1   2   3   >