omnievents_2.6.2-6.1~exp2_source.changes uploaded successfully to localhost
along with the files:
omnievents_2.6.2-6.1~exp2.dsc
omnievents_2.6.2-6.1~exp2.debian.tar.xz
omnievents_2.6.2-6.1~exp2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 26 Feb 2024 07:18:08 +
Source: omnievents
Architecture: source
Version: 1:2.6.2-6.1~exp2
Distribution: experimental
Urgency: medium
Maintainer: Debian QA Group
Chang
The previous patch overlooked some necessary changes in debian/rules that
resulted in file mismatches. Please find attached a corrected patch.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Your message dated Sun, 25 Feb 2024 14:47:37 -0600
with message-id <2208071.NgBsaNRSFp@riemann>
and subject line Re: libgs9-common: URW fonts: Missing glyphs for uk language
has caused the Debian Bug report #841957,
regarding libgs9-common: URW fonts: Missing glyphs for uk language
to be marked as
Hello,
I've recently adopted ghostscript, so I can't answer the direct question of
why libgsN-common ships a dangling symlink. I am curious what folks think of
this.
It's not clear to me whether there are bad consequences of a dangling symlink.
For example is it treated differently than a co
Source: davfs2
Version: 1.6.1-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> checking whether to use NLS
6 matches
Mail list logo
