Control: reassign 12 python3-gdbm 3.10.0~b1-3
Control: notfound 12 3.9.12-1
Hi,
You reported a conflict between a package in unstable
(libpython3-stdlib) and a package in experimental
(python3-gdbm/3.10.0~b1-3).
Surely the bug should be reported against the package in experimental,
if at
Le 07 septembre 2018 à 12h24, Emmanuel Fleury disait :
> Hi all,
>
> I just reported this bug to the rubber dev-team. Waiting for the next
> bug-fix, I suggested the following fix:
[…]
This patch does indeed solve my problem, namely #907937, thanks!
But #907988 is unfortunately more general: th
Hi Kurt,
Le 23 août 2018 à 22h20, Kurt Roeckx disait :
> On Thu, Aug 23, 2018 at 02:54:36PM +0200, Antonin Kral wrote:
> > Thu Aug 23 14:46:07 2018 OpenSSL: error:1425F18C:SSL
> > routines:ssl_choose_client_version:version too low
> > Thu Aug 23 14:46:07 2018 TLS_ERROR: BIO read tls_read_plainte
severity 861134 critical
fixed 861134 1.3.6-5.1
close 861134 1.3.6-5.1
merge 861134 861474
thanks
Hello,
I just had a look to try and see what's going wrong.
ifdown gets stuck waiting for
dhclient -6 -r -pf /run/dhclient6.eth0.pid -lf
/var/lib/dhcp/dhclient6.eth0.leases eth0
to complete, which it never does. Even running that command directly
does the same result, never returns.
Version 0.7.5
Package: ifupdown
Version: 0.7.6
Severity: grave
Justification: causes non-serious data loss
Dear Maintainer,
After upgrading to version 0.7.6, ifupdown froze my system during shut
down, stopping at the DHCPRELEASE step.
Reverting to version 0.7.5+nmu1 in testing solves the issue.
For what it's
affects 691847 + libprocps0
thanks
Due to the bug report, apt-listbugs blocked the upgrade of procps but
not of libprocps0, which provoked an equally messy result.
(I'm somewhat assuming that the “affects” command would be enough for
apt-listbugs to avoid the upgrading in such a case, but I'm n
Hi Raphael,
I was indeed missing the console-setup package, and with it works as expected.
(But I don't know what sequence of install / uninstall I must have
done, since aptitude selects the Recommends by defaults; but this
debian was installed some years ago, its history is long… In
particular, I
Hi Michael,
2012/10/1 Michael Prokop
> * Samuel Hym [Mon Oct 01, 2012 at 06:41:10PM +0200]:
>
> > My disk is dm_crypted. After upgrading from 0.107 to 0.108, my system
> > could not
> > boot anymore with the newly generated ramfs: entering the passphrase did
> not
&g
error message as a wrong passphrase.
Downgrading to 0.107 solved the problem.
Best regards
Samuel Hym
--- System information. ---
Architecture: amd64
Kernel: Linux 3.2.0-3-amd64
Debian Release: wheezy/sid
990 unstable ftp.fr.debian.org
500 testing ftp.fr.debian.org
500 stable ftp.fr.debian.org
1
Hello,
Thank you for the link to the FHS.
And there is no doubt that was fairly silly of me (hence the « non-serious
data loss »), I intended some data there to be kept for about one year,
assuming the policy was to leave it up to applications to clean up.
I reported this as a bug thinking about o
at the
installation than that would happen would have been most helpful.
Best regards,
Samuel Hym
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (
Hello,
Same problem, with a weirder remark to make: I don't get the segfault if I
run "xrandr -q" to check the result after the modifying xrandr (noticed
thanks to arandr which follows this behaviour).
Regards,
Samuel Hym
id=74004&atid=539646
some time ago without reaction yet).
Regards,
Samuel Hym
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux
Hi Chris,
> Looks like your two bugs are the same issue - it's not fixed by
> downgrading Jasmin to 2.2.4 - it looks like jasmin will need
> porting to cup 0.11a for this to be fixed.
I opened two bugs because I wasn't sure whether it was the same bug. And
538860 is fixed in 2.3.0-3, but not 5388
Package: jasmin-sable
Version: 2.3.0-2
Severity: grave
Justification: renders package unusable
When run with the cup provided in package 0.11a+20060608-1, parsing
fails immediately:
$ jasmin /usr/share/doc/jasmin-sable/examples/ANewArray.j
ANewArray.j:11: /usr/share/doc/jasmin-sable/examples/AN
16 matches
Mail list logo
