Have been rewriting the description according to the new findings. I
hardly think I can do much more now. But I hope to have saved some time
for the developer. Dont hessitate to ask if you need something more.

/Kenneth

** Description changed:

- [Later edit: Clearify and some spelling corrections.]
+ I had made some new findings, and am rewriting the description accordingly. 
I'm not a developer and don't know how it works behind the surface. I'm using 
“trial and error” and tries find things out.
+ Please change anything according to your skills and needs.
  
- This bug might affect or have it's source in another package. I just
- putted it where I found the troubble. Feel free to change if you like.
- (This might affect unattended-upgrades as well, i don't know.)
+ WHERE IS THE BUG FOUND?
+ I think it is best to start here.
  
- I will first tell what I found, and then what I expect instead. Last of
- all, a workaround.
+ I have found this bug using Xubuntu, I guess the other flavors are affected 
in the same way.
+ I have found it in Xubuntu 12.04.3 Precise, and in 13.10 Saucy. Both 64-bit. 
It is likely that it affects Quantal and Raring likewise.
+ 
+ 
+ It do affect amd64 systems. It does not seem to affect i386. I tried at 
Lubuntu Saucy 32-bit as well, not problem. I can not explain why.
+ 
  
  PROBLEM
- I'm running a fully updated Saucy 13.10, with critical and recommended repos 
enabled. Not backports or proposed.
- update-manager version 1:0.194.1
- 
- I have lately found out about the apt-build package. When I install that
- package it also installs several others. It also, this is crucial, ads a
- line in the sources list found in sources-manager-GUI. But there is no
- change in /etc/apt/sources.list. (Suprinsing) So the change is made
- somewere else thats affects the sources-manager. The new row is
- "file:/var/cache/apt-build/repository". I don't know where the actual
- addition is made, but it's visible in tha sources-manager-GUI.
- 
- This new line complicates thing. When I run update-manager it complains
- that it could not "download" all files. If I uncheck that line in the
- sources-manager, then the software-updater works as normal again. The
- error message looks like this:
- 
+ In a fresh install av Xubuntu I have installed apt-build and its 
dependencies. During the installation it asks some questions. One of them is 
what architecture I want to build my applications for. I choose “native”, there 
is also generic and a couple of specified. Another question is about putting a 
line in the sources list, wich should be necessary if you want to install the 
compiled packages with apt. I accepted. (Sadly, I don't remember the exact 
words, it might be important. English is not my primary language.)
+ I have disabled proposed and backport repos, and after this I have updated 
the sources cache with the update-manager-GUI. It then showed this error 
message:
  ------------
- "W:Failed to fetch 
file:/var/cache/apt-build/repository/dists/apt-build/main/binary-i386/Packages  
File not found
+ "W:Failed to fetch 
file:/var/cache/apt-build/repository/dists/apt-build/main/binary-i386/Packages 
File not found
  , E:Some index files failed to download. They have been ignored, or old ones 
used instead."
  -----------
+ Note that the path in the error message point at a i386-folder! (The machine 
is amd64.)
+ If I inspect the file /etc/apt/sources.list, there is nothing related to the 
path mentioned in the error message. It seems untouched. This means that 
apt-build did not add a line there, it added the line somewhere else. I do not 
know where. It is visible in the sources-manager-GUI, and can be checked and 
unchecked. (Unchecked it does not generate this error.)
  
- WHAT I EXPECT TO HAPPEN
- I expect that the software-updater can tell difference of local and remote 
files, and only demand download and updated of the later. The local ones can be 
used as they are.
+ If I use the terminal and am running apt-get update I face the same problem. 
In the output, there is two error messages.
+ –---------------
+ user@computer:~$ sudo apt-get update
+ [sudo] password for user: 
+ Ign file: apt-build InRelease
+ Ign file: apt-build Release.gpg                                          
+ Get:1 file: apt-build Release [107 B]                                         
 
+ Err file: apt-build/main i386 Packages                                        
 
+   File not found
+ Ign file: apt-build/main Translation-en_US                                    
 
+ Ign file: apt-build/main Translation-en
+ 
+ [...]
+ Ign http://ubuntu.mirror.su.se saucy-security/multiverse Translation-en_US
+ Ign http://ubuntu.mirror.su.se saucy-security/universe Translation-en_US
+ W: Failed to fetch 
file:/var/cache/apt-build/repository/dists/apt-build/main/binary-i386/Packages 
File not found
+ E: Some index files failed to download. They have been ignored, or old ones 
used instead.
+ user@computer:~$ sudo apt-get update > /home/user/upgrade.txt
+ W: Failed to fetch 
file:/var/cache/apt-build/repository/dists/apt-build/main/binary-i386/Packages 
File not found
+ E: Some index files failed to download. They have been ignored, or old ones 
used instead.
+ ---------------
+ 
+ By now it is obvious that the problem is not related to the GUI.
+ 
+ Note that in all error messages it is asked for an i386 folder. But the
+ line I can see in update-manager only specifies "file:/var/cache/apt-
+ build/repository", nothing about either i386 or amd64. That direction is
+ chosen somewhere else. And that seems to be whats going wrong!
+ 
+ FOLDER STRUCTURE
+ If I am looking in the folder "file:/var/cache/apt-build/repository", it 
looks like this:
+ -----ls output-------
+ dists [folder]
+ gthumb_3.0.2-0ubuntu3+aptbuild1_amd64.deb
+ gthumb-data_3.0.2-0ubuntu3+aptbuild1_all.deb
+ gthumb-dbg_3.0.2-0ubuntu3+aptbuild1_amd64.deb
+ gthumb-dev_3.0.2-0ubuntu3+aptbuild1_amd64.deb
+ Packages.gz
+ Release
+ ----------------------
+ If I continue down the path according to the error messages, I find a folder: 
“/var/cache/apt-build/repository/dists/apt-build/main/binary-amd64/” This is 
likely to be the correct path.
+ 
+ CONCLUSION
+ Either apt-build, or the update programs is getting something wrong. I can't 
tell wish of them.
+ 
+ Apt-get is correctly creating a local repository for the chosen
+ architecture, but does not seem able to communicate it to the update
+ programs. Or, it might as well bu that is informed correctly, but the
+ update programs is reading it wrong.
  
  WORKAROUND
- Keep the row  "file:/var/cache/apt-build/repository" deactivated in sources 
manager. Only enable it when you are messing around with apt-build, then 
deactivate it again. The own-build packages doesn't seem to be classified as 
obolsete/local in synaptic on this account.
- --- 
- ApportVersion: 2.12.5-0ubuntu2.2
- Aptdaemon:
-  
- Architecture: amd64
- DistroRelease: Ubuntu 13.10
- GsettingsChanges:
-  com.ubuntu.update-manager first-run false
-  com.ubuntu.update-manager launch-time 1389440694
-  com.ubuntu.update-manager show-details true
-  com.ubuntu.update-manager window-width 439
- InstallationDate: Installed on 2013-12-28 (14 days ago)
- InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
- MarkForUpload: True
- Package: update-manager 1:0.194.1
- PackageArchitecture: all
- Tags:  saucy
- Uname: Linux 3.8.13-03081315-generic x86_64
- UpgradeStatus: No upgrade log present (probably fresh install)
- UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ My previous workaround did remove the  error messages, but did not solve the 
problem. Therefore removed. It was wrong.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268120

Title:
  apt-build generates en error message in update-manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-build/+bug/1268120/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to