Your message dated Thu, 24 Apr 2014 19:51:22 +0200 with message-id <20140424175122.GB4433@betterave.cristau.org> and subject line Re: Bug#744746: transition: plasma-nm has caused the Debian Bug report #744746, regarding transition: plasma-nm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 744746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744746 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: transition: plasma-nm
- From: Maximiliano Curia <maxy@debian.org>
- Date: Mon, 14 Apr 2014 11:04:30 +0200
- Message-id: <[🔎] 20140414090430.15009.31715.reportbug@amadeus.maxy.com.ar>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: transition -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi. The new upstream release of plasma-nm (already uploaded to unstable) bumps the soversion of libmodemmanagerqt and libnetworkmanagerqt, as the api changed, following the modem manager and network manager changes. When I first uploaded the libmm-qt packages an auto-transition was generated, but I obviously failed to act properly on it. As I thought that fixing: #742963 will be enough. Thanks. Ben file: title = "plasma-nm"; is_affected = .depends ~ "libmodemmanagerqt0" | .depends ~ "libnetworkmanagerqt0" | .depends ~ "libmodemmanagerqt1" | .depends ~ "libnetworkmanagerqt1"; is_good = .depends ~ "libmodemmanagerqt1" | .depends ~ "libnetworkmanagerqt1"; is_bad = .depends ~ "libmodemmanagerqt0" | .depends ~ "libnetworkmanagerqt0"; - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-rc7-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJTS6SVAAoJEMcZdpmymyMqYzYP/irShepoNIVjQezzrONZIRH4 nRCzbHGi6YV8+FRtrvfp9kOFspFYTMcUfDK/w6toKvg1V3mVghWs29SV/HIc36V2 UIUR1i+g/clqOAmnwpBTS+90UqczTOHNW5LOU/zd7+OsZaxqWEetKkyJKKexzgs9 0fdwvuZUW7RysPkpwqXNbHKyiddbKhPRv9PqtnQaetch+sfX4g3NInsiqZz5eQfw QjAy9uhAHMYTXwg0Ws2xAq8oGgB9QIkunL2g0344Q85+pL7/8bgIC+8B9Dqsu6x9 bJEws3ohK8lwSILhTJp4p82x/G///pfcmARks9Zw+jHovKCuWMJ9Av65EzZlShVi eeW4IcnhCxp+2ICfWPJeCV39BaMIufcHRYfu6ev9eixD67D5AGVagwrT6yHLThQ6 4D6Q7+ERAnGy4dlxHHzrjsYEzwTZ1U77vJ0qoQiDFD3HhwAxmLn5kYixrRhth9Ru 3c84nr1pZussr2I5HwJBRFzrzyykRrRcRNJ41hdYCF9Yflzvl1Jn4gjaE7bvSVPI YWYVYGtBvV5zLGqkenhzxsaXlsgV/+5I7513BwEvQNyjdN67zQjGUil9lY2Qzl0i SVuSMYu0mllhZSlDx/GU6URrun9XytnBckICxdUYxYwxL4tI7Vlrz3150trFUkbe uYQJj9bXvlQkK+Yb2t0m =fieT -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
- To: Maximiliano Curia <maxy@debian.org>, 744746-done@bugs.debian.org
- Subject: Re: Bug#744746: transition: plasma-nm
- From: Julien Cristau <jcristau@debian.org>
- Date: Thu, 24 Apr 2014 19:51:22 +0200
- Message-id: <20140424175122.GB4433@betterave.cristau.org>
- In-reply-to: <[🔎] 20140414090430.15009.31715.reportbug@amadeus.maxy.com.ar>
- References: <[🔎] 20140414090430.15009.31715.reportbug@amadeus.maxy.com.ar>
On Mon, Apr 14, 2014 at 11:04:30 +0200, Maximiliano Curia wrote: > Package: release.debian.org > Severity: normal > User: release.debian.org@packages.debian.org > Usertags: transition > > Hi. > > The new upstream release of plasma-nm (already uploaded to unstable) > bumps the soversion of libmodemmanagerqt and libnetworkmanagerqt, as the api > changed, following the modem manager and network manager changes. > > When I first uploaded the libmm-qt packages an auto-transition was generated, > but I obviously failed to act properly on it. As I thought that fixing: > #742963 will be enough. > That seems to have taken care of itself, closing. Cheers, JulienAttachment: signature.asc
Description: Digital signature
--- End Message ---