Your message dated Fri, 28 Oct 2016 00:26:35 +0200 with message-id <20161028002053.GA28064@debian.org> and subject line Re: Bug#842307: Ports still broken with error "unknown key (key id B4C86482705A2CE1)" has caused the Debian Bug report #842307, regarding Ports still broken with error "unknown key (key id B4C86482705A2CE1)" 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.) -- 842307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842307 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Ports still broken with error "unknown key (key id B4C86482705A2CE1)"
- From: Jeffrey Walton <noloader@gmail.com>
- Date: Thu, 27 Oct 2016 17:38:56 -0400
- Message-id: <[🔎] CAH8yC8kNvX0B2ZTU3d7VQxrVGB6u60aJGSXghuzgJn_aLBSbUQ@mail.gmail.com>
- Reply-to: noloader@gmail.com
Package: apt Version: 1.0.9.8 Severity: important Ports and Apt are still broken. And Apt does not honor --no-check-gpg or --allow-unauthenticated. I'm going to call bullshit on Message 15 at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826043#15. The shit does not work. I'm going to call bullshit on Message 65 at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826043#65. The report should not have been closed. Debian has a major engineering problem if it does not realize how broken some of this stuff is. Its ridiculous to suffer the same problems and errors for nearly two years. Its ridiculous to have bug reports like 826043 with all the details but manage to avoid fixing a problem. See for yourself. Follow the directions at http://ftp.ports.debian.org/debian-ports-cd/hurd-i386/current/YES_REALLY_README.txt. Download today's image. Then try to update the VM. It sure would be nice if someone stepped up, took ownership of these ports, and fixed the god damn things so they "just worked".
--- End Message ---
--- Begin Message ---
- To: noloader@gmail.com, 842307-close@bugs.debian.org
- Subject: Re: Bug#842307: Ports still broken with error "unknown key (key id B4C86482705A2CE1)"
- From: Julian Andres Klode <jak@debian.org>
- Date: Fri, 28 Oct 2016 00:26:35 +0200
- Message-id: <20161028002053.GA28064@debian.org>
- In-reply-to: <[🔎] CAH8yC8kNvX0B2ZTU3d7VQxrVGB6u60aJGSXghuzgJn_aLBSbUQ@mail.gmail.com>
- References: <[🔎] CAH8yC8kNvX0B2ZTU3d7VQxrVGB6u60aJGSXghuzgJn_aLBSbUQ@mail.gmail.com>
On Thu, Oct 27, 2016 at 05:38:56PM -0400, Jeffrey Walton wrote: > Package: apt > Version: 1.0.9.8 > Severity: important > > Ports and Apt are still broken. And Apt does not honor --no-check-gpg > or --allow-unauthenticated. > > I'm going to call bullshit on Message 15 at > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826043#15. The shit > does not work. > > I'm going to call bullshit on Message 65 at > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826043#65. The > report should not have been closed. There was a problem and it was fixed in 1.2 and 1.3. There will be no fix for older release series. Hurd is not a release architecture, it is not part of the stable release and it would thus be pointless to include a fix for it in a stable update. > > Debian has a major engineering problem if it does not realize how > broken some of this stuff is. Its ridiculous to suffer the same > problems and errors for nearly two years. Its ridiculous to have bug > reports like 826043 with all the details but manage to avoid fixing a > problem. > > See for yourself. Follow the directions at > http://ftp.ports.debian.org/debian-ports-cd/hurd-i386/current/YES_REALLY_README.txt. > Download today's image. Then try to update the VM. > > It sure would be nice if someone stepped up, took ownership of these > ports, and fixed the god damn things so they "just worked". I'm closing this bug. Get your shit together. Your email is inappropriate. If you experience a different bug, explain the bug you experience. And do it for 1.3, not for stable. Ports are not supported in any case. Please talk to your porters and let them talk to us instead of writing hate emails. -- Debian Developer - deb.li/jak | jak-linux.org - free software dev When replying, only quote what is necessary, and write each reply directly below the part(s) it pertains to ('inline'). Thank you.
--- End Message ---