Your message dated Wed, 18 May 2016 19:43:27 +0200 with message-id <20160518174327.GB21790@crossbow> and subject line Re: Bug#824563: [apt] dep11 backward compatilibity has caused the Debian Bug report #824563, regarding [apt] dep11 backward compatilibity 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.) -- 824563: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824563 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: [apt] dep11 backward compatilibity
- From: Fernando Toledo <ftoledo@docksud.com.ar>
- Date: Tue, 17 May 2016 11:19:25 -0300
- Message-id: <[🔎] d0a045eb-5878-954d-cb8a-cbf8053782a8@docksud.com.ar>
Package: apt Version: 1.2.11 Severity: normal --- Please enter the report below this line. --- apt-get update in stretch has error using old repos that not expose DEP11 files. I use reprepro to generate my own repo to support a derivated debian distro. I believe that exists many private and public repos made with tools like reprepro/aptly/mini-dinstall etc.. and have this problem too. I known that reprepro must be fixed to support DEP11 (i was fill a bug on reprepro bts) but until this "transition" stage, i think that apt-get must have compatilibity and raise a warning instead of error. Thanks! -- Fernando Toledo Dock Sud BBS http://bbs.docksud.com.ar telnet://bbs.docksud.com.ar
--- End Message ---
--- Begin Message ---
- To: Fernando Toledo <ftoledo@docksud.com.ar>, 824563-done@bugs.debian.org
- Subject: Re: Bug#824563: [apt] dep11 backward compatilibity
- From: David Kalnischkies <david@kalnischkies.de>
- Date: Wed, 18 May 2016 19:43:27 +0200
- Message-id: <20160518174327.GB21790@crossbow>
- In-reply-to: <[🔎] 34269289-088b-aaf6-6ba6-ea306844b37e@docksud.com.ar>
- References: <[🔎] d0a045eb-5878-954d-cb8a-cbf8053782a8@docksud.com.ar> <[🔎] 20160517175233.GA2593@debian.org> <[🔎] 34269289-088b-aaf6-6ba6-ea306844b37e@docksud.com.ar>
On Tue, May 17, 2016 at 01:48:09PM -0300, Fernando Toledo wrote: > I found that bug > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814416 that is exacly > my problem. > please close this bug and my apologies! No problem & as you wish: Closing as not a bug. Best regards David KalnischkiesAttachment: signature.asc
Description: PGP signature
--- End Message ---