Re: [SOGo] Debian Jessie i386 builds missing by mistake or intentionally ?
Hello Am 20.01.2016 um 14:32 schrieb Christian Mack: > > Am 20.01.2016 um 12:43 schrieb Andreas Balg (XiNCS): >> >> I know it might be a strange thing nowadays to run any server using i386 >> builds, but nevertheless we do so for legacy reasons - Now I cannot >> update sogo 2 from the debian/jessie repos anymore: >> >> Due to this error: >> >> W: Failed to fetch http://inverse.ca/debian/dists/jessie/InRelease >> Unable to find expected entry 'jessie/binary-i386/Packages' in Release >> file (Wrong sources.list entry or malformed file) >> >> Is it just your decision not to build i386 packages for debian/jessie >> anymore? Or did this happen by mistake? >> >> BTW: building and offering sogo for arm - cpu's seems like a good idea >> to me as well - this would allow running it as personal Groupware on a >> NAS like QNAP or Synology as well .. >> >> > > Inverse does not provide i386 builds since almost a year now. > They are no longer supported because they need substantial work to keep > up, but are not used much. > http://www.sogo.nu/bugs/view.php?id=3407 > BTW: There was a thread on this mailinglist about getting SOGo running on ARM. Don't remember, if they succeeded or not, sorry. Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416 smime.p7s Description: S/MIME Cryptographic Signature
Re: [SOGo] Debian Jessie i386 builds missing by mistake or intentionally ?
Hello Am 20.01.2016 um 12:43 schrieb Andreas Balg (XiNCS): > > I know it might be a strange thing nowadays to run any server using i386 > builds, but nevertheless we do so for legacy reasons - Now I cannot > update sogo 2 from the debian/jessie repos anymore: > > Due to this error: > > W: Failed to fetch http://inverse.ca/debian/dists/jessie/InRelease > Unable to find expected entry 'jessie/binary-i386/Packages' in Release > file (Wrong sources.list entry or malformed file) > > Is it just your decision not to build i386 packages for debian/jessie > anymore? Or did this happen by mistake? > > BTW: building and offering sogo for arm - cpu's seems like a good idea > to me as well - this would allow running it as personal Groupware on a > NAS like QNAP or Synology as well .. > > Inverse does not provide i386 builds since almost a year now. They are no longer supported because they need substantial work to keep up, but are not used much. http://www.sogo.nu/bugs/view.php?id=3407 Kind regards, Christian Mack PS: Please do not hijack threads. -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416 smime.p7s Description: S/MIME Cryptographic Signature
[SOGo] Debian Jessie i386 builds missing by mistake or intentionally ?
I know it might be a strange thing nowadays to run any server using i386 builds, but nevertheless we do so for legacy reasons - Now I cannot update sogo 2 from the debian/jessie repos anymore: Due to this error: W: Failed to fetch http://inverse.ca/debian/dists/jessie/InRelease Unable to find expected entry 'jessie/binary-i386/Packages' in Release file (Wrong sources.list entry or malformed file) Is it just your decision not to build i386 packages for debian/jessie anymore? Or did this happen by mistake? BTW: building and offering sogo for arm - cpu's seems like a good idea to me as well - this would allow running it as personal Groupware on a NAS like QNAP or Synology as well .. -- users@sogo.nu https://inverse.ca/sogo/lists
