On 23.07.2024 23:33, Soren Stoutner wrote:
Hi,
Alternately, you could mark it as fixed in the current version of fq.
Actually I solved the issue by marking as notfound in fq. This ist not
100% correct, as it was package fq, which introduced the file conflict.
Anyway; nq has now migrated to t
On Tuesday, July 23, 2024 2:23:44 PM MST Preuße, Hilmar wrote:
> On 23.07.2024 23:07, Soren Stoutner wrote:
>
> Hello,
>
>
> > Somehow the system didn’t pick up on the closure in the 1.0-0.1
> > changelog. I would suggest you manually mark it as fixed in 1.0-0.1
> > using:
> >
>
> The bug pa
On 23.07.2024 23:07, Soren Stoutner wrote:
Hello,
Somehow the system didn’t pick up on the closure in the 1.0-0.1
changelog. I would suggest you manually mark it as fixed in 1.0-0.1
using:
The bug page itself [1] looks good and states:
Found in versions fq/0.9.0-2, nq/0.3.1-4, fq/0.0.4-2
F
Preuße,
Somehow the system didn’t pick up on the closure in the 1.0-0.1 changelog. I
would
suggest you manually mark it as fixed in 1.0-0.1 using:
https://www.debian.org/Bugs/server-control#fixed[1]
On Tuesday, July 23, 2024 1:12:42 PM MST Preuße, Hilmar wrote:
> Hi,
>
> for nq the excuse [1
Hi,
for nq the excuse [1] currently reads
Migration status for nq (- to 1.0-0.2): BLOCKED: Rejected/violates
migration policy/introduces a regression
Issues preventing migration:
Updating nq would introduce bugs in testing: #1005961
The bug has been closed in latest upload. What needs to
Thank you both, I understand now.
Johannes
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/caljqy_hq0e6ucksocdv6kgjg36awb+svtonau3b2gzjknqk...@mail.gmail.com
On 2012-03-14 10:14, Johannes Ring wrote:
> Dear all,
>
> One of my packages, syfi, has not migrated to testing, but I fail to
> see why. According to the excuses page [1], it won't migrate because
> "Updating syfi introduces new bugs: #628243", but that bug was closed
> a long time ago. The excus
On Wed, Mar 14, 2012 at 5:14 PM, Johannes Ring wrote:
> One of my packages, syfi, has not migrated to testing, but I fail to
> see why. According to the excuses page [1], it won't migrate because
> "Updating syfi introduces new bugs: #628243", but that bug was closed
> a long time ago. The excuses
Dear all,
One of my packages, syfi, has not migrated to testing, but I fail to
see why. According to the excuses page [1], it won't migrate because
"Updating syfi introduces new bugs: #628243", but that bug was closed
a long time ago. The excuses page also says "syfi (source) has new
bugs!", but i
9 matches
Mail list logo
