Michael Bann <[EMAIL PROTECTED]> writes:
> The exact error message is the following:
> Preparing to replace libqt4-gui 4.1.3-3 (using
> .../libqt4-gui_4.1.4-1_i386.deb) ...
> Unpacking replacement libqt4-gui ...
> dpkg: error processing
> /var/cache/apt/archives/libqt4-gui_4.1.4-1_i386.deb (--unpa
Package: libqt4-gui
Version: 4.1.4-1
The exact error message is the following:
Preparing to replace libqt4-gui 4.1.3-3 (using
.../libqt4-gui_4.1.4-1_i386.deb) ...
Unpacking replacement libqt4-gui ...
dpkg: error processing
/var/cache/apt/archives/libqt4-gui_4.1.4-1_i386.deb (--unpack):
trying to
Processing commands for [EMAIL PROTECTED]:
> close 368883
Bug#368883: qt4-x11: FTBFS on alpha
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Filipus Klutiero <[EMAIL
PROTECTED]>
>
End of message, stopping processing here.
Pl
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.20
> tags 380097 + patch
Bug#380097: qt4-x11: FTBFS on hurd-i386: missing GNU detection + POSIX
incompatibilities
There were no tags set.
Tags added: patch
>
End of message, stopping pro
Package: kmix
Version: 4:3.5.3-2
Severity: wishlist
With my SoundBlaster Live! 5.1 digital model SB0220 EMU10K1 sound card,
it is difficult to remember the significance of all all the controls and
it would also be good to be able to attach notes to the controls
documenting their significance a
I'd like to adopt this package. I'm already working on the new upstream
version.
BTW: Is there any reason why the source package is gtk-qt-engine while
the actual package name is gtk2-engines-gtk-qt? I'd really like to
rename the package to upstreams gtk-qt-engine.
Best regards,
--
Bastian Ven
Package: kopete
Version: 4:3.5.3-1
Severity: normal
I right clicked a icon on my KDE desktop but the context menu didn't
appear. I already had this several times so I supposed the kwm crashed.
But I also found out that my Kopete windows didn't respond to user
interaction. After killing kopete the
Your message dated Fri, 28 Jul 2006 00:48:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#193527: fixed in kdebase 4:3.5.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Fri, 28 Jul 2006 00:48:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#367090: fixed in kdebase 4:3.5.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Fri, 28 Jul 2006 00:48:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#313375: fixed in kdebase 4:3.5.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Fri, 28 Jul 2006 00:48:21 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#378408: fixed in kdebase 4:3.5.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Fri, 28 Jul 2006 00:48:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368208: fixed in kdebase 4:3.5.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Fri, 28 Jul 2006 00:48:21 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#376958: fixed in kdebase 4:3.5.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Fri, 28 Jul 2006 00:48:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#313375: fixed in kdebase 4:3.5.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Fri, 28 Jul 2006 00:48:21 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#377147: fixed in kdebase 4:3.5.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Fri, 28 Jul 2006 00:48:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368208: fixed in kdebase 4:3.5.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Fri, 28 Jul 2006 00:48:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368504: fixed in kdebase 4:3.5.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Fri, 28 Jul 2006 00:48:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#374087: fixed in kdebase 4:3.5.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
kdebase_3.5.4-1_amd64.changes uploaded successfully to localhost
along with the files:
kdebase_3.5.4-1.dsc
kdebase_3.5.4.orig.tar.gz
kdebase_3.5.4-1.diff.gz
kdebase_3.5.4-1_all.deb
kdebase-data_3.5.4-1_all.deb
kdebase-doc_3.5.4-1_all.deb
kdebase-doc-html_3.5.4-1_all.deb
kappfinder_3
Accepted:
kappfinder_3.5.4-1_amd64.deb
to pool/main/k/kdebase/kappfinder_3.5.4-1_amd64.deb
kate_3.5.4-1_amd64.deb
to pool/main/k/kdebase/kate_3.5.4-1_amd64.deb
kcontrol_3.5.4-1_amd64.deb
to pool/main/k/kdebase/kcontrol_3.5.4-1_amd64.deb
kdebase-bin_3.5.4-1_amd64.deb
to pool/main/k/kdebase/
Probably you are the uploader of the following file(s) in
the Debian upload queue directory:
kdebase_3.5.4-1.diff.gz
kdebase_3.5.4-1.dsc
kdebase_3.5.4-1_all.deb
kdebase_3.5.4.orig.tar.gz
This looks like an upload, but a .changes file is missing, so the job
cannot be processed.
If no .chang
21 matches
Mail list logo