oxygen-icons_4.4.2-1_amd64.changes uploaded successfully to localhost
along with the files:
oxygen-icons_4.4.2-1.dsc
oxygen-icons_4.4.2.orig.tar.bz2
oxygen-icons_4.4.2-1.debian.tar.gz
oxygen-icon-theme_4.4.2-1_all.deb
kde-icons-oxygen_4.4.2-1_all.deb
Greetings,
Your Debian
Accepted:
kde-icons-oxygen_4.4.2-1_all.deb
to main/o/oxygen-icons/kde-icons-oxygen_4.4.2-1_all.deb
oxygen-icon-theme_4.4.2-1_all.deb
to main/o/oxygen-icons/oxygen-icon-theme_4.4.2-1_all.deb
oxygen-icons_4.4.2-1.debian.tar.gz
to main/o/oxygen-icons/oxygen-icons_4.4.2-1.debian.tar.gz
Your message dated Thu, 08 Apr 2010 10:10:15 +
with message-id e1nzogh-0007rf...@ries.debian.org
and subject line Bug#531004: fixed in oxygen-icons 4:4.4.2-1
has caused the Debian Bug report #531004,
regarding oxygen: Duplicate files could be linked
to be marked as done.
This means that you
kdeadmin_4.4.2-1_i386.changes uploaded successfully to localhost
along with the files:
kde-config-cron_4.4.2-1_i386.deb
knetworkconf_4.4.2-1_i386.deb
ksystemlog_4.4.2-1_i386.deb
kuser_4.4.2-1_i386.deb
kdeadmin-dbg_4.4.2-1_i386.deb
Greetings,
Your Debian queue daemon (running on
kdepim_4.4.2-1_i386.changes uploaded successfully to localhost
along with the files:
kdepim-dbg_4.4.2-1_i386.deb
akregator_4.4.2-1_i386.deb
kaddressbook_4.4.2-1_i386.deb
kalarm_4.4.2-1_i386.deb
kdepim-kresources_4.4.2-1_i386.deb
kdepim-groupware_4.4.2-1_i386.deb
pkg-kde-tools_0.7.0.1_amd64.changes uploaded successfully to localhost
along with the files:
pkg-kde-tools_0.7.0.1.dsc
pkg-kde-tools_0.7.0.1.tar.bz2
pkg-kde-tools_0.7.0.1_all.deb
Greetings,
Your Debian queue daemon (running on host ries.debian.org)
--
To UNSUBSCRIBE, email to
Accepted:
kde-config-cron_4.4.2-1_i386.deb
to main/k/kdeadmin/kde-config-cron_4.4.2-1_i386.deb
kdeadmin-dbg_4.4.2-1_i386.deb
to main/k/kdeadmin/kdeadmin-dbg_4.4.2-1_i386.deb
knetworkconf_4.4.2-1_i386.deb
to main/k/kdeadmin/knetworkconf_4.4.2-1_i386.deb
ksystemlog_4.4.2-1_i386.deb
to
Accepted:
akonadiconsole_4.4.2-1_i386.deb
to main/k/kdepim/akonadiconsole_4.4.2-1_i386.deb
akregator_4.4.2-1_i386.deb
to main/k/kdepim/akregator_4.4.2-1_i386.deb
blogilo_4.4.2-1_i386.deb
to main/k/kdepim/blogilo_4.4.2-1_i386.deb
kaddressbook_4.4.2-1_i386.deb
to
Accepted:
pkg-kde-tools_0.7.0.1.dsc
to main/p/pkg-kde-tools/pkg-kde-tools_0.7.0.1.dsc
pkg-kde-tools_0.7.0.1.tar.bz2
to main/p/pkg-kde-tools/pkg-kde-tools_0.7.0.1.tar.bz2
pkg-kde-tools_0.7.0.1_all.deb
to main/p/pkg-kde-tools/pkg-kde-tools_0.7.0.1_all.deb
Override entries for your
On Mon, Apr 05, 2010 at 05:40:46PM +0200, Eckhart Wörner wrote:
you reported http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563497 some
time
ago. It looks like the X server is crashing, can you therefore please attach
the files /var/log/Xorg.0.log and /var/log/Xorg.0.log.old after
Your message dated Thu, 8 Apr 2010 18:12:04 +0200
with message-id 201004081812.04941.ewoer...@kde.org
and subject line Re: powerdevil: session crash on ac connect
has caused the Debian Bug report #563497,
regarding powerdevil: session crash on ac connect
to be marked as done.
This means that you
#
# bts-link upstream status pull for source package kdemultimedia
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #200688 (http://bugs.debian.org/200688)
# *
#
# bts-link upstream status pull for source package kdebase-workspace
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #547576 (http://bugs.debian.org/547576)
# *
#
# bts-link upstream status pull for source package kdewebdev
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #550998 (http://bugs.debian.org/550998)
# *
#
# bts-link upstream status pull for source package kdepim
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #413085 (http://bugs.debian.org/413085)
# *
#
# bts-link upstream status pull for source package kdebase
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #407279 (http://bugs.debian.org/407279)
# *
I'd like to share approved contacts with you on Boxbe
Here's the link: https://www.boxbe.com/register?tc=226815_1396905862
-neiver
This message was sent at the request of convoycub...@gmail.com.
If you want to opt-out of invitations from Boxbe members, use this link:
attachment: botas+2010_Bauru.JPG
On Friday 09 April 2010 08:30:14 Albert Astals Cid wrote:
hm? eh? what? why would we remove a perfectly valid translation to a
language spoken by 11 million people?
Albert,
I don't think the issue is the removal of the translations, rather the fact
that the locale-code hne isn't defined in
Mark Purcell m...@debian.org writes:
I don't think the issue is the removal of the translations, rather the
fact that the locale-code hne isn't defined in ISO 639-1 ISO 639-2.
My reading of Chhattisgarhi_language[1] shows that the ISO 639-3 code is
hne, whilst the ISO 639-2 code for this
Mark Purcell wrote:
On Friday 09 April 2010 08:30:14 Albert Astals Cid wrote:
hm? eh? what? why would we remove a perfectly valid translation to a
language spoken by 11 million people?
Albert,
I don't think the issue is the removal of the translations, rather the
fact that the
Heyho!
Given a Debian package (kmail, in this case, with installed kdepim-dbg
package) and an extracted source package: how do I properly start gdb (or
ddd or ...) so that it finds both the debugging symbols and the source code?
Just gdb -p pid /usr/bin/kmail doesn't work :-(
(I've only ever
Heyho!
... and, sending the last mail: is it a Debian specific issue, or some local
feature of my KDE profile, or a KDE bug: recently (4.3 to 4.4, but I'm not
sure exactly which updates triggered it), the pinentry window always comes
up behind the kmail windows when I sign email. Confused me
Hello,
Am Donnerstag, 8. April 2010 07:26:03 schrieb Adrian von Bidder:
Heyho!
... and, sending the last mail: is it a Debian specific issue, or some
local feature of my KDE profile, or a KDE bug: recently (4.3 to 4.4, but
I'm not sure exactly which updates triggered it), the pinentry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
Adrian von Bidder wrote:
... and, sending the last mail: is it a Debian specific issue, or some
local feature of my KDE profile, or a KDE bug: recently (4.3 to 4.4, but
I'm not sure exactly which updates triggered it), the pinentry window
Hello,
On ketvirtadienis 08 Balandis 2010 08:26:03 Adrian von Bidder wrote:
Heyho!
... and, sending the last mail: is it a Debian specific issue, or some
local feature of my KDE profile, or a KDE bug: recently (4.3 to 4.4, but
I'm not sure exactly which updates triggered it), the pinentry
Hm. I have another problem - I can't sign any email, I get Bad Passphrase
every time I try to sign it. Pinentry window doesn't appear.
The solution of your problem is to make a rule for this window.
System settings - Window behavior - Window-Specific - New.
В сообщении от Четверг 08 апреля
Hi Boris,
Am Donnerstag, 8. April 2010 11:44:41 schrieb Boris Bobrov:
Hm. I have another problem - I can't sign any email, I get Bad
Passphrase every time I try to sign it. Pinentry window doesn't
appear.
The solution of your problem is to make a rule for this window.
System settings -
On Thursday 08 April 2010 12.02:26 Frank Störzer wrote:
Hi Boris,
Am Donnerstag, 8. April 2010 11:44:41 schrieb Boris Bobrov:
Hm. I have another problem - I can't sign any email, I get Bad
Passphrase every time I try to sign it. Pinentry window doesn't
appear.
The solution of your
Am Donnerstag, 8. April 2010 schrieb Adrian von Bidder:
Given a Debian package (kmail, in this case, with installed kdepim-dbg
package) and an extracted source package: how do I properly start gdb (or
ddd or ...) so that it finds both the debugging symbols and the source
code?
Just gdb -p
Hi, Adrian.
Четверг 08 апреля 2010 18:52:00 you wrote:
On Thursday 08 April 2010 12.02:26 Frank Störzer wrote:
Ok - but that's not a solution, that's more like a workaround. I'll not
file bugs until I can identify the source of the problem, as I haven't
tried with a new created account.
Hi, Frank.
Please, post you gpg-agent.conf.
Четверг 08 апреля 2010 15:02:26 you wrote:
Hi Boris,
Am Donnerstag, 8. April 2010 11:44:41 schrieb Boris Bobrov:
I had the same problem some days ago. Just have a look in your
~/.gnupg/gpg-agent.conf which pinentry will be called and have a
Hallo Boris,
Am Donnerstag, 8. April 2010 17:23:32 schrieb Boris Bobrov:
Hi, Frank.
Please, post you gpg-agent.conf.
here it is (comments are missing):
1 pinentry-program /usr/bin/pinentry-qt4
2 no-grab
[...]
7 allow-mark-trusted
8 default-cache-ttl 1800
9 debug-level basic
10
Hi, Frank.
Thanks, it worked for me.
Четверг 08 апреля 2010 22:00:20 you wrote:
Hallo Boris,
here it is (comments are missing):
1 pinentry-program /usr/bin/pinentry-qt4
2 no-grab
[...]
7 allow-mark-trusted
8 default-cache-ttl 1800
9 debug-level basic
10 disable-scdaemon
34 matches
Mail list logo
