Bug#717536: current status
On Wed, 16 Apr 2014 12:19:57 +0530 Ritesh Raj Sarraf wrote: > I see this bug tagged as pending. ... please explain the fix. Looks like you missed the explanation provided in the tag pending: https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=9;bug=717536 # Source package in NEW: http://packages.qa.debian.org/phoronix-test-suite";>phoronix-test-suite; tags 717536 + pending Looking at NEW right now, the phoronix-test-suite package isn't there so I expect you'll need to ask the ftpteam who uploaded it there. BTW: Anibal's tag pending mails are sent automatically. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/19/2015 01:37 PM, James Cowgill wrote: > From the bug: >> RC severity mostly so this shows up on the radars of all the >> right people crossing off the details we need to finalise for the >> release. > > That doesn't apply here. stretch will be released at some point in the future and we will exactly run into the same problem. We already did for Jessie where cmus is now broken by default. > Hmm I personally can't get cmus to break this way but it could be > RC if it breaks in default installations. Did you remove your .cmus configuration directory? If you have an existing .cmus directory, it often works. However, this bug was discovered by someone at my physics department after upgrading to Jessie. Initially, .cmus immediately segfaulted with her old configuration directory. I asked her to rename it, so cmus would use a new directory and she ended up with the application being stuck at the start because of libdnet. It is clearly reproducible. Just did a test install on an unstable system where cmus was never installed and I get: glaubitz@ikarus:~$ cmus getnodeadd: Can not open /etc/decnet.conf Interestingly, on this machine there is a timeout and cmus starts eventually. However, I have seen machines (which had a static IP network configuration) where it hung forever. >> Which is my whole point. > > Then this is a bug in roaraudio / dnprogs, not cmus. No one denies that. However, the problem is that the ROAR people refuse to drop DECnet support and hence Ron asked in [1] to drop ROAR audio support. >> The ROAR developers and maintainers refuse to do that which is >> why we should drop it from cmus. They, for some reason, think >> it's important to support a pre-historic networking protocol. > > I found this bug: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675014 Which was closed with the message "Go away, I don't care." > This is the newer one: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755934 Which is, again, ignored. > But I couldn't find any evidence the _current_ maintainer of > roaraudio has refused to remove DECnet support. The current bug > about it has no replies. Quoting what Ron said who requested the removal in [1]: But basically roar was a disaster on lots of fronts as we were trying to wrap up the wheezy freeze. It was getting dragged in as a hard dependency by packages it was pretty hard to avoid having installed if you had any sort of media support application installed - and the DECNet farce meant that was breaking people's network configuration. It in turn was also depending on the obsolete celt package which we trying to get removed from wheezy - and every attempt to get its maintainers to try to fix these things was met with "what problem? I see no problem here. DECNet is essential functionality, we can't drop it ..." Which basically meant the only choice remaining was to get roar itself removed from wheezy (which meant dropping the deps on it for anything that didn't also want to get removed with it). AFAICT, about the only two actual users of roar in the world are Philipp, its primary author, and his mate Stephan (who filed all the "bring it back" bugs for him). If cmus is Recommending it again, then yeah, dropping that back to a suggests at the very least seems like a prudent move if it's still breaking people's systems ... Though if it's still going to break the systems of people who install it as a Suggests - and its upstream is still refusing to fix that after all these years of it being a known problem, I have to wonder a bit about even the value of that ... but that's really a question for the cmus users and maintainer to decide where the value lies. Adrian > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675610 - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVhTcxAAoJEHQmOzf1tfkTOq4P/R+TWffDmc9w4+LVPrVtNwFR Tg/GSmOGQk6WyXWVqZWD8EZLIOdSovnPcNd9l/Nig6DEI+3/XQmPq0CehX12qIiJ y8hNHwNvwyEKP3qQzYJ6fDtHUFuo+xF2CthHTta54bjF9/LiJktZwh5xSqAJrjk+ tC0g8iXjgffubxpHzMiVuWZAAXHhofzJ6KxUr8ppRHRJcuZCnK8hgjPCf8mqOZli rNj0MMTIu4YQI+cPyAKA6CZP3sgYqqBUKrDSqCKMkMwJypX+7ndFS6LFyJK5VlNM e8yk2bH9yZgy5wy5Rb/cT/me0W64lH2aKpT3tYGjyMtIG2y0Dsgej7+NUEOX64eN L+q4E4o/yR1ruirEeMQWe3YzigbI8xCJHFBslpSoVFG3+s7rgLJPTwo+oWKW0m/Z qAyy/TIyCLDa2V/Fnzf1TWo/5qFA0Y+XtKEApiwEFodMM+XgSWli/fKPbq36XJ6W Nbv9WMWj9w0L2i1lqsbcTFkhtX5TjhuTMNYPf3R0e1guniaz+clUsvwICJv9sJAP sbgFpHZwy6LLAt6mM6fBLO+WFdxucndQftnB5SyPp1ZWJ+yLQdai8uRq7IL0fl8F 0e4VcZrVbCKDgQ5Q4ER/lMpNY7gn3gq/vUpv9rg2ZPw3rbFNPv1llQ6WsuJZft+J cn2tauus+TRYWWIOY5Hq =EfUG -END PGP SIGNATURE-
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Hi, I will post the important part of one of my previous mails again: Is there a chance that you got slp installed? If yes. please try to remove it. On Jessie libslp gets pulled in automatically. I can't reproduce the bug on a fresh debian wheezy VM. And neither on a fresh debian jessie VM. Please attach system informations and a stacktrace to your bug on cmus. Wheezy does not install dnet/roar at all and Jessie installs libroar, libdnet and libslp. Both startup without problems. On Jessie i additionally get a warning about /etc/decnet.conf. Which is the info that decnet is not configured. I also ran two tests: 1. cmus Wheezy with https://archive.org/details/onclassical-quality-wav-audio-files-of-classical-music files: works nicely 2. cmus on Jessie with roaraudio as output: works as nicely as with the default soundserver I did not test on Debian 9 so far. I fear that I can't reproduce your issue. :( Kind Regards, Stephan signature.asc Description: Digital signature
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Stephan, seriously, you are missing the point. Absolutely _no_one_ needs ROAR audio with DECnet support except you and your buddy Patrick. If you desperately need ROAR audio in cmus, then you can rebuild it manually. Debian should not keep packages that are dead upstream, especially when it comes to network libraries. There is _always_ the risk of these being the source of RC bugs. I have fixed dozens of such packages during the Wheezy release phase with NMU uploads because the original maintainer was MIA and we really should try to avoid such problems in future releases. Again, if you need ROAR audio in cmus, just rebuild the package yourself. It's not magic and would save you and us a lot of time and nerves. Thanks, Adrian - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVhUOxAAoJEHQmOzf1tfkTbAEQAJ/DawvDmQJcPQCNQm+MEd1F 0z1tFeGMRhxj/IXX+lkmbokX4R9gw1Zt50KwHSfb13UpP3rbc7VMRhbelcHUMUo2 FLFjb2z3jnfhh/aZ6kHKGWbW6gx7YzX9FDr4UeSoP0IzreFD+XFebp5/Ntoholr3 2I2q3EpOoCLbKhvjqG61jijNxn5eK+2vvXnzpbliwM0dWbmRrup3kzy+EyUBDNJy 4XNZ7u4WYilu7ILxKTkD07hq3dn35IY0PmvXn1jDeT85MfykprIO5cpZWPXg4GD8 4fbZkwNkK72H4VARUBH4Ot0uYCjwSwPKYc56V4djlBY3OdL/pNFLiLdrAG1Dv6A2 XRvRKd7QUSgq9qGZXLHaPPAbQ9IYEP4QNngb4tVCAvDtceoGQZPq1SytGfIr2ixF ZMRH2yVXsL8tP55+jsdSfC9OyBBCE9I32fZqW3bB0JZRIOh1mheVtc+klGBACn9r MeSEbW5Z4lV1SnrrkTcA1pmU5eI9V4qAGyUVD83Vwk7KXbZI/UOo9xeckT2c72Be 0WybQ1Zxi4G6cj+25FZccTHMZq93RScjGTpFgoQMk/z+vaBLVhtHnG/dXrDSBzzf +zdB1EiujXp3gLuF19EcZ62LGri310gJNszOXL1EWIcTkJlFQZwnOhNjBLMn3LtS QT/5hRB+1P8Akmubilwm =7wAC -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/558543b1.4050...@physik.fu-berlin.de
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/20/2015 12:23 PM, Stephan Jauernick wrote: > Is there a chance that you got slp installed? If yes. please try > to remove it. On Jessie libslp gets pulled in automatically. Oh, and btw, removing essential packages like OpenSLP is _not_ an option. That's basically crippling functionality just because the ROAR developers can't get with the time and drop a network protocol that hasn't seen any serious use for at least 15 years. OpenSLP is a useful thing to have on most desktops and most people don't want to uninstall it just because of cmus. Adrian - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVhUR1AAoJEHQmOzf1tfkTBigP/iXJE6t1eTZKiWUa/vFr2RxF ehQQSeCXO1Zeaey5yJKyc29fKD3NqKA9mRc24TYlrCvKYeaI4DNuSS6AOHAyZfEX DkIaTux1kAFqKPsvqvlFANIr7LuRefW8KL8Z/7k5OO1c6eYZ2wvIUp3zuyHDLMPJ Hfs+EKUYtWZJknLIZ63qxdhYwpYTXyrbwN9lRgrRyKdfwYToJ9yN1utPxEmJCBDD G1WQVSR9XXXdxnbAVyXEu+I5pVjtK7FTwRfaoZLctccrHpLfBUC6yrJFBmjHG2rO R+933na9VRJhD3XTEDumMi7uUtwj/+K8H2phwEVgSB2apRGorzTHwcX//MhDe22p QMDMk+Nu2HYF1zBi/uUrZ408wsayGSkTbAKJxZmYLEh9a3WaA7aQc/WsykgDepMh gi6wxp1x/O71GF2dW+7Ve/F1r5queATFAmSfSVvRXnawiZQqCok7pr6if0+5Nnjj x2h08UQhFRZkoGirNy1M4I8hdvyuj9qN9jIYuXt7qHYFXdbHXvS8V1FAiz72KRaP Puu+sguNWtCZ5Ae6P8Bh3R8634+w0+Jzh841S8hXDNXdvTbHB0kYkWvewzJdDjIt 63DurYweB//qaNxB4CGRYqp4RVxkzxJk/ztQVf73z6kHaqymzkXOT0l4saQ8vAfd C0K9DFJjgPSCyAAVuV6f =ia/7 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55854475.9020...@physik.fu-berlin.de
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/20/2015 12:23 PM, Stephan Jauernick wrote: > Is there a chance that you got slp installed? If yes. please try > to remove it. On Jessie libslp gets pulled in automatically. Btw, how did you remove libslp1 without removing libroar2? glaubitz@ikarus:~$ aptitude why libslp1 i cmus Recommends libroar2 i A libroar2 Dependslibslp1 glaubitz@ikarus:~$ Adrian - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVhUTdAAoJEHQmOzf1tfkTmFgQAIC5bLAKeh2yeRi1rNC4YoNE v5okdk/dkvWt+Cf17J0Bmp6AcwAut0Tmqu0FCn0lq6qVrZNKumVIZ1MFFC12OVMd 7WQ80iGOmw7NnmUpLSEB/X5Zfw26fAEZInldsseYURiE8Lsx9OJWRQlYwiRpKnAZ TVH574fVgUxx/FBetrMejRmPwTdkGczMzP0vD7t1PWUCSXtkENiIWW5a7ZU4y/23 XVD24ow8dxpLYXS1hyfuU/8j9RJfh0B98SxKjD8xy6cfXthkLhSxAvF6Ul7zuz6z Y5mbcVFPkO3TKdyLk0KWrA2e8RUX3vUDAFgzIprkmV0zJ4dmndiq5RRXp3A7F7Lz pxXUE6v5aKcDOScw9Lt2dUpBcfo3/aa+3+HzE25m4X6QWzx7BoHYOE+mLSko3NUg ewcZXz5zKnvwMkWugaX8qhORiAlBCI3TS7s7mwLH5fj4ImRcnjXkWOqS8gXGjjem v7Jxw1Cz2WtQdCyoM5u3eLTwIKKALKoJPl7s5Wn8JPshuqOC3FA65kI2IASeaKAr GH4Fet6Bcn2/tJn8w0P6DS+1nnwP7Nr0Do3G4ar+6LBtPT1+eSy8cP9/B+7RCAIc hybGHK+ufIIzc7WvxK/F4E7KlBeLWf6zjwIiJiPgC6MyRBWRA4a2i3myWVqdEoM0 X2X1fdGmETC7YU3Zsb9J =myFt -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/558544dd.1070...@physik.fu-berlin.de
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Am 20.06.2015 um 12:42 schrieb John Paul Adrian Glaubitz: > Stephan, > > seriously, you are missing the point. Absolutely _no_one_ needs ROAR > audio with DECnet support except you and your buddy Patrick. I need roaraudio for myself? He is my buddy? I don't know him at all :o John: please stop writing e-mails like this.. > > If you desperately need ROAR audio in cmus, then you can rebuild it > manually. Debian should not keep packages that are dead upstream, > especially when it comes to network libraries. There is _always_ > the risk of these being the source of RC bugs. This is defintily not the Debian packaging way: "just some people want to use it: build it yourself" > > I have fixed dozens of such packages during the Wheezy release > phase with NMU uploads because the original maintainer was MIA > and we really should try to avoid such problems in future releases. Thanks for fixing RC bugs, this is our job @ Debian :) -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/20/2015 12:52 PM, Patrick Matthäi wrote: > I need roaraudio for myself? He is my buddy? I don't know him at > all :o John: please stop writing e-mails like this.. It's Adrian, not John, and I am just quoting Ron who certainly isn't making this stuff up. It has apparently always Stephan who came forward and ask for ROAR audio reactivation. >> If you desperately need ROAR audio in cmus, then you can rebuild >> it manually. Debian should not keep packages that are dead >> upstream, especially when it comes to network libraries. There is >> _always_ the risk of these being the source of RC bugs. > > This is defintily not the Debian packaging way: "just some people > want to use it: build it yourself" It's definitely the Debian way when a certain package functionality that maybe a handful people need breaks other packages. Then it's your duty as a good Debian maintainer to get rid of the old and broken stuff. And there have been more than one bug report against ROAR that asked to drop the DECnet dependency and you keep ignoring them. >> I have fixed dozens of such packages during the Wheezy release >> phase with NMU uploads because the original maintainer was MIA >> and we really should try to avoid such problems in future >> releases. > > Thanks for fixing RC bugs, this is our job @ Debian :) You are missing the point. I don't have a problem with fixing RC bugs. I have a problem having to fix RC bugs in packages that no one really uses anymore. In case you have forgotten, the release process for Wheezy was dragged along endlessly because the amount of RC bugs would simply not go down. Among such bugs were gems like Iceweasel crashing on sparc or libsnack (used by aMSN) having a buffer overflow vulnerability. Do you really think it's justified to hold the release back because of such ancient software? They introduced automatic removal of packages affected by RC bugs for this very reason and the fact that DECnet is no longer maintained means that ROAR is permanently at risk being affected by RC bugs unless you think you can fix vulnerabilities or other serious bug in an ancient networking stack. Adrian - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVhUhaAAoJEHQmOzf1tfkTZycQALLrt1ECi9I7T0CfD0FsE5ez YAs8s4oqQoByvjxHNNz1Gxvnjb/JS4Amr15FHZ4YjqYYv+/5j0zBoj8JLCUB/j/P OORjTagETPg3oYkej/XAiFH95eOoXf8BMPE5PvQkEAFfHv87nV7ou93yRWVEjZsh cFR1QDjot4ERwKnFqnDdyvvtfrtCfbzRrCrZ9u6jkWiqFi/wjL7bWLERweASfIWQ rn9sQ004uk2Y0euc5TXSoRcM4TuW4IWSUorfUbjC6CSiCu6MZZ1iSqVIe2ls4sFQ 5O/40GbWQbUhzzkBt+iPOD6lWqfn4BVEjwYTaq2XOAAFipBE8Lub7INcGLZ/aIb6 jjy8Sz/r9J5baJMiyXjiWR6LjgmbtE5JyCCU3J1WAzL8EpveLBsqmKXIspWcFoUX pvxGi8nqUoAkg2aJkpAoGbZuQo2Pt37K196ZNmvMgn4hG0ELqYLUD6z6jsIENOUj msmEPqvm1B7KwMIXMZmZhPAehPJmkRJ7SYJ0SpYzaXyjO+0bmgJ2VZlE90vrwStq 1b8p9CbGT7tH3zYv/qKAVn6DlDIeqh9Yzr2wC8Md9Y+rFiddCv1J+3vH9eczEP6D GbzyCK451bOooRCnq/22FyaGNhb7rEDrjLgeqVeMVeItMS2xPZ23AnqtHz5Q5mcx igChqM7E9jkKge2Ky4wl =2CmF -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5585485a.4060...@physik.fu-berlin.de
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Hi Adrian, On Sat, Jun 20, 2015 at 12:47:57PM +0200, John Paul Adrian Glaubitz wrote: > On 06/20/2015 12:23 PM, Stephan Jauernick wrote: > > Is there a chance that you got slp installed? If yes. please try > > to remove it. On Jessie libslp gets pulled in automatically. > > Btw, how did you remove libslp1 without removing libroar2? > > glaubitz@ikarus:~$ aptitude why libslp1 > i cmus Recommends libroar2 > i A libroar2 Dependslibslp1 > glaubitz@ikarus:~$ > Thanks for pointing that out. I was mistaken there. Sorry :( Can you maybe still provide a backtrace/strace log? Also are you running Debian 8 or Debian 9? > Adrian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 Kind Regards, Stephan signature.asc Description: Digital signature
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
On Sat, Jun 20, 2015 at 12:42:57PM +0200, John Paul Adrian Glaubitz wrote: Hi Adrian, Could you please make a bug against roaraudio asking to drop the libdnet dependency? > Stephan, > > seriously, you are missing the point. Absolutely _no_one_ needs ROAR > audio with DECnet support except you and your buddy Patrick. > > If you desperately need ROAR audio in cmus, then you can rebuild it > manually. Debian should not keep packages that are dead upstream, > especially when it comes to network libraries. There is _always_ > the risk of these being the source of RC bugs. > > I have fixed dozens of such packages during the Wheezy release > phase with NMU uploads because the original maintainer was MIA > and we really should try to avoid such problems in future releases. > > Again, if you need ROAR audio in cmus, just rebuild the package > yourself. It's not magic and would save you and us a lot of time > and nerves. > > Thanks, > Adrian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 Kind Regards, Stephan signature.asc Description: Digital signature
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Am 20.06.2015 um 13:02 schrieb John Paul Adrian Glaubitz: > On 06/20/2015 12:52 PM, Patrick Matthäi wrote: >> I need roaraudio for myself? He is my buddy? I don't know him at >> all :o John: please stop writing e-mails like this.. > > It's Adrian, not John, and I am just quoting Ron who certainly isn't > making this stuff up. It has apparently always Stephan who came forward > and ask for ROAR audio reactivation. No, it was your e-mail. To quote it again: "except you and your buddy Patrick." Stop it, seriously.. > >>> If you desperately need ROAR audio in cmus, then you can rebuild >>> it manually. Debian should not keep packages that are dead >>> upstream, especially when it comes to network libraries. There is >>> _always_ the risk of these being the source of RC bugs. > >> This is defintily not the Debian packaging way: "just some people >> want to use it: build it yourself" > > It's definitely the Debian way when a certain package functionality > that maybe a handful people need breaks other packages. Then it's > your duty as a good Debian maintainer to get rid of the old and > broken stuff. And there have been more than one bug report against > ROAR that asked to drop the DECnet dependency and you keep ignoring > them. This is not true. Please attach links/emails where I ignored bug reports/requests (on other channels). > >>> I have fixed dozens of such packages during the Wheezy release >>> phase with NMU uploads because the original maintainer was MIA >>> and we really should try to avoid such problems in future >>> releases. > >> Thanks for fixing RC bugs, this is our job @ Debian :) > > You are missing the point. I don't have a problem with fixing RC > bugs. I have a problem having to fix RC bugs in packages that > no one really uses anymore. In case you have forgotten, the > release process for Wheezy was dragged along endlessly because > the amount of RC bugs would simply not go down. Among such bugs > were gems like Iceweasel crashing on sparc or libsnack (used > by aMSN) having a buffer overflow vulnerability. Do you really > think it's justified to hold the release back because of such > ancient software? OK, so lets drop iceweasel? This is definitly offtopic here > > They introduced automatic removal of packages affected by RC > bugs for this very reason and the fact that DECnet is no longer > maintained means that ROAR is permanently at risk being affected > by RC bugs unless you think you can fix vulnerabilities or > other serious bug in an ancient networking stack. Lets drop package XYZ: it may have got issues we didn't discovered, yet.. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#789407: unable to send openpgp messages
package: pidgin-openpgp version: 0.1-2 severity: grave I can only receive openpgp messages, sending does not work. signature.asc Description: OpenPGP digital signature
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
On Sat, Jun 20, 2015 at 01:02:50PM +0200, John Paul Adrian Glaubitz wrote: > On 06/20/2015 12:52 PM, Patrick Matthäi wrote: > > I need roaraudio for myself? He is my buddy? I don't know him at > > all :o John: please stop writing e-mails like this.. > > It's Adrian, not John, and I am just quoting Ron who certainly isn't > making this stuff up. It has apparently always Stephan who came forward > and ask for ROAR audio reactivation. You're confusing Patrick and Philipp :) Not that it makes a whole lot of difference here, we've had exactly the same sort of rambling dismissal of this as a problem from both of them, every time somebody tried to resolve this (and I was far from the first to have been pulled into trying or needing to do that). James, Re: > But I couldn't find any evidence the _current_ maintainer of > roaraudio has refused to remove DECnet support. The current bug > about it has no replies. None of the people responsible for roar has changed in all the years that people have been having trouble with this and trying to resolve it, so if there's no new responses it seems fairly safe to assume that their previous refusals still stand. I can't say what's right or best for cmus, but what is right for Debian seems fairly self evident to everyone but the roar maintainers. Personally I don't really see that this needs to go to the TC, it's purely a maintainer decision for the cmus people whether they want to support this as a dependency or not. And whether or not that's a sane thing to do basically rests on whether the roar people actually engage with resolving the ongoing concerns, or continue to insist that DECnet being dead and obsolete is some kind of insidious conspiracy theory. Cheers, Ron -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150620164518.ga21...@hex.shelbyville.oz
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Am 20.06.2015 um 18:45 schrieb Ron: > On Sat, Jun 20, 2015 at 01:02:50PM +0200, John Paul Adrian Glaubitz wrote: >> On 06/20/2015 12:52 PM, Patrick Matthäi wrote: >>> I need roaraudio for myself? He is my buddy? I don't know him at >>> all :o John: please stop writing e-mails like this.. >> >> It's Adrian, not John, and I am just quoting Ron who certainly isn't >> making this stuff up. It has apparently always Stephan who came forward >> and ask for ROAR audio reactivation. > > You're confusing Patrick and Philipp :) I am not confused. >> But I couldn't find any evidence the _current_ maintainer of >> roaraudio has refused to remove DECnet support. The current bug >> about it has no replies. > > None of the people responsible for roar has changed in all the years > that people have been having trouble with this and trying to resolve > it, so if there's no new responses it seems fairly safe to assume > that their previous refusals still stand. > > I can't say what's right or best for cmus, but what is right for > Debian seems fairly self evident to everyone but the roar maintainers. There is no depenedencie of *roar* to dnet at all. > > > Personally I don't really see that this needs to go to the TC, it's > purely a maintainer decision for the cmus people whether they want to > support this as a dependency or not. And whether or not that's a sane > thing to do basically rests on whether the roar people actually engage > with resolving the ongoing concerns, or continue to insist that DECnet > being dead and obsolete is some kind of insidious conspiracy theory. Sorry Ron, but you are realy the last person who is responsible to discuss about topic at all. Same topic as with mumble/celt... -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/20/2015 06:56 PM, Patrick Matthäi wrote: >> I can't say what's right or best for cmus, but what is right for >> Debian seems fairly self evident to everyone but the roar >> maintainers. > > There is no depenedencie of *roar* to dnet at all. Excuse me? glaubitz@ikarus:~$ apt-cache depends libroar2 |grep dnet Depends: libdnet glaubitz@ikarus:~$ > Sorry Ron, but you are realy the last person who is responsible to > discuss about topic at all. Same topic as with mumble/celt... Well, he's right and I am pretty sure that all these bug reports with requests to drop DECnet support by various users agree: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755934 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675014 > https://bugs.launchpad.net/ubuntu/+source/cmus/+bug/923027 Patrick, why are you so incredibly stubborn and refuse to accept that no one wants to have DECnet packages installed on their system when they want to use ROAR or cmus? Adrian - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVhaKzAAoJEHQmOzf1tfkTTcwP/102v1XDucGnxEhP4d2KvRgc 4X2PogWQephFOhA/A1QDCA6jgA1if3uQSpprtNZMmF+VXkzf8sFedKaUEdXyDt93 RdViAShWA9RjTd82tq+vQna6dA+MRJ1UutuliUDH9iK6+a8TgRrnB6YQJp/tKmj9 +OQP42Fezb2saFuxQpsLV0FcjCEcgbjNDt8FEARUSk2kPhcDrybowKq0IAuG4CC6 Of3GCirZuwlRic5bV2/ZwJ3wgRykQ1wfjtseHydBXByLCYa5nRsngfHxkaYZiSQc lKdpqiKuWC6K8M0xhQVkN6jeOotqknPxXnUaDiKr2UYFeJrBy2CVJahtI52BaI0v xN2GF4iaiHYRPm8z5mpPAl1R+EEL05TlGcdzkerNFSjkfnjd/HIHCGaA8i1jl+Rk 09g378rjYMNMG+TYk9C6B/4iUE1Do2CXLSc9ph4pS0aWbv5EJcHi5dizllA3n/D7 xWMQkGATqPv3TwVbhc2JP+OQTUQdMpGJ0hifngeY7CDuhcMZE8fki2JafXZO6THB yQWGx9K0ZNCmyM47qk97Rery5yQCDmW2HJahUWABopyPfDlGdOSjCAQ5oO6PyfCO /Ewy0EAZ9VIWu0DW1d8poFXai0CUsuaEmJDd9PPc22G9lgZ5FNES5r0V/aHCR/7d YIAGnRyPY5rl3FuT+TAo =NLrR -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5585a2b3.5010...@physik.fu-berlin.de
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/20/2015 01:03 PM, Stephan Jauernick wrote: > Thanks for pointing that out. I was mistaken there. Sorry :( No worries, I don't think we disagree about the problem in general. > Can you maybe still provide a backtrace/strace log? This isn't really necessary as this isn't cmus crashing, it's cmus getting stuck because it's apparently waiting for the DECnet stack to become ready. I can't imagine that you cannot reproduce this on a clean install, I could reproduce it on all machines running at least Jessie. > Also are you running Debian 8 or Debian 9? I'm running unstable. But this problem is reproducible on Jessie and Stretch as well. After all, it were users at the department where I work who complained that cmus stopped working after upgrading to Jessie. There were no issues on Wheezy as the cmus version there was compiled without ROAR support. Adrian - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVhaQhAAoJEHQmOzf1tfkT58cQAMRzdF87vJBa2QSka8LCKPjH IBREOlAtKWjIGnUs7dDTL+wFc07QWcOorf7jQRAS80u4XPUw7ZitGf7+YV5/ABiv 7rN3d09CEPz3/cQdC3lia+ohrvyHUUDV5tTp4Y/tCCia4fqpXMhNOvOCvsFufRpQ gRy8vYq3GO5Pjfc6bcF48TR93bdrIMgpXXtn0aJz4UXX6LSgL5IEKMG9rFovWgc3 jhLbzQ1mOALdOa3ZSdGHP/8pP/Tvhf+gFHAARSCv9SoaRu5lihqqyio8WJYunP+V nopJ1mUSRKWw4ez17yerVesP33ymdQwa3FQCHqWGRxKHe79qxI06ZnrX8xx0JIJ5 tKA6KnBmwTvmTWxMc1VzbfYNBTcgQcD1VBQ6z/SFpn4N3mtcDtARw+G7UG3DW4n8 4zIMyhdZmFlf1UqIIK1mVIJIKtseoTPy++7IicAGQBVf+uE8b4ipFCsLy+/e4xT6 sV7aKeZxQtXA/70xEIwOcRxcSnwMU+bILDP4K7+tA2GSdVjK+kpmvRuQiqlZvJbD DCtCyUoX5vwU6e5jCqV3uuJTJnSVpc2zGepvqn/UxtNTgoKsrDukrD0Sc2HZeSzN FJVZKp7p5NUkg2Fd9fT0bVQ+Il7Aop7FmjxqHLNkCc89f1zD9oLcIOLdxJAqTITN uo7CzC2HJFJID/nI0hI0 =SIMg -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5585a421.6080...@physik.fu-berlin.de
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/20/2015 01:06 PM, Stephan Jauernick wrote: > Could you please make a bug against roaraudio asking to drop the > libdnet dependency? There are already three of such bug reports: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755934 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675014 > https://bugs.launchpad.net/ubuntu/+source/cmus/+bug/923027 This is why Ron asked in [1] to drop ROAR audio support in cmus because he felt it was pointless to continue the discussion with Patrick who thinks that in 2015 DECnet support is essential. Adrian > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675610 - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVhaTVAAoJEHQmOzf1tfkT41cP/0BKOo+OhoXmF1devyIguX8R N80UjTOc6wI4Kc7WZROquz0NtgYvPKm+FOz55tFyMBRtsRWYeXryic49IT+2gs23 vOzkt//pI8B2TOJRS5ML965K6BVRsu0jj6tKzR0JLdsHpeUx5ZTvsrH6KNU6gR49 GB/5bNKm4LBu+CLH7ynA4QQW/MjEIFNyXZTL8eBwvs1fkyJLW88POYVD2/xP3bsM biEBxIURxl6f5QpEw85mSccTYxGmaXAbxFKpw/7rauhxRpSgTFTrL/SybpUYaXUk lvxqhecn5Bp84oQ6fiWPpKBmgo7YQeUq6oRkfwDUAj6x9UC0I01MUaKtclIisDVU wRxAR5v0M/O5Pwu7oUbftuKXp6LXd3JFju3sXmp1caDTFaM3y9mBpHCt2j2/AeOB A5/0btu0nMzCZg5FAynSkAnqlJR55o3Elo1j2b3KD+HTxy2qYmipqb3eryQ4Xqg2 iDAHDn8cVVLZSpZ2qwLCiVl0rWmlXpVrRfnBfs80vxBXkUyV4k9yTTvKlfFpU1Nk sppEqoPZnK6FhdD231n3ImZBL6wNlbXq37E9MQBLakgYyVlT2urBAAk+ubn8iNxy G1/iAbJ8QSyZIXDKvhAjnWPufz2PIs4yMfZQyamMTUq+Yj05LsSD6FcsNGDciinM 6dnCCLmWBp7IJTLWWkjS =7Uin -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5585a4d5.7030...@physik.fu-berlin.de
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/20/2015 01:12 PM, Patrick Matthäi wrote: >> It's definitely the Debian way when a certain package >> functionality that maybe a handful people need breaks other >> packages. Then it's your duty as a good Debian maintainer to get >> rid of the old and broken stuff. And there have been more than >> one bug report against ROAR that asked to drop the DECnet >> dependency and you keep ignoring them. > > This is not true. Please attach links/emails where I ignored bug > reports/requests (on other channels). > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755934 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675014 Are you actually reading bug reports? Serious question. >> You are missing the point. I don't have a problem with fixing RC >> bugs. I have a problem having to fix RC bugs in packages that no >> one really uses anymore. In case you have forgotten, the release >> process for Wheezy was dragged along endlessly because the amount >> of RC bugs would simply not go down. Among such bugs were gems >> like Iceweasel crashing on sparc or libsnack (used by aMSN) >> having a buffer overflow vulnerability. Do you really think it's >> justified to hold the release back because of such ancient >> software? > > OK, so lets drop iceweasel? This is definitly offtopic here No, we dropped sparc as a release architecture as a result in case you missed that. >> They introduced automatic removal of packages affected by RC bugs >> for this very reason and the fact that DECnet is no longer >> maintained means that ROAR is permanently at risk being affected >> by RC bugs unless you think you can fix vulnerabilities or other >> serious bug in an ancient networking stack. > > Lets drop package XYZ: it may have got issues we didn't discovered, > yet.. No, let's drop package XYZ which _no_one_ maintains both upstream and downstream. It's absolutely a common practice in Debian and happens all the time. Here are some examples: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=206866 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=288112 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=179392 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=182434 I'm sorry Patrick, but I am starting to have doubts that you know how to do a proper job as a maintainer. You apparently don't read bug reports (as shown above), you don't know the details about your *own* packages (you claimed that libdnet is not a dependency which is simply untrue) and you apparently have never heard that Debian does, in fact, remove packages that are either buggy or no longer in active upstream development. We may really need to forward this to the technical committee and ask them to make a decision over the removal of the DECnet dependencies in ROAR as you are apparently completely out of touch with reality. Adrian - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVhaguAAoJEHQmOzf1tfkTjbAP/1mlLWcfl8KsBG4PphR1N+KF HJd/902m7bzEXZ6oKwOIwfAvDVN5VFS9WMELSVxx2fw7vthX/x5+Dvb858E3JqPa hk+R7yxobij1qCAz6c7P8L7DFJPvH3M/33WZllznh/QW/iL1mJCsO8MHImd9Phpn jNiFperP1KhHsWwTx94OMEQF0XZYWnaSAthEmkoDI0eN5o41Cy6xY8qM0o74vHgO t6KvXvMslquCvZo8ZCqf5xaPlbVjCcxWjmhPtRPiq3mqPQfSc1HVgQczMb28+Oyf /NfSH65LryzGyLwLX4IcELkmdcntL6YrbkDR8mVxOMFJorl5oNjBgdjfZQ3otDYI Cm2MwAdoBJgVb6aMrVVVbISreVYghes+dDkQmuiq7cCjJJMIY0zhU1GYkOB2LZwc V2O63WYVKvpUyftsXDn/xzQ7+kP5hjHRRTVCFzz8VigHk1+fmHYaZJNokXCcnHeh c/XTiW1N7dbcGnbGW5WOc77kIM4slRH/s+iMbJtT9IhQ8TgRgAIDqGCRYiMqu6/R cdtRAveQKFQwDHc3NNVxorBb1RYSm6e0oMzHAl2i/Au8LE3pNd9BP0+0LwIqkK7P vAeyDTVEXwStuGr8a9jmflKG17Fn5X65igEsPPb/xPM9W2RNUA/sbO8kPmQijcY3 mQuK5wPOkDx5xsuEuHiA =dkWi -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5585a82e.6010...@physik.fu-berlin.de
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Quoting John Paul Adrian Glaubitz (2015-06-20 12:34:25) > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 06/20/2015 01:03 PM, Stephan Jauernick wrote: > > Thanks for pointing that out. I was mistaken there. Sorry :( > > No worries, I don't think we disagree about the problem in general. > > > Can you maybe still provide a backtrace/strace log? > > This isn't really necessary as this isn't cmus crashing, it's cmus > getting stuck because it's apparently waiting for the DECnet stack > to become ready. > > I can't imagine that you cannot reproduce this on a clean install, > I could reproduce it on all machines running at least Jessie. Please provide the command to reproduce _without_ --with-suggests option enabled! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/20/2015 07:56 PM, Jonas Smedegaard wrote: >> I can't imagine that you cannot reproduce this on a clean >> install, I could reproduce it on all machines running at least >> Jessie. > > Please provide the command to reproduce _without_ --with-suggests > option enabled! Jonas, I think you need to re-read what I wrote. Currently libroar2 is a Recommends and _not_ a Suggests: glaubitz@ikarus:~$ apt-cache depends cmus | grep libroar2 Recommends: libroar2 glaubitz@ikarus:~$ My elaborations regarding "--with-suggests" were regarding the case that Alessio would drop libroar2 from Recommends to Suggests. Currently cmus is definitely getting stuck on a _fresh_ install, simply by installing with "apt-get install cmus". Adrian - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVhapVAAoJEHQmOzf1tfkTwUoP/3hSKp9hFYubdqUtE4o24hU4 NtGYrYIYf77tYR0a8/TrvBvd2vcATlaBhICJzWmLI3q2ptOuCKzfvJsJHFj33s6M UcMD8itnjfQGMLEhP6vmc/ucAQyWGiqaraChE7y6KMQ9GGPgHhWoGTXFFZ2hYSsL l6uGhP7EAt0PP7MZUN7h3QqciLEtnb+Bc/awzvTFK8lefjQ9I8E2i0cyNhw5Nw0z NGg57saH+LBYh8HnIcp6W4n5QTIU9HqZursR2rBFzlQ3OueebdnKKQrUSNF3oTTu OcvrcaCBpZGgIhOt8KnjsLJFKSjVmhScrNeHR/hwkzpxcPQaC7jSTzdqQkSWN35e TI4JecsYoB2nsScLPtdXFNytPhqi/B9HfykMvmthNhFqK4BnGdmwv8uDYi2lbtU/ nTkKFAztZZlVDU/Voiy2gqWKjZnHciGr7yl1VU+V6RT7D7cSfmD+wvGX0Nr1TUTu 7biHDxy4lINm+PJjejWFnYBwoEsUhe8Kn78IMaq5CZVsN5HQzwZAfCDLwzcRZSIk hLBPH9bJIqFmczebSH4/XGx+47oLagkC9hvQdh0AdRu9qGxCjT/DT46Cr5c039Xu Q92jtn2Th/xYb9fR2rRwlDLj8GHbmWTaeB1pYibrtHuBcFAqND16KWrpya2iF8/6 WxAvx4lhYnVrryielSjQ =fJqp -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5585aa55.1090...@physik.fu-berlin.de
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Am 20.06.2015 um 19:28 schrieb John Paul Adrian Glaubitz: > On 06/20/2015 06:56 PM, Patrick Matthäi wrote: >>> I can't say what's right or best for cmus, but what is right for >>> Debian seems fairly self evident to everyone but the roar >>> maintainers. > >> There is no depenedencie of *roar* to dnet at all. > > Excuse me? > > glaubitz@ikarus:~$ apt-cache depends libroar2 |grep dnet > Depends: libdnet > glaubitz@ikarus:~$ dnet-common to be exactly now. libdnet is not problematic at all > >> Sorry Ron, but you are realy the last person who is responsible to >> discuss about topic at all. Same topic as with mumble/celt... > > Well, he's right and I am pretty sure that all these bug reports > with requests to drop DECnet support by various users agree: > >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755934 It is a packaging issue of roaraudio. Nothin decnet related. >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675014 This is fixed since years >> https://bugs.launchpad.net/ubuntu/+source/cmus/+bug/923027 >This is Ubuntu, not Debian. And in Debian there is no depedencie on libdnet-common. > > Patrick, why are you so incredibly stubborn and refuse to accept > that no one wants to have DECnet packages installed on their > system when they want to use ROAR or cmus? John... There is just a depends on a library pushing not more than yet another lib on the system. Why? Because roaraudio is using some functions of it. Where is the problem? Nowhere. So John. What is *your* problem? I am not "stubbhorn" about this "issue". It just looks like you made it to your religion to argue against it at all without any arguments. You argue with release critical bugs which do not exist etc etc.. Please use your free time to do something more innovative, like planting a tree.. But never again add me to a troll discussion just because Ron wants so. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Am 20.06.2015 um 19:51 schrieb John Paul Adrian Glaubitz: ld the release back because of such ancient >>> software? > >> OK, so lets drop iceweasel? This is definitly offtopic here > > No, we dropped sparc as a release architecture as a result > in case you missed that. Because of roaraudio? Oh no? Ok this is a realy related issue here... X affected Y and Z was the result, so roaraudio is affected. Please discuss this with the iceweasel team if you have got enough free time. > >>> They introduced automatic removal of packages affected by RC bugs >>> for this very reason and the fact that DECnet is no longer >>> maintained means that ROAR is permanently at risk being affected >>> by RC bugs unless you think you can fix vulnerabilities or other >>> serious bug in an ancient networking stack. > >> Lets drop package XYZ: it may have got issues we didn't discovered, >> yet.. > > No, let's drop package XYZ which _no_one_ maintains both upstream > and downstream. It's absolutely a common practice in Debian > and happens all the time. > > Here are some examples: > >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=206866 >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=288112 >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=179392 >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=182434 You are just quoting mostly invalid closed reports which are as old as I am :D And it is not my package, just FYI > > I'm sorry Patrick, but I am starting to have doubts that you > know how to do a proper job as a maintainer. You apparently > don't read bug reports (as shown above), you don't know the > details about your *own* packages (you claimed that libdnet > is not a dependency which is simply untrue) and you apparently > have never heard that Debian does, in fact, remove packages > that are either buggy or no longer in active upstream > development. You are open to post to d-d@l.d.o something like "pmatthaei is not able to do Debian work". I will make your life a bit easier and CC'ing d-d now.. It makes no sense but it seems like this is the best way to follow an issue to it's own . > > We may really need to forward this to the technical committee > and ask them to make a decision over the removal of the > DECnet dependencies in ROAR as you are apparently completely > out of touch with reality. Please, do it. But *again*: IMMEADITLY STOP(!) adding/quoting/responding me for stuff where I never were responsible for! And also for things like who is my "buddy" or not, especially if they do not know the person at all.. I am just doing my Debian Developer work, also for the roaraudio packages, but it looks again like you and Ron just want to fool.. .. .. . -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Quoting John Paul Adrian Glaubitz (2015-06-20 13:00:53) > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 06/20/2015 07:56 PM, Jonas Smedegaard wrote: >>> I can't imagine that you cannot reproduce this on a clean >>> install, I could reproduce it on all machines running at least >>> Jessie. >> >> Please provide the command to reproduce _without_ --with-suggests >> option enabled! > > Jonas, I think you need to re-read what I wrote. Currently libroar2 is > a Recommends and _not_ a Suggests: > > glaubitz@ikarus:~$ apt-cache depends cmus | grep libroar2 > Recommends: libroar2 > glaubitz@ikarus:~$ I agree that cmus pulls in libroar2. Why is that dangerous? > My elaborations regarding "--with-suggests" were regarding the case > that Alessio would drop libroar2 from Recommends to Suggests. If you mean to say that "--with-suggests" is irrelevant to discuss here, then I agree: Use of special package install options should be irrelevant when dicussing whether cmus is dangerously broken or not. If you mean something else then please elaborate. > Currently cmus is definitely getting stuck on a _fresh_ install, simply > by installing with "apt-get install cmus". On those systems where you experience cmus being stuck, is the package "dnet-common" also installed (or was it ever)? If so, you will need to figure out how that got installed, and I am quite certain the cause is *not* cmus and therefore this bugreport against cmus is bogus. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/20/2015 08:25 PM, Jonas Smedegaard wrote: >> glaubitz@ikarus:~$ apt-cache depends cmus | grep libroar2 >> Recommends: libroar2 glaubitz@ikarus:~$ > > I agree that cmus pulls in libroar2. Why is that dangerous? Because libroar _depends_ on libdnet which is an unwanted dependency for most users for one: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755934 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675014 > https://bugs.launchpad.net/ubuntu/+source/cmus/+bug/923027 And libdnet breaks cmus on some configurations as I have explained now several times. >> My elaborations regarding "--with-suggests" were regarding the >> case that Alessio would drop libroar2 from Recommends to >> Suggests. > > If you mean to say that "--with-suggests" is irrelevant to discuss > here, then I agree: Use of special package install options should > be irrelevant when dicussing whether cmus is dangerously broken or > not. > > If you mean something else then please elaborate. No, I'm sorry. You misread what I wrote. Really, read my first message in this bug report. >> Currently cmus is definitely getting stuck on a _fresh_ install, >> simply by installing with "apt-get install cmus". > > On those systems where you experience cmus being stuck, is the > package "dnet-common" also installed (or was it ever)? No. I never claimed that. > If so, you will need to figure out how that got installed, and I am > quite certain the cause is *not* cmus and therefore this bugreport > against cmus is bogus. It isn't bogus because, as several people have explained several times, the maintainer of roaraudio refuses to drop DECnet support. Adrian - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVhbT5AAoJEHQmOzf1tfkTfXoP/RYcW0SdV2rtCoXTt+eCWD4B 80Bp4i7rX+oNXod6CiGX5gsF9d9inLTH0Mpbk9kgc1LOG6VWESHJ+M6cPyvQBGjU d8oRcpqi7tuTfzlc4Fv1POyj8EZRDvWFZAznh/GZyC70Cv28elZupz4MDPlKVlMs lWxshWYyrp9K+Kbty8WjloWvmqtHLE6YR3/akkTYbWlVPW7rMBPtFwcx2C5KE2f0 dyfz27iAUBEyTitWIc6yndU1EFlWCRYk4Y74zxU19R2rt7cICMoTY0E3F3iYgrl0 NTq0Bq+oEvR56ipoTqUYw9in9DoZeJKvUeoSITXIBxsv7U7nIQP+WdMfI8VApdEV NkE0HlQqk4TGjievFtnBbWDpan9hHMQCP4rx6FMgN2TcGm4PpbSJnvy58jQ7K5Fg AabE7wxuWL0ZeqneogPx0vFBLolOEQg2bBjW5pFzWh0nb/bTqwPk+Pev7Eit2IQv /WHLNUF1xQp+0s4klCaoBew+0h4HTbCKwxp7MPGvEb7kC1iikME/sY8rL3wiau4R Z6Kvkj0aAMz8J1l+AcTXV5YP+mc6cLd/e4Rjg9DvT1Bian6TmVE3JFvr1OQQeTY5 p/0UTsi+w21wX7cxyG6nqv67znriIq2oIzzwOQ1Q2tAd5CJS5wUuVWZDk7sgDPS4 H7ofH26Jxg5Cl1ErBorf =FRG2 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5585b4f9.9090...@physik.fu-berlin.de
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
On Sat, 20 Jun 2015, Patrick Matthäi wrote: > Am 20.06.2015 um 19:51 schrieb John Paul Adrian Glaubitz: > ld the release back because of such ancient > >>> software? > > > >> OK, so lets drop iceweasel? This is definitly offtopic here > > > > No, we dropped sparc as a release architecture as a result > > in case you missed that. > > Because of roaraudio? Oh no? Ok this is a realy related issue here... X > affected Y and Z was the result, so roaraudio is affected. Please > discuss this with the iceweasel team if you have got enough free time. Can we please stick with discussing the technical details of this issue instead of attacking eachother? There's clearly a bug here, but even after reading this bug log, I've had to do research on my own to determine what that issue is. If the libroar2 maintainers which to keep decnet support, then someone should probably figure out how to circumvent waiting for the DECnet to settle when it isn't actually configured, and propose a patch to do that. Even just checking for the existence of dnet-common or similar would probably be enough. -- Don Armstrong http://www.donarmstrong.com -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150620193825.gh5...@qor.donarmstring.com
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Hi Adrian, On Sat, Jun 20, 2015 at 07:34:25PM +0200, John Paul Adrian Glaubitz wrote: > On 06/20/2015 01:03 PM, Stephan Jauernick wrote: > > Thanks for pointing that out. I was mistaken there. Sorry :( > > No worries, I don't think we disagree about the problem in general. > > > Can you maybe still provide a backtrace/strace log? > Please do for the reasons mentioned below. Also these are considered standard of a good bug report. > This isn't really necessary as this isn't cmus crashing, it's cmus > getting stuck because it's apparently waiting for the DECnet stack > to become ready. > > I can't imagine that you cannot reproduce this on a clean install, > I could reproduce it on all machines running at least Jessie. > I can't even reproduct it on unstable. I only get the decnet warning and then cmus starts up with about 5 seconds delay on the first start and from then on instantly. My steps to reproduce in all 3 Debian versions: 1. Install a fresh VM from Netinst in VirtualBox 2. Accept the defaults for Desktop and additionally select SSH Server 3. Install cmus as root 4. Change back to a normal user 5. run cmus 6. 7. quit it again > > Also are you running Debian 8 or Debian 9? > > I'm running unstable. But this problem is reproducible on Jessie > and Stretch as well. After all, it were users at the department > where I work who complained that cmus stopped working after > upgrading to Jessie. There were no issues on Wheezy as the cmus > version there was compiled without ROAR support. > Thanks thats another thing i will test. Can you maybe give us a list of installed packages? I will assume that these are desktop machines which where used for some time before upgrading. Unless you can assure me these are fresh installs before updates, we can only assume that there are other packages installed which interfere. I am currently upgrading my fresh debian 8 vm fron yesterday to debian unstable. I will write back when its done and I got to test that. Also does it just hang or will cmus start after some time? > Adrian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 Kind Regards, Stephan signature.asc Description: Digital signature
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/20/2015 09:52 PM, Stephan Jauernick wrote: > Please do for the reasons mentioned below. Also these are > considered standard of a good bug report. No, the problem is apparent and I don't really want to debug libdnet. You are still trying to boil this down to the mere problem with cmus, but that's just a side effect. The real point is that roaraudio depends on an unmaintained piece of core software which Debian would like to get rid of. It doesn't really matter if you're able to fix this bug now as this won't change anything about the unmaintained status of dnet-progs. So, please refrain from continuing the focus on this particular problem with cmus, this is not the main issue, it's just the trigger that brought me to the attention of this problem. I won't be bothered to continue the discussion anymore if your only concern is this particular problem with cmus but just eventually hand over the issue to the TC. > I only get the decnet warning and then cmus starts up with about 5 > seconds delay on the first start and from then on instantly. Which is _exactly_ the problem. It just appears that for some network configurations it seems to get stuck forever. It seems that it affects static network configurations. But again, it's not just this issue but the fact that dnet-prog is unmaintained, both upstream and in Debian and normally packages in such state - where it's apparent that no one is going to pick it up anywhere soon - are to be removed from Debian. I mean, are you going to adopt the DECnet-related packages? Adrian - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVhcocAAoJEHQmOzf1tfkTPYwP/1ib6p22dw88EqbudBgYbJyl fL44WBfhXQDMVlhlbI9mNWWuyXytdnY8ZbizL1GDBJsP6AHQIPmQ1D7oaZYkP8HW dpkIdjcBiaPMdGJftptdj+81b6iCZsTBqs2rx3cN431b9rGZf8GHf6JDpg/7qkD8 qnGz8wT2eNfXZTGpYvYrLCzO0kIiDP3ZMv043SC7bAJqZuC/NnE3HFF+7iPVwihT Fxvt0FsNwctmceehzksu3tKUE8NoOwVf6UQqKfKNbVMAB29X8js45h4Ac4DrFGAA mxHhRzWAPPiA+cRjTom6KyqRLzq4pgt+rJhOg1CbaKpSMRvf0zYAipliwVLOeA2s //2tfF30JwCIK8gDCVkbtIYltpKRe7e4QBnMQfSM4AdW2SFZW3Bp8DbqLw2y3Pha bVnqrByJU9oCHGXYeerIaulNEQnefzswCDk2Jr3w0hLAQzgTNj1ZNH3olagwpOSb /9Klv+aiHOd9DmJ8GZVxFIzI+7KNAGeOjsLgzcExbhn5LLcjqf7JoHZNqOkqKKg1 zW9UqoX6KMCebIVuIN4adMN0vvvYk6cYzs7hCPGHqxRWJm3El4ZUCM3Y4PLTm+hH xvE9j3HsTuDTzhUR6z4YMtuuibAiYLNffERtMb6r3OXbCpLkhOuXm1aD+iIuDnkq OdpuTAplp6K1nESqTPpy =0Kbb -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5585ca1c.2040...@physik.fu-berlin.de
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Hi Adrian, On Sat, Jun 20, 2015 at 10:16:28PM +0200, John Paul Adrian Glaubitz wrote: > On 06/20/2015 09:52 PM, Stephan Jauernick wrote: > > Please do for the reasons mentioned below. Also these are > > considered standard of a good bug report. > > No, the problem is apparent and I don't really want to debug libdnet. > > You are still trying to boil this down to the mere problem with cmus, > but that's just a side effect. The real point is that roaraudio depends > on an unmaintained piece of core software which Debian would like > to get rid of. It doesn't really matter if you're able to fix this > bug now as this won't change anything about the unmaintained status > of dnet-progs. > > So, please refrain from continuing the focus on this particular problem > with cmus, this is not the main issue, it's just the trigger that > brought me to the attention of this problem. I won't be bothered to > continue the discussion anymore if your only concern is this particular > problem with cmus but just eventually hand over the issue to the TC. > I am only a user who wants to help. While it is not even clear if it is in dnet you seem to be quite obsessed with it. So far from your previous mails i can only do a wild guess that it is somewhere in the cmus roar plugin/roaraudio complex. I never used decnet myself and probably won't. Also I myself don't particularily care about decnet. Additionally I am not the maintainer of either project but just someone who wants to help. If you point out a valid bug in decnet... I think nobody will object to dropping it. Also you are free to ask Patrick to drop the libdnet from roaraudio. I am trying to find out where the bug is located so we finally can contact the right upstream and work on a fix. > > I only get the decnet warning and then cmus starts up with about 5 > > seconds delay on the first start and from then on instantly. > > Which is _exactly_ the problem. It just appears that for some network > configurations it seems to get stuck forever. It seems that it affects > static network configurations. But again, it's not just this issue > but the fact that dnet-prog is unmaintained, both upstream and in > Debian and normally packages in such state - where it's apparent > that no one is going to pick it up anywhere soon - are to be removed > from Debian. > Then please make a bugreport against dnprogs, asking for it to be dropped from debian. We only know(as stated above i only can guess that much) that this bug occours on some configurations(which are currently unamed; for me it works on a virtualbox/with dhcp) and somewhere in the roaraudio/cmus plugin. It is not even clear if it is inside of libdnet. You could recompile roaraudio and the cmus roar without dnet and check if you still get the same behaviour. I would be happy to provide the debugging myself but i can't reproduce the bug. You could start giving us a meaningfull starting point for debugging the issue remotely. Ofcourse you can progress with trying to get Patrick or the TC to drop the dnet dependency. This might or might not solve the actual problem. In the event it does: Good job. You fixed a bug without propper debugging. In the event it doesn't: Good job. We can now finally start with bughunting! > I mean, are you going to adopt the DECnet-related packages? No. I am not going to do this. Reasons are stated above. > > Adrian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 Kind Regards, Stephan signature.asc Description: Digital signature
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Quoting Don Armstrong (2015-06-20 14:38:25) > There's clearly a bug here, but even after reading this bug log, I've > had to do research on my own to determine what that issue is. > > If the libroar2 maintainers which to keep decnet support, then someone > should probably figure out how to circumvent waiting for the DECnet to > settle when it isn't actually configured, and propose a patch to do > that. > > Even just checking for the existence of dnet-common or similar would > probably be enough. As I understand it, these are the issues raised here: a) libdnet is unmaintained and thus potentially dangerous to link against b) dnet-common commonly (or always by default?) cause whole system to hang I disagree that any of above are bugs in cmus. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Quoting John Paul Adrian Glaubitz (2015-06-20 15:16:28) > You are still trying to boil this down to the mere problem with cmus, This bugreport is filed against cmus, is it not? > but that's just a side effect. The real point is that roaraudio > depends on an unmaintained piece of core software which Debian would > like to get rid of. Then please reassign and retitle the bugreport to discuss the real issue where it belongs. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#788970: marked as done (abiword: please adapt for libwps 0.4)
Your message dated Sun, 21 Jun 2015 06:19:14 + with message-id and subject line Bug#788970: fixed in abiword 3.0.0-9 has caused the Debian Bug report #788970, regarding abiword: please adapt for libwps 0.4 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 ow...@bugs.debian.org immediately.) -- 788970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: abiword Version: 1:3.0.0-8 Severity: wishlist Tags: patch See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786713. libwps 0.4 was released in May and we should transition to that, especially because LibreOffice 5.0 strictly needs >= 0.4 and won't work/build with earlier ones. As I mentioned in the first message to the above bug - thankfully the diff is trivial, as demonstrated by the "official" patch I mentioned in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786713.#15 which is http://pkgs.fedoraproject.org/cgit/abiword.git/commit/?id=1482cf1f893b6378f6c868a1f12b7bd366d6 Regards, Rene -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: abiword Source-Version: 3.0.0-9 We believe that the bug you reported is fixed in the latest version of abiword, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 788...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rene Engelhard (supplier of updated abiword package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 16 Jun 2015 23:11:12 +0200 Source: abiword Binary: abiword-common abiword abiword-plugin-grammar abiword-plugin-mathview libabiword-3.0 libabiword-3.0-dev abiword-dbg Architecture: source all amd64 Version: 3.0.0-9 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Rene Engelhard Description: abiword- efficient, featureful word processor with collaboration abiword-common - efficient, featureful word processor with collaboration -- common abiword-dbg - debugging symbols for abiword word processor abiword-plugin-grammar - grammar checking plugin for AbiWord abiword-plugin-mathview - equation editor plugin for AbiWord libabiword-3.0 - efficient, featureful word processor with collaboration -- shared libabiword-3.0-dev - efficient, featureful word processor with collaboration -- develo Closes: 788970 Changes: abiword (3.0.0-9) unstable; urgency=medium . * QA upload. * build against libwps 0.4.0 (closes: #788970) Checksums-Sha1: 8c36b07250f1d7fb7589655e8dfc320fc9c060fc 2946 abiword_3.0.0-9.dsc b0873e771dfb875a906646919dcdad9146e3f5f5 51732 abiword_3.0.0-9.debian.tar.xz d3be0c98b038d6ae46fa08b0b11e00281fb04f93 1665052 abiword-common_3.0.0-9_all.deb a8d8d3ef0405fcdc52a4605134a41b6c48cf4d23 26091448 abiword-dbg_3.0.0-9_amd64.deb 3712b6e4303fb634f6c79bf4ff1a72e72b74fcbd 46928 abiword-plugin-grammar_3.0.0-9_amd64.deb a3c1c5724648770323330c5384ac2e9bf7335271 123700 abiword-plugin-mathview_3.0.0-9_amd64.deb e8238fd45a61e0f2ec8b760bf4dc10efa7d7a24d 1231492 abiword_3.0.0-9_amd64.deb ce6d0992b9057630d5c85b31bb118bc8d7fc5706 43272 libabiword-3.0-dev_3.0.0-9_amd64.deb ac59880e8958eaf0fb992b9ab2cf2c0419a5b6d0 2091688 libabiword-3.0_3.0.0-9_amd64.deb Checksums-Sha256: af4017015090ffd89bcb44928bf8f8798625ccfb13ea7c9728d52eb4b4c17cd5 2946 abiword_3.0.0-9.dsc c4e89a3416bad74f24b30cac38e4b160f7df8166782e9f513c400be79dcae55c 51732 abiword_3.0.0-9.debian.tar.xz 4d6704402b86bded118f4e688c077f80272ab2d938e3424c0cc28f4e2db42061 1665052 abiword-common_3.0.0-9_all.deb d13d4dd7d6d58bccf9b6de70b84e003e78f030370a58e553c9bb9bccb8fab8ef 26091448 abiword-dbg_3.0.0-9_amd64.deb e56d0b0ff7368a42810f130fe6cc46b30ab49cc05aad16e98a425feaa669fc89 46928 abiword-plugin-grammar_3.0.0-9_amd64.deb 9e379ff4dc82da37276be0cd060decae366bea507242750eb4e58dba30efc9e5 123700 abiword-plugin-mathview_3.0.0-9_amd64.deb 87141fdd2cc394dbbb1d2
Processing of abiword_3.0.1-3_amd64.changes
abiword_3.0.1-3_amd64.changes uploaded successfully to localhost along with the files: abiword_3.0.1-3.dsc abiword_3.0.1-3.debian.tar.xz abiword-common_3.0.1-3_all.deb abiword-dbg_3.0.1-3_amd64.deb abiword-plugin-grammar_3.0.1-3_amd64.deb abiword-plugin-mathview_3.0.1-3_amd64.deb abiword_3.0.1-3_amd64.deb gir1.2-abiword-3.0_3.0.1-3_amd64.deb libabiword-3.0-dev_3.0.1-3_amd64.deb libabiword-3.0_3.0.1-3_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1z6yqu-00058p...@franck.debian.org
Processing of abiword_3.0.0-9_amd64.changes
abiword_3.0.0-9_amd64.changes uploaded successfully to localhost along with the files: abiword_3.0.0-9.dsc abiword_3.0.0-9.debian.tar.xz abiword-common_3.0.0-9_all.deb abiword-dbg_3.0.0-9_amd64.deb abiword-plugin-grammar_3.0.0-9_amd64.deb abiword-plugin-mathview_3.0.0-9_amd64.deb abiword_3.0.0-9_amd64.deb libabiword-3.0-dev_3.0.0-9_amd64.deb libabiword-3.0_3.0.0-9_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1z6yqz-000593...@franck.debian.org
abiword_3.0.1-3_amd64.changes is NEW
binary:gir1.2-abiword-3.0 is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will recieve an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1z6ybn-0006vr...@franck.debian.org
abiword_3.0.0-9_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 16 Jun 2015 23:11:12 +0200 Source: abiword Binary: abiword-common abiword abiword-plugin-grammar abiword-plugin-mathview libabiword-3.0 libabiword-3.0-dev abiword-dbg Architecture: source all amd64 Version: 3.0.0-9 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Rene Engelhard Description: abiword- efficient, featureful word processor with collaboration abiword-common - efficient, featureful word processor with collaboration -- common abiword-dbg - debugging symbols for abiword word processor abiword-plugin-grammar - grammar checking plugin for AbiWord abiword-plugin-mathview - equation editor plugin for AbiWord libabiword-3.0 - efficient, featureful word processor with collaboration -- shared libabiword-3.0-dev - efficient, featureful word processor with collaboration -- develo Closes: 788970 Changes: abiword (3.0.0-9) unstable; urgency=medium . * QA upload. * build against libwps 0.4.0 (closes: #788970) Checksums-Sha1: 8c36b07250f1d7fb7589655e8dfc320fc9c060fc 2946 abiword_3.0.0-9.dsc b0873e771dfb875a906646919dcdad9146e3f5f5 51732 abiword_3.0.0-9.debian.tar.xz d3be0c98b038d6ae46fa08b0b11e00281fb04f93 1665052 abiword-common_3.0.0-9_all.deb a8d8d3ef0405fcdc52a4605134a41b6c48cf4d23 26091448 abiword-dbg_3.0.0-9_amd64.deb 3712b6e4303fb634f6c79bf4ff1a72e72b74fcbd 46928 abiword-plugin-grammar_3.0.0-9_amd64.deb a3c1c5724648770323330c5384ac2e9bf7335271 123700 abiword-plugin-mathview_3.0.0-9_amd64.deb e8238fd45a61e0f2ec8b760bf4dc10efa7d7a24d 1231492 abiword_3.0.0-9_amd64.deb ce6d0992b9057630d5c85b31bb118bc8d7fc5706 43272 libabiword-3.0-dev_3.0.0-9_amd64.deb ac59880e8958eaf0fb992b9ab2cf2c0419a5b6d0 2091688 libabiword-3.0_3.0.0-9_amd64.deb Checksums-Sha256: af4017015090ffd89bcb44928bf8f8798625ccfb13ea7c9728d52eb4b4c17cd5 2946 abiword_3.0.0-9.dsc c4e89a3416bad74f24b30cac38e4b160f7df8166782e9f513c400be79dcae55c 51732 abiword_3.0.0-9.debian.tar.xz 4d6704402b86bded118f4e688c077f80272ab2d938e3424c0cc28f4e2db42061 1665052 abiword-common_3.0.0-9_all.deb d13d4dd7d6d58bccf9b6de70b84e003e78f030370a58e553c9bb9bccb8fab8ef 26091448 abiword-dbg_3.0.0-9_amd64.deb e56d0b0ff7368a42810f130fe6cc46b30ab49cc05aad16e98a425feaa669fc89 46928 abiword-plugin-grammar_3.0.0-9_amd64.deb 9e379ff4dc82da37276be0cd060decae366bea507242750eb4e58dba30efc9e5 123700 abiword-plugin-mathview_3.0.0-9_amd64.deb 87141fdd2cc394dbbb1d2458acce5ed5da07990907347b26b48ff17019a8fcae 1231492 abiword_3.0.0-9_amd64.deb a204a81ca99a0f860fa0d58467a56d446433a2c05e36d8fc8653a310ac6aad3d 43272 libabiword-3.0-dev_3.0.0-9_amd64.deb 3833d53fb8927d5cf24e5a4d64527997c83bf01926d9fbeb691016c52406 2091688 libabiword-3.0_3.0.0-9_amd64.deb Files: 2c442759c919ecbcb4998e4a1b73e544 2946 gnome optional abiword_3.0.0-9.dsc 02960501a2fac8678714eb1399baf8ca 51732 gnome optional abiword_3.0.0-9.debian.tar.xz 1fdc059250555e66c5d0ee72195f279f 1665052 editors optional abiword-common_3.0.0-9_all.deb 89227729b2be4dbd3dbcb7e4b3334cd7 26091448 debug extra abiword-dbg_3.0.0-9_amd64.deb ffd45499f5092b7a40548fcf98ad14d9 46928 editors optional abiword-plugin-grammar_3.0.0-9_amd64.deb 85a48710a85651578910d0671d0df7c6 123700 editors optional abiword-plugin-mathview_3.0.0-9_amd64.deb 9e8b0a9b899a632d48fec4fc6176ad3b 1231492 editors optional abiword_3.0.0-9_amd64.deb 4a68ae0b950a5956f277ff4a5cc72cb0 43272 libdevel optional libabiword-3.0-dev_3.0.0-9_amd64.deb 603b3bc971a1b8655d1d8acf3203aaa4 2091688 libs optional libabiword-3.0_3.0.0-9_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVgQzjAAoJEAqgRXHQPj5wjLQP/jlz/4lDMitUn18hGre10iP9 iqaTmmlqjnpXmqGe/BE0SrkbF+1ePSr4andBMhz2rGwUCAAcxDR/kpAl9zBPyASi hAEQZfJkHWRcWs9maVwICC2Zi2xRU8cLZ05n2lmmzyhv6qYvk1BTsrDq58kuSp9r Z3uNz9ZLOLlMNVTYZ4ybVuaBXu6mCITmENigTN2gyg8AzryDwLt16E0YFeDxrMcO FSTx0nzvHWmMfMoIPkIxJQ8hK1OSzQQwTNt+j8//abZzd3Z4ksg0lT+yOPhpM755 CjCzhzLlkv5Qj9GbA0hNohkHki4lKc4yjF6Snt6lZmkMukFtizn8jRglPJazffDF JI4c93wJgx5wKyQrn8t+n/oTzVNiPSk87cDc/zX2T4D/w91PrQ2A/5vxdVEAxIX0 eGAllwJ2TeisAmOtACsv9qKBX8bldWlUoI0A0IyiAVu6AyY0hdVo2U8egbEnI/LW oLKWBOLl0W3RocTK3FN8+/CkfduRs/YHLYR17PBxgdnXHsT6YHdNY5dlS6Nu02V8 2/kTe7S5mCPUSqin4vAM9kvXmcP3rmCpnRBSVFYK0o0/mP+f/Nb3v1MZ2Elibcox h2CTJvkl1P4ZtvAqXl+GrXktljB5i3gddVs+ynAi0omDkY551pikREIgBfFRJwL6 IqErm26sXcSoJmCwenzC =FqSF -END PGP SIGNATURE- Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1z6yb4-0006fc...@franck.debian.org
Processed: Bug#788970 tagged as pending
Processing commands for cont...@bugs.debian.org:
> tag 788970 pending
Bug #788970 {Done: Rene Engelhard } [src:abiword] abiword:
please adapt for libwps 0.4
Added tag(s) pending.
> --
Stopping processing here.
Please contact me if you need assistance.
--
788970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/handler.s.c.143486851521110.transcr...@bugs.debian.org
