Control: notfound -1 debian-builder/1.8.0
Control: fixed -1 1.8.0
Correcting metadata. Note if found version == fixed version then the
BTS assumes the bug is not fixed.
On Fri, 25 Jan 2019 00:23:22 +0100 Klaumi Klingsporn
wrote:
> Package: cd-paranoia
> Followup-For: Bug #889803
>
> On Tue, 14 Aug 2018 19:24:07 + Niels Thykier
> wrote:
> > Source: libcdio-paranoia
> > Source-Version: 10.2+0.94+2-4
> >
> > We believ
Benjamin Barenblat:
> Niels, it looks like you uploaded src:libcdio-paranoia 10.2+0.94+2-4,
> removing the cd-paranoia binary package, because cd-paranoia(1) is
> already included in the libcdio-utils package. However, if you look at
> libcdio-utils in sid, you’ll see this is no lon
in buster but it failed:
>
>
> [...]
Fixed in 2.0.1+dfsg-3 but I forgot the changelog entry.
Thanks,
~Niels
emaining) reverse dependencies and have them fixed.
Thanks,
~Niels
time for buster.
CC'ing Ian, because he is the last person to have uploaded this package
(it is currently orphaned AFAICT).
Thanks,
~Niels
Control: reassign -1 sgml-base
Control: retitle -1 sgml-base: Ensure no (non-essential) dependencies
Niels Thykier:
> Package: debhelper,sgml-base
> Severity: normal
>
> Hi,
>
> The current sgml-base setup relies on await triggers to carry out its
> tasks. Originall
catalogs can now
potentially start a trigger cycle with sgml-base, which makes the
entire setup frail.
I have talked with Helmut (X-CC'ed) and concluded that "-noawait"
triggers won't do here. Accordingly, I think the safest short term
option is to revert to a maintscript snippet.
Thanks,
~Niels
Control: tags -1 fixed-upstream
On Thu, 04 May 2017 17:35:00 + Niels Thykier wrote:
> Control: tags -1 moreinfo
>
> [...]
>
> Hi Chris,
>
> I suspect your patch is wrong because the original code is wrong as well.
>
> $$ in postgres SQL is (often?) used t
code is wrong as well.
$$ in postgres SQL is (often?) used to delimit the definition of
triggers and functions. Therefore, I think you rather want the $$ to be
literal $$ in the config file rather than a ("random") number.
Thanks,
~Niels
- Compat 5 is the bare minimum
- If the package has been relying on dh_install being lenient about
missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].
* Compat level 4 will be removed on the first debhelper upload after
the 15th of June.
Thanks,
~Niels
- Compat 5 is the bare minimum
- If the package has been relying on dh_install being lenient about
missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].
* Compat level 4 will be removed on the first debhelper upload after
the 15th of June.
Thanks,
~Niels
recommended
- Compat 5 is the bare minimum
- If the package has been relying on dh_install being lenient about
missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].
* Compat level 4 will be removed on the first debhelper upload after
the 15th of June.
Thanks,
~Niels
- Compat 5 is the bare minimum
- If the package has been relying on dh_install being lenient about
missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].
* Compat level 4 will be removed on the first debhelper upload after
the 15th of June.
Thanks,
~Niels
recommended
- Compat 5 is the bare minimum
- If the package has been relying on dh_install being lenient about
missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].
* Compat level 4 will be removed on the first debhelper upload after
the 15th of June.
Thanks,
~Niels
you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.
Thanks,
~Niels
[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.
Thanks,
~Niels
[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
severity 720570 serious
severity 720552 serious
severity 720569 serious
severity 720561 serious
severity 720551 serious
severity 720572 serious
thanks
Hi,
I am bumping the OpenJDK-6 removal to release critical; please update /
fix your packages at your earliest convenience.
Thank you,
~Niels
w-popcon-lt-500.txt") are not dealt with before the 8th of
July, the packages will be removed from testing. Note that "dealt
with" may also include downgrading a severity-inflated bug or fixing
affected versions in the BTS.
For reference, the original list is also included.
Thanks,
N
It is also easier for us if we can avoid having to
reintroduce a removed package.
We will check the DELAYED queues before activing the removal hints, so
NMUs in the DELAYED queues will be given a chance to reach unstable.
Thanks,
Niels (on behalf of the Release Team)
The bugs were found using the
On 2013-01-23 20:36, Paul Gevers wrote:
> tags 698661 -moreinfo
> retitle 698661 unblock: openmotif/2.3.3-8
> reopen 673690
> thanks
>
> On 22-01-13 15:21, Niels Thykier wrote:
>> Can you please re-upload openmotif with the M-A (and possibly the
>> hardenin
el/2005/05/msg01085.html.
I have already filed a similar bug report on the other package, lush,
which blocks binutils in a similar way, see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648014.
Regards,
/Niels Möller
--
Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26.
Internet
22 matches
Mail list logo
