reopen 846074
thanks
--
Hi,
0.4.0-0.2 still not build on all release archs after one week.
reopen and setting severty to RC.
kind regards,
Thilo
Hello Dr. Tobias Quathamer,
i am not sure you are subscribed to pkg dateutils bug list as you uploaded as
Non-maintainer. So this here is to notify you that your upload of
dateutils/0.4.0-0.1 to unstable introduced #846074.
While this bug unfortunate we still thank you for contributions to
Package: libxtables12
Version: libxtables12
Severity: grave
Justification: renders package unusable
Dear Maintainer,
dpkg: dependency problems prevent configuration of iptables:
iptables depends on libxtables12 (= 1.6.0+snapshot20161117-3); however:
Package libxtables12:amd64 is not
Hello Andreas,
Hello Simon,
Andreas Metzler schrieb/wrote:
> Control: reopen -1
> Control: severity -1 serious
>
> On 2016-04-30 Thilo Six <deb...@xk2c.de> wrote:
>> -- --
>
>>> Conditions we want to track:
>>> * installation state of
Hello
i was hit by this also.
I saw this too:
fmtutil [ERROR]: running `pdftex -ini -jobname=mptopdf -progname=context
-translate-file=cp227.tcx mptopdf.tex
Hello RMs,
Hello SRMs,
Hello D-I folks,
i dare to write on this channels because there is a IMHO rather serious bug in
os-prober which up to now went below the radar of everyone it seems.
So this email in the first place is ment to make more people aware of this issue
and here is hope that
Package: libical1
Version: 1.0-1.1
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
after updating libical1 to 1.0-1.2 kalarm does not work anymore.
Manual downgrading libical1 back to 1.0-1.1 fixes this.
Setting high bug priority to prevent migration to jessie at
Hello Marco,
By the way netbase 5.0 migrated to testing.
apt would have removed ifupdown by now if i haven't been very observant. I would
expect this to break networking. How can this be called not to be a bug as in
#672966?
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18
Hello Adam,
Excerpt from Adam D. Barratt:
-- snip --
apt would have removed ifupdown by now if i haven't been very observant. I
would
expect this to break networking. How can this be called not to be a bug as
in
#672966?
apt-get -tsid install ifupdown # should fix it until it migrates.
Hello
since the qt upgarde from 4.7 to 4.8 kalarm chrashes for me, too.
Whenever i try to e.g. delay an alarm.
Not sure if that is the same as the original bug report though.
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
To UNSUBSCRIBE, email
10 matches
Mail list logo
