On 29/02/2020 23:11, gumb wrote:
On 27/02/2020 15:03, Simon Becherer wrote:
put all into a directory "./Downloaded-rpm" and let createreop create a repository-index from it createrepo ./Downloaded-rpm (maybe install with yast before "createrepo_c") add this repo to your repos.
now install with yast (i installed each rpm single) mfc7460dnlpr cupswrapperMFC7460DN
I'll come back to this. [snip]
To come back to the earlier point about your install of the files via YaST, I've already done the install numerous times from different directories, either with the rpms in situ or downloaded fresh from the script. Within YaST Software Management I see the rpms as 'installed' so they should be in the rpm database. I could uninstall and reinstall for the umpteenth time and do it all in YaST without the script. Maybe when I've got more mental energy tomorrow. But I can't see how that would really change anything.
Success at last! Although I'm not 100% sure which of the actions I just performed had the desired effect. After the first few days of getting nowhere, I'd uninstalled the long list of 76 32-bit dependencies, attached to my original post, keeping just libusb-0_1-4-32bit. When installing using the Brother script it doesn't pull all these in and the only consistent reference I keep seeing is about that libusb file. I've already tried installing one or two random things in the interim, such as additonal cups backends, to no avail. I was browsing through other associated cups files in YaST and saw libcups2-32bit, so I selected it for install, just on a hunch (I've subsequently noted that that was amongst the 76 previously installed). That pulled in 26 32-bit dependencies, so not as many as the 76 I had originally. I also decided to search for each of the three Brother rpms already installed, then select them to 'Update Unconditionally'. This indicated that it also wanted to install libgcc_s1-32bit and libstdc++6-32bit. Both of these were amongst those 76 too. The next time I tried a test print in YaST suddenly it sprang into life, both via wireless and USB. I've subsequently reinstated the firewall, AppArmor and removed my user from the lp group. It continues to print fine. Either forcibly reinstalling the rpms had some effect or I was missing something else in the config when I originally had the 76 files installed, though I struggle to see what. I'm not inclined to mess about diagnosing it any further, I need to use it urgently over the next couple of days. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org